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

Jenkins Slaves do not connect after update from version 2.95 to version 2.99

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Blocker Blocker
    • core, remoting
    • None

      After having installed Jenkins Version 2.99, none of my slaves did connect to the server anymore. Even a restart of the java script on the slave did not help.

      Workaround: Update Remoting on the agent side to 3.15

          [JENKINS-48754] Jenkins Slaves do not connect after update from version 2.95 to version 2.99

          Michael M. created issue -
          Oleg Nenashev made changes -
          Assignee New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Component/s New: core [ 15593 ]
          Component/s New: remoting [ 15489 ]
          Component/s Original: slave-utilization [ 17575 ]

          Hi,

          I've exactly the same problem.

           

          Agent log :

          janv. 02, 2018 3:05:49 PM hudson.remoting.jnlp.Main createEngine
          INFO: Setting up slave: Windows Slave
          janv. 02, 2018 3:05:49 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
          INFO: Using D:\Jenkins\remoting as a remoting work directory
          Both error and output logs will be printed to D:\Jenkins\remoting
          janv. 02, 2018 3:05:49 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
          INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
          janv. 02, 2018 3:06:00 PM hudson.remoting.jnlp.GuiListener$1 run
          INFO: Connecting to ciserver:8081 (retrying:2)
          java.io.IOException: Failed to connect to ciserver:8081
          {{ at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242)}}
          {{ at hudson.remoting.Engine.connect(Engine.java:686)}}
          {{ at hudson.remoting.Engine.innerRun(Engine.java:547)}}
          {{ at hudson.remoting.Engine.run(Engine.java:469)}}
          Caused by: java.net.ConnectException: Connection refused: connect
          {{ at sun.nio.ch.Net.connect0(Native Method)}}
          {{ at sun.nio.ch.Net.connect(Unknown Source)}}
          {{ at sun.nio.ch.Net.connect(Unknown Source)}}
          {{ at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)}}
          {{ at java.nio.channels.SocketChannel.open(Unknown Source)}}
          {{ at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203)}}
          {{ ... 3 more}}

           

          And in master log nothing appears...

           

          Regards,

          Bruno.

          Bruno Laoueillé added a comment - Hi, I've exactly the same problem.   Agent log : janv. 02, 2018 3:05:49 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: Windows Slave janv. 02, 2018 3:05:49 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir INFO: Using D:\Jenkins\remoting as a remoting work directory Both error and output logs will be printed to D:\Jenkins\remoting janv. 02, 2018 3:05:49 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] janv. 02, 2018 3:06:00 PM hudson.remoting.jnlp.GuiListener$1 run INFO: Connecting to ciserver:8081 (retrying:2) java.io.IOException: Failed to connect to ciserver:8081 {{ at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:242)}} {{ at hudson.remoting.Engine.connect(Engine.java:686)}} {{ at hudson.remoting.Engine.innerRun(Engine.java:547)}} {{ at hudson.remoting.Engine.run(Engine.java:469)}} Caused by: java.net.ConnectException: Connection refused: connect {{ at sun.nio.ch.Net.connect0(Native Method)}} {{ at sun.nio.ch.Net.connect(Unknown Source)}} {{ at sun.nio.ch.Net.connect(Unknown Source)}} {{ at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)}} {{ at java.nio.channels.SocketChannel.open(Unknown Source)}} {{ at org.jenkinsci.remoting.engine.JnlpAgentEndpoint.open(JnlpAgentEndpoint.java:203)}} {{ ... 3 more}}   And in master log nothing appears...   Regards, Bruno.

          Oleg Nenashev added a comment -

          Which agent version do you use?

          Oleg Nenashev added a comment - Which agent version do you use?

          For me : I've uninstalled my Windows Service agent and click again on "Launch agent from browser". I guess it's the latest with this method ?

          In the agent.jar manifest file it's written 3.15 for the version...

          Bruno Laoueillé added a comment - For me : I've uninstalled my Windows Service agent and click again on "Launch agent from browser". I guess it's the latest with this method ? In the agent.jar manifest file it's written 3.15 for the version...

          Oleg Nenashev added a comment - - edited

          My first guess is that Remoting receiver thread is not active due to whatever reason. Or maybe not, the HTTPs receiver should be working

          Please provide...
          1) Jenkins log, starting from the master startup
          2) Thread dump for the master

          If you could just generate a bundle using https://wiki.jenkins.io/display/JENKINS/Support+Core+Plugin, it would be great

          Oleg Nenashev added a comment - - edited My first guess is that Remoting receiver thread is not active due to whatever reason. Or maybe not, the HTTPs receiver should be working Please provide... 1) Jenkins log, starting from the master startup 2) Thread dump for the master If you could just generate a bundle using https://wiki.jenkins.io/display/JENKINS/Support+Core+Plugin , it would be great
          Oleg Nenashev made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]
          Bruno Laoueillé made changes -
          Attachment New: support_2018-01-02_17.45.19.zip [ 41006 ]
          Bruno Laoueillé made changes -
          Attachment New: master-logs.txt [ 41007 ]

            oleg_nenashev Oleg Nenashev
            michaelmotteler Michael M.
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: