We updated three plugins for jenkins. After they were updated jenkins will not start. We get jenkins.service: main process exited, code=exited, status=5/NOTINSTALLED and jenkins.service: main process exited, code=exited, status=1/FAILURE. Any ideas what this error could be or perhaps suggest a starting place to find the issue?
It turns out the issue was that somehow installing the plugin update removed JAVA from the system path.
Related
I have a deprecated Jenkins plugin installed (WMI Windows Agents Plugin, v1.8.1), and I'm trying to uninstall it.
Problem
When I uninstall the plugin from the Jenkins web UI, it gets stuck at "Uninstallation pending" no matter how long I wait.
What I Tried
When I do a safe restart after a long wait, the UI shows that the plugin is still installed, as if I had not attempted an uninstall. I also tried disabling the plugin before attempting another uninstall—still stuck at pending uninstallation. Doing a yet another safe-restart after a long wait doesn't work either.
After you click uninstall, while the status is "Uninstallation pending",
click on Available Plugins and without selecting any plugins click on Download now and Install after Restart.
For some reason this completes the uninstallation
I initially couldn't uninstall the WMI Windows Agents Plugin on Jenkins 2.375.2 either.
This comment on JENKINS-70454 suggested that upgrading to Jenkins 2.375.3 might help, and indeed:
I could uninstall the plugin as expected after upgrading.
FWIW: I assume that hudson.PluginManager#considerDetachedPlugin was somehow responsible for keeping that plugin, as
journalctl -ujenkins | grep windows
showed me
hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/lib/jenkins/plugins/windows-slaves.jpi
after every reboot (but to be honest, I don't know much about detached plugins).
What is difference between installation jenkins plugin with restart and without restart.
Can I install a plugin with restart when other builds are running?.
The main difference between 'with restart' and 'without restart' plugin installation is that you cannot upgrade or uninstall plugins without restart (because of the architectural choice made in Jenkins).
So, new plugin can be installed without restart (and when other builds are running as well).
For details, see the official post from Kohsuke Kawaguchi's blog.
I use HPE Automation Tool plugin in Jenkins to run UFT(CI/CD). In the configuration I have put a timeout of 36000 sec(10 hours). Ideally UFT should terminate after 10 hours but it is not terminating and keeps on running.
At the same time if I change the timeout configuration to 2 minutes it works like a charm. But the project that I am working on needs that 10 hours timeout configuration.
UFT version 14.03 is installed in a windows server and the scripts run there.
HPE Automation Tool Plugin version used is 5.2.
Can someone please provide me their inputs, what may the issue?
The plugin uses the QuickTest.Application COM Object to start and control the Test Robot(UFT). I had many issues with UFT running more than 2 hours without any restart (I had my own script driving it) - so I wouldn't assume it is an issue of the Plug-in but of UFT. You could try investigate it further but hey let me tell you my tests:
Have some long tests and run them directly from UFT (Do they run for 10 hours without restart? - mine didn't)
Do the same but drive the execution via a script.
If all those 2 is OK, well then you can assume it is the Plug-in, but again my personal experience with the 2 ways mentioned above led me to the conclusion that it is UFT and not the driver scripts.
What I can propose as an alternative:
Have milestones (Save some Item IDs, critical data somewhere (DB, Files) - restart UFT regularly and reload data stored in the milestone
I just updated our Jenkins installation to version 2.59 (from 2.53) for which I had to install Java 8 (also on the agents) since it is used by 2.54 and later.
The Jenkins came up again and seemed to be working but there is a problem when checking out Git repositories on any of our projects. Jenkins seems to hang:
Fetching changes from the remote Git repository
Cleaning workspace
...and that's it.
When looking into the Jenkins logs I see the following exception:
May 08, 2017 11:34:47 AM hudson.init.impl.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler uncaughtException
SEVERE: A thread (Thread-17/172) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.
java.lang.NullPointerException
at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:447)
at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:790)
at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:502)
at java.lang.Thread.run(Thread.java:745)
What causes the problem here? How do I fix this?
I have started to use jenkins to build my project. I build my project yesterday and it took me 26 sec to build my flex sdk. I build the same file today and it took me 19 min to build the same file. Could anyone explain how this is happening ? I am trying to optimize my build scripts and I am not able to understand if there is something wrong with my build file or with jenkins.
This is the build that took 19 min
This is the build that took 26 sec
This is my second build running after the first one and the part of MXMLC Compiles took around 27 min out of the total 34 min
Is this happening consistently? Was your system perhaps overloaded when the second build occurred? e.g. A backup running or some CPU-intensive process?
If you install the Timestamper plugin for Jenkins, you will be able to see which parts are taking longer.
Is your Jenkins system on a box all by itself? Is this on Windows?
On Windows systems, files can become locked for all sorts of reasons. I've had problems just because I had a Windows Explore window open up to a directory where Jenkins wanted to overlay a file. Jenkins froze up until I closed my Explorer window. Could this be an issue?
Where is the task being delayed? Install the Jenkins timestamper plugin, and that'll show you what tasks are taking so long. From there, you can narrow down your investigation a bit.