[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Jesse Glick updated JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped Change By: Jesse Glick (03/Dec/14 8:14 PM) Labels: jnlpregressionslave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped So I also tried to install jenkins as service via the JNLP connection window, but that failed on OS X. So it looks like we really have to use the 'java' command for now on both affected platforms. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped But isn't that the headless mode? The tests we are running require a GUI. That's why we used the JLNP method so far. Would that not be necessary? Means we could write our own little daemon (script) to ensure that slave.jar is the current version and (re-)starts the slave if it is not running? I tested it with the `java` command and it works at least on Ubuntu. I will also have to test on Windows, but would like to know more about my above question first. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Daniel Beck commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped Not sure. All my Linux slaves are headless, but on Windows, the java started from cmd gets UI access. It's just the launch method not requiring a UI. but would like to know more about my above question first. How long can it possibly take to try and see what happens when a slave is launched this way? Please remember that there are many more users with questions than developers or users with the time to answer others' questions. I'd make sure to start it from a terminal in an interactive session though, so the process inherits the UI environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Richard Mortimer commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped I suspect that the changes that made this happen are related to those that caused JENKINS-24272 but it is not the same failure. Namely between 1.554.3 and 1.565.1 Jenkins now restarts the whole slave process when the master restarts (to ensure that any memory leaks are gone) rather than just reconnecting to the master. Now it looks to me that JWS is deleting the downloaded file (slave.jar I would guess) and hence when the slave tries to restart it cannot find the executed file and hence the error seen occurs. This delete downloaded file behaviour is typical for what a web launched application would do to stop filling up the disk with unneeded junk. That might just be at odds with the whole restart JVM (as opposed to reconnect to master) approach. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Daniel Beck commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped To clarify, the Linux slave has a UI and you're launching it using the Start button on the slave's index page on the Jenkins UI? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped That is correct, yes. We don't have it running as service via upstart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Daniel Beck commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped Please try the workaround of using the java ... command line call in a terminal on the slave instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin created JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Nov/14 1:27 PM 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) Environment: Jenkins 1.580.1 on Ubuntu 14.04 with slaves connected via JLNP. Project: Jenkins Priority: Critical Reporter: Henrik Skupin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped A quick regression check has been shown that this regression started between 1.554.3 and 1.565.1. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped This is a regression in v1.559 (https://jenkins-ci.org/changelog#v1.559) and totally smells like an unwanted behavior caused by https://issues.jenkins-ci.org/browse/JENKINS-19055 May this only be a problem if the JLNP client it's not installed as a service? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25490) Slave JLNP client stops working with Unable to launch the application when master is stopped
Henrik Skupin commented on JENKINS-25490 Slave JLNP client stops working with Unable to launch the application when master is stopped May be a dupe of #24272? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
