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

Agent tunnel connection issues after ugrading Jenkins to 2.191

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: remoting
    • Labels:
    • Environment:
      Windows 7
      Jenkins 2.191
      Oracle JRE jre1.8.0_171
      AdoptOpenJDK jre-8.0.222.10-hotspot
    • Similar Issues:
    • Released As:
      Remoting 3.35

      Description

      After updating Jenkins master to 2.191 windows slave thows following exception:

      Aug 27, 2019 8:41:10 AM hudson.remoting.jnlp.Main createEngine
      INFORMATION: Setting up agent: spsde05ws016
      Aug 27, 2019 8:41:10 AM hudson.remoting.jnlp.Main$CuiListener <init>
      INFORMATION: Jenkins agent is running in headless mode.
      Aug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main createEngine
      WARNUNG: Certificate validation for HTTPs endpoints is disabled
      Aug 27, 2019 8:41:11 AM hudson.remoting.Engine startEngine
      INFORMATION: Using Remoting version: 3.34
      Aug 27, 2019 8:41:11 AM hudson.remoting.Engine startEngine
      WARNUNG: No Working Directory. Using the legacy JAR Cache location: C:\Windows\system32\config\systemprofile\.jenkins\cache\jars
      Aug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main$CuiListener status
      INFORMATION: Locating server among [https://tools.xxxxx.local/devjenkins/]
      Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver openURLConnection
      WARNUNG: HTTPs certificate check is disabled for the endpoint.
      Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
      INFORMATION: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
      Aug 27, 2019 8:41:11 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
      INFORMATION: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check
      Aug 27, 2019 8:41:11 AM hudson.remoting.jnlp.Main$CuiListener error
      SCHWERWIEGEND: For input string: ""
      java.lang.NumberFormatException: For input string: ""
      	at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
      	at java.lang.Integer.parseInt(Integer.java:592)
      	at java.lang.Integer.parseInt(Integer.java:615)
      	at org.jenkinsci.remoting.engine.HostPort.splitHostPort(HostPort.java:25)
      	at org.jenkinsci.remoting.engine.HostPort.<init>(HostPort.java:8)
      	at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:329)
      	at hudson.remoting.Engine.innerRun(Engine.java:529)
      	at hudson.remoting.Engine.run(Engine.java:490)
      

       

       

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            https://github.com/jenkinsci/jenkins/pull/4186 for a temporary regression fix until the new version of Remoting is ready

            Show
            oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/jenkins/pull/4186  for a temporary regression fix until the new version of Remoting is ready
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            A workaround has been released in 2.193. We hope to have a Remoting fix in the next releases

            Show
            oleg_nenashev Oleg Nenashev added a comment - A workaround has been released in 2.193. We hope to have a Remoting fix in the next releases
            Hide
            jthompson Jeff Thompson added a comment -

            The problem turned out to be related to tunneling configurations, when the tunnel HOST:PORT is missing the HOST and / or PORT specification. In my change for Remoting 3.34, I had missed some magic whereby the values are filled in from prior sources. Remoting 3.3.5 restores these configuration paths / options and retains the new capabilities introduced in 3.34. I couldn't find any connection between this issue and the Windows platform, as the original title stated, so I've changed the title to better reflect the actual issue.

            Show
            jthompson Jeff Thompson added a comment - The problem turned out to be related to tunneling configurations, when the tunnel HOST:PORT is missing the HOST and / or PORT specification. In my change for Remoting 3.34, I had missed some magic whereby the values are filled in from prior sources. Remoting 3.3.5 restores these configuration paths / options and retains the new capabilities introduced in 3.34. I couldn't find any connection between this issue and the Windows platform, as the original title stated, so I've changed the title to better reflect the actual issue.
            Hide
            dmazuronak Dzianis Mazuronak added a comment -

            Update to Jenkins version 2.194 was successful. Thank you very much for this fix.

            Show
            dmazuronak Dzianis Mazuronak added a comment - Update to Jenkins version 2.194 was successful. Thank you very much for this fix.
            Hide
            jthompson Jeff Thompson added a comment -

            Great! I'm glad that solved it for you.

            Show
            jthompson Jeff Thompson added a comment - Great! I'm glad that solved it for you.

              People

              • Assignee:
                jthompson Jeff Thompson
                Reporter:
                dmazuronak Dzianis Mazuronak
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: