I am trying to migrate jenkins from old server to newer one. I have imported all the jobs and config from old server. But after making changes to job configuration in new jenkins, I am facing "A problem occurred while processing the request" error while applying and saving that job.
Old Jenkins Version: 2.289.1
New Jenkins Version: 2.289.1
openjdk version:11.0.11
Error Screenshot
Error Screenshot
The issue has been resolved.
It was happening because the permissions inside jenkins jobs directory were not set to jenkins:jenkins
Related
I am trying to execute a CI/CD project. Everytime i am trying to create a job and trying to save my job it pops up an error. I have gone through a few issues available on the internet, but none of them have resolved the issue.
Can anybody help in this regard? Thanks
Tomcat 9 Server
Java 16.0.1
Jenkins 2.361.1
I would suggest do following:
Check the Jenkins logs on server and try to fix.
If don't work, try to restart your Jenkins.
Before installing Git plugin in my Jenkins all my jobs were working properly. After installing the Git plugin, my Jenkin get restart and after that my jobs are not displaying in dashboard. When I check in system log, I found issue stating "Failed to load struct, Failed to load x job, Failed to load Y job..... And so on".
How can I resolve this?
You need to upgrade Jenkins to the latest version. This will solve the problem.
Executing Maven build in jenkins pod(container) using jenkins Kubernetes
Created a maven build
I am cloning from git
Then trying to execute the junit scripts
For few builds I faced pom.xml path issue
Later after clone I faced java.nio.channels.ClosedChannelException
Now directly once the build starts getting this error java.nio.channels.ClosedChannelException
More Info:
I also increased memory but didnt worked
enter image description here
I was using the same port for docker Jenkins and local jenkins. I made com.nirima.jenkins.plugins.docker.DockerContainerWatchdog.enabled=false on ALL the Jenkins servers as per some reference.But still facing the issue
I recently had some issues regarding version upgrade for my Jenkins server. In order to update the version of the jenkins server, the first step I did was to create a backup:
sudo tar -zcvf /tmp/jenkins.tgz /var/lib/jenkins
Then, I copied the archived file, from server A and untar it on another server, server B. I can see all the files [workspace, config.xml, jobs] of server A to server B in var/lib/jenkins.
When I am logging into the jenkins box it showed:
Jenkins detected that you appear to be running more than one instance of Jenkins that share the same home directory '/var/lib/jenkins’. This greatly confuses Jenkins and you will likely experience strange behaviors, so please correct the situation.
This Jenkins:
490566619 contextPath="" at 8779#jm1597185631ybr.cloud.phx3.gdg
Other Jenkins:
1998724099 contextPath="" at 20292#jm1584048540yxl.cloud.phx3.gdg
So, I stopped the jenkins service using:
sudo service jenkins stop
Then I restarted the service using
sudo service jenkins restart
All the jobs started to appear suddenly. I have following questions:
Why did the jobs started to show up and not throw the error of running multiple instances?
If version is the only issue, why cannot the newly provisioned
server have the updated version? Is it when I copy the files from server A, the server B files gets overwritten and hence, shows the same error of the version upgrade?
I am using Jenkins version 2.222.1 with EWM version 7.0 (Formerly known as RTC). When I am trying to save a build definition created in RTC I am getting this error.
I have checked the test connection was successful while creating build engine in RTC.
This is similar to this issue:
either the user for the test connection is not the same as the one used to access Jenkins Job in the RTC build definition
or it is, but without the right, on Jenkins permission matrix, to view jobs
or the user is Jenkins admin and has all the right anyway, but the Jenkins logs might include something like "WARNING hudson.security.csrf.CrumbFilter#doFilter: No valid crumb was included in request for ... by <aUser>: Returning 403"
The last case is an actual RTC issue, to be fixed with RTC 7.x (and seen with Jenkins 2.190 or later)