• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • core

      Upgraded from 1.599 to 1.614.
      JNLP slaves now fail to connect with following error, where <HOST> is my actual host.
      SSH slaves are unaffected.

      May 20, 2015 10:57:51 AM hudson.remoting.jnlp.Main$CuiListener error
      SEVERE: https://<HOST>/tcpSlaveAgentListener/ is invalid: 404 Not Found
      java.lang.Exception: https://<HOST>/tcpSlaveAgentListener/ is invalid: 404 Not Found
      at hudson.remoting.Engine.run(Engine.java:214)

          [JENKINS-28499] tcpSlaveAgentListener not found

          James Howe created issue -

          James Howe added a comment -

          Downgraded to 1.611, and issue is resolved.

          James Howe added a comment - Downgraded to 1.611, and issue is resolved.

          James Howe added a comment -

          SSL is provided by an nginx proxy.

          James Howe added a comment - SSL is provided by an nginx proxy.

          Daniel Beck added a comment -

          Does 1.613 work correctly?

          Daniel Beck added a comment - Does 1.613 work correctly?

          Daniel Beck added a comment -

          Anything interesting in the Jenkins master log?

          Daniel Beck added a comment - Anything interesting in the Jenkins master log?

          Daniel Beck added a comment -

          No response to comment asking for additional information in several weeks, so resolving as Incomplete.

          Please reopen if this issue still occurs on the current Jenkins release, and provide the information requested in earlier comments. Also see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue for what information is typically useful in bug reports.

          Daniel Beck added a comment - No response to comment asking for additional information in several weeks, so resolving as Incomplete. Please reopen if this issue still occurs on the current Jenkins release, and provide the information requested in earlier comments. Also see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue for what information is typically useful in bug reports.
          Daniel Beck made changes -
          Resolution New: Incomplete [ 4 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 163340 ] New: JNJira + In-Review [ 197175 ]

          After an update this issue re-appeared, in our special configuration

          Jenkins 2.32.2
          Libvirt Plugin with 8 virtual machines at one and 4 times 2 virtual machines at 4 more real servers
          We suffer from issue 32118 (https://issues.jenkins-ci.org/browse/JENKINS-32118), therefore we added the following Java option at our startup script: \"-Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self'; style-src 'self';\"

          After a restart, all our nodes stay offline (the virtual machines get started), because of this error on the clients

          Andreas Tscharner added a comment - After an update this issue re-appeared, in our special configuration Jenkins 2.32.2 Libvirt Plugin with 8 virtual machines at one and 4 times 2 virtual machines at 4 more real servers We suffer from issue 32118 ( https://issues.jenkins-ci.org/browse/JENKINS-32118 ), therefore we added the following Java option at our startup script: \"-Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-scripts; default-src 'none'; img-src 'self'; style-src 'self';\" After a restart, all our nodes stay offline (the virtual machines get started), because of this error on the clients
          Andreas Tscharner made changes -
          Resolution Original: Incomplete [ 4 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

            Unassigned Unassigned
            jameshowe James Howe
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: