Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16346

Upgrade to Jenkins ver. 1.499 breaks master/slave connection

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • core, slave-setup-plugin
    • None
    • Linux bambpmsauto 2.6.34.7-0.4-desktop #1 SMP PREEMPT 2010-10-07 19:07:51 +0200 x86_64 x86_64 x86_64 GNU/Linux

      After the upgrade all our Windows slaves could not be reached:

      C:\jenkins>java -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/compu
      ter/vmbam04.eur.ad.sag/slave-agent.jnlp
      Failing to obtain http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag
      /slave-agent.jnlp
      java.io.IOException: Failed to load http://bambpmsauto.eur.ad.sag:8080/computer/
      vmbam04.eur.ad.sag/slave-agent.jnlp: 403 Forbidden
      at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:228)
      at hudson.remoting.Launcher.run(Launcher.java:190)
      at hudson.remoting.Launcher.main(Launcher.java:166)
      Waiting 10 seconds before retry
      Failing to obtain http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag
      /slave-agent.jnlp

      I also tried headless slave:

      CouldNotLoadArgumentException[ Could not load file/URL specified: http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp]
      at com.sun.javaws.Main.launchApp(Unknown Source)
      at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
      at com.sun.javaws.Main$1.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

      java.io.IOException: Server returned HTTP response code: 403 for URL: http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp
      at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
      at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
      at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source)
      at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
      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$1.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

      This must be a regression of some kind because all the slaves were fine before the upgrade of the version (we were on 1.497 as 1.498 had similar problems)

          [JENKINS-16346] Upgrade to Jenkins ver. 1.499 breaks master/slave connection

          alexlombardi added a comment -

          I was able to overcome this issue by giving the Anonymous user connection privilides in the Configure Global Security tab, then restarting the system. It's a terrible kludge, and I am hoping they find a way to make this unnecessary going forward.

          alexlombardi added a comment - I was able to overcome this issue by giving the Anonymous user connection privilides in the Configure Global Security tab, then restarting the system. It's a terrible kludge, and I am hoping they find a way to make this unnecessary going forward.

          sogabe added a comment -

          use -jnlpCredentials username:password option.

          sogabe added a comment - use -jnlpCredentials username:password option.

          I will try both options now but will hold off that version for the moment

          If I have to explicitly pass -jnlpCredentials username:password then I guess Jenkins needs to generate the proper command line when configuring the slaves. I mean those:
          Run from slave command line:

          javaws http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp
          Or if the slave is headless:

          java -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp

          We have quite a lot of slaves and it will take a while to go tru all of them for reconfiguration

          Vassilena Treneva added a comment - I will try both options now but will hold off that version for the moment If I have to explicitly pass -jnlpCredentials username:password then I guess Jenkins needs to generate the proper command line when configuring the slaves. I mean those: Run from slave command line: javaws http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp Or if the slave is headless: java -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp We have quite a lot of slaves and it will take a while to go tru all of them for reconfiguration

          Jesse Glick added a comment -

          Duplicate I think. You need appropriate authentication to connect a slave using JNLP.

          Jesse Glick added a comment - Duplicate I think. You need appropriate authentication to connect a slave using JNLP.

            kohsuke Kohsuke Kawaguchi
            vassilena Vassilena Treneva
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: