Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Duplicate
-
Jenkins 1.580.1 on Ubuntu 14.04 with slaves connected via JLNP.
Description
Since the former major LTS release I experience a kinda problematic problem with our Jenkins instance. Whenever the master is stopped (shutdown) with active connections to slaves, the JLNP client on the slaves stops working with the message: "Unable to launch the application". This was not the case before, so the client application was still running and reconnected once the master was back online.
With the current behavior I have to step through all the >60 slave nodes, and start the JLNP client manually.
Steps:
1. Download Jenkins 1.580.1 and run it
2. Setup a dumb slave via Java Web Start
3. Connect the slave via the same machine
4. Stop the master
After step 4 the JLNP client should stay open, waiting for the master being online again. But it fails with the above message and the following stack:
Exception: CouldNotLoadArgumentException[ Could not load file/URL specified: /tmp/javawJ3YZLo] at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main.access$000(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Thread.java:744) Wrapped Exception: java.io.FileNotFoundException: /tmp/javawJ3YZLo (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:146) at java.io.FileInputStream.<init>(FileInputStream.java:101) at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source) at com.sun.javaws.Main.launchApp(Unknown Source) at com.sun.javaws.Main.continueInSecureThread(Unknown Source) at com.sun.javaws.Main.access$000(Unknown Source) at com.sun.javaws.Main$1.run(Unknown Source) at java.lang.Thread.run(Thread.java:744)
Attachments
Issue Links
- is blocking
-
JENKINS-19055 In case of connection loss, slave JVM should restart itself if it can
-
- Resolved
-
- is duplicated by
-
JENKINS-25895 GUI-mode JNLP slave does not reconnect after Jenkins restart (UnixSlaveRestarter broken)
-
- Resolved
-
-
JENKINS-25855 Mac agents fail reconnect when jenkins service restarted
-
- Resolved
-
- is related to
-
JENKINS-24272 jnlp slaves fail to reconnect when master is restarted
-
- Resolved
-
So I already tried the way via the terminal by connecting the slave via javaws, but the client dies the same way when the master gets shutdown. So this is not a workaround. And this only happens on Linux and OS X. I re-tested with Windows and I cannot observe this behavior. There the client re-connects successfully once the master is back online.
I'm not that happy with the 'java' workaround given that it would require us to update all of our 70 machines, by downloading the slave.jar file first. Also not sure how often it was required to re-download it given updates to that file. I'm working on a puppet configuration for us but that is not ready yet.