I realize that this question has been asked before but I feel like my case is different.
About five hours after I launch jenkins I sometimes see this message appear when loading the jenkins administrator panel:
Jenkins detected that you appear to be running more than one instance of Jenkins that share the same home directory '’. This greatly confuses Jenkins and you will likely experience strange behaviors, so please correct the situation."
This is strange, it happens every time I launch it, eventually making Jenkins unusable. I installed Jenkins via homebrew and launch is via the jenkins CLI. I manually do this so I don't see how it's possible that Jenkins launches twice.
I reinstalled Jenkins after completely removing it. Still no luck.
Anyone have any issues like this before?
I also had a similar problem and solved it with following checks:
Check if another java process is running which runs jenkins e.g. in unix using top
If you're using tomcat, search for a second instance of tomcat having the jenkins.war exploded somewhere
Could be helpful to just have one version of java installed
Related
Today I noticed that several of our Jenkins jobs (which are independant, different projects and everything) failed.I investigated an finally listed all processes on the machine that Jenkins uses with the top command. It showed me a very greedy process launched by Jenkins, which name is iLmBjh. Not very clear, isn't it?I tried some things and finally killed it. But it appeared again when I launched a new Jenkins job.Do someone know what this process does? It's the first time I see it on the processes list...
Ok, I guess I found the problem and it's kind of surprising. On our Jenkins instance, we had the JiraTestReporter plugin installed. Our Jira licence ended today. And when I checked the Jenkins logs, it was full of Jira error messages.What is disturbing is that we weren't using it at all... in any of our jobs!I uninstalled it and was able to run my job again. The iLmBjh process did not come back.
I created a slave node and ran a pipeline successfully but after that unable to configure the node. I've tried restarting Jenkins using the weburl as well as the shell. At this point, its stuck at creating a new Node or even when configure is clicked. The page just never opens. Deleting an existing node worked however.
Even the Mutli-Slave config plugin runs into the same problem. I'm guessing some data corruption? It would be a shame to reinstall Jenkins and redo the awful amount of configuration. Any ideas?
I was just beginning to like Jenkins.
PS: Editing the master node works. Using Jenkins 2.5.
EDIT:
I manually created a folder for a node under JENKINS_HOME/nodes and copied a config.xml for the node from some other server. The node appears in the list after server restart but still the option to Configure it hangs forever.
After wasting a lot of time I finally fixed the issue by downgrading Credentials plugin to the previous version: 1.28. Earlier today I had upgraded to the available latest 2.0.
Looks like others also hit the same problem today: https://github.com/jenkinsci/credentials-plugin/issues/49
Situation:
Yesterday morning, all of our Slaves had problems (because thanks to Java, which removed the medium security level, the Jenkins slave agent could not be launched anymore). Java then started blocking all Jenkins slave agent.jlnp, we had to add on every slave an exception for our jenkins server, so the slave application can be launched. This was annoying but now they work. (was there an easier solution?)
Few slaves had Jenkins installed as a service (to be launched automatically on startup). However, since yesterday, they do not launch anymore, and we cannot find why. It probably has to do with the security from Java.
Someone has any idea?
You need to update jenkins reference to Java. It is in file C:\Jenkins\jenkins-slave.xml (or whereever is your Jenkins folder). When you updated Java Jenkins no longer knows where to find new version
Mine looks something like this.
<executable>C:\Program Files (x86)\Java\jre1.8.0_91\bin\java.exe</executable>
I made it works with the following steps:
1-) Uninstalling service
2-) Reboot
3-) Installing service
4-) Reboot
I am not entirely sure I am on the right track. I have Jenkins installed on a Mac - this was installed by someone else, but I gather this is a homebrew installation. It under /Users/$USER/.jenkins
The system does not show a jenkins user, which is something I have not seen in an instance of jenkins before. Jenkins is being used to run automated builds, but consistently cannot find commands that are available via terminal when I attempt them (ex: appium, node). I am trying to launch appium via the 'execute shell' step.
I am unsure where to go from here. Using a full directory path does not seem to help.
One thing to note is that Jenkins can successfully use the Android SDK it self-installed. It installed the Android SDK even though the box it is running on already had Android SDK installed. Jenkins doesn't seem to be aware of things happening outside of its own context.
Can anyone shed some insight on what the issue may be? I have spent quite a number of hours searching and cannot seem to resolve this on my own.
I am on a redhat linux box. I recently updated Jenkins to version 1.509 only to find that after doing so it has "forgotten" two of my jobs/projects. The jobs can still be found on my Jenkins machine under /var/lib/jenkins/jobs, but they no longer show up in the Jenkins GUI. I attempted to re-create them based off the configuration file I have, but I am not confident I have totally re-created the functionality they had.
I also tried to copy the job and or rename it hoping that would get jenkins to see it, but no luck. I had tried cp -r /var/lib/jenkins/jobs/JOB1 /var/lib/jenkins/jobs/JOB2. I also restarted the service a number of times. Finally I updated all of my plugins on the off chance that was somehow related.
So my question is "How can I get Jenkins to notice these jobs?" or failing that "can I run these jobs from in the terminal?"
NOTE: I am not discouraging others from upgrading Jenkins. After I upgraded Jenkins did complain about a number of things which I didn't pay enough attention to which I believe got me into this mess in the first place.
If I were you, I would try the Jenkins CLI (from $JENKINS_URL/cli) and use the create-job command and feed the job configuration file to the cli's stdin.
If that does not help, I would inspect Jenkins log files (you are saving stdout and stderr of Jenkins somewhere, right?) for any errors or clues. If the job failed to load because of some tag that you can guess is provided by a plugin, try to remove that part from the config file.
If that does not help, I would upgrade Jenkins. I think there might be some fixes related to this in the LTS version changelog since 1.509.
And above all... if I were you, I would start making backups of the job configuration files.
I regularly back up the global config.xml, all the job config.xml files and all the plugins. Using these I can set up my Jenkins from scratch. And I do that to set up a test instance where I try any plugin or Jenkins core upgrade. If I see no problems after running a few of the trickiest builds, I know I can upgrade the production instance with much more confidence.