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

Remoting : NioChannelHub is not currently running

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When We try to reconnect any windows slave it throws following exception.

      JNLP agent connected from /10.219.160.235
      <===[JENKINS REMOTING CAPACITY]===>Failed to establish the connection with the slave IB-TC-5
      java.io.IOException: NioChannelHub is not currently running
      at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:492)
      at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:351)
      at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:280)
      at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:290)
      at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36)
      at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52)
      at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120)
      at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63)
      at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57)
      at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31)
      at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156)

      We checked all the configuration on Windows slave. Everything looks perfect e.g JENKINS_HOME etc.

      If this happens for one slave then all the slaves which try to connect after shows the same error.
      There is only one workaround to fix this is to restart Jenkins and then everything falls in place.

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          What version of Jenkins is this?

          Show
          danielbeck Daniel Beck added a comment - What version of Jenkins is this?
          Hide
          itsvnay Vinay Shah added a comment -

          We are using Jenkins version 1.579, and intermittently observing similar issue.
          <===[JENKINS REMOTING CAPACITY]===>Failed to establish the connection ...<slave name>.
          java.io.IOException: NioChannelHub is not currently running
          at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446)
          ..

          Do we know the root cause of it? And how to address it without restarting the Jenkins server.

          Thanks,
          Vinay

          Show
          itsvnay Vinay Shah added a comment - We are using Jenkins version 1.579, and intermittently observing similar issue. <=== [JENKINS REMOTING CAPACITY] ===>Failed to establish the connection ...<slave name>. java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446) .. Do we know the root cause of it? And how to address it without restarting the Jenkins server. Thanks, Vinay
          Hide
          vishnudutt_yadav Vishnu Yadav added a comment -

          My windows slaves which are running as a service also shown at disconnected even though the service jenkins_slave running on slave. In node llog I get this -

          Can any one suggest pls?
          <===[JENKINS REMOTING CAPACITY]===>Failed to establish the connection with the SLAVENAME
          java.io.IOException: NioChannelHub is not currently running
          at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446)
          at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220)
          at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149)
          at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:159)
          at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36)
          at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52)
          at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120)
          at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63)
          at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57)
          at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31)
          at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156)

          Show
          vishnudutt_yadav Vishnu Yadav added a comment - My windows slaves which are running as a service also shown at disconnected even though the service jenkins_slave running on slave. In node llog I get this - Can any one suggest pls? <=== [JENKINS REMOTING CAPACITY] ===>Failed to establish the connection with the SLAVENAME java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:159) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:156)
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Hard to say anything. Does this issue still happen? If yes, upgrade to JNLP4 is probably the best first step.

          There were also some fixes in Remoting 3.x related to NioHub protection from runtime exceptions

          Show
          oleg_nenashev Oleg Nenashev added a comment - Hard to say anything. Does this issue still happen? If yes, upgrade to JNLP4 is probably the best first step. There were also some fixes in Remoting 3.x related to NioHub protection from runtime exceptions
          Hide
          pjdarton pjdarton added a comment -

          "it works for me"

          I know it's not much comfort if it doesn't work for you, but it does work.  FYI there's (now) lots of information on the plugin's wiki page regarding how to get Windows VMs to work.  Windows makes things non-trivial, but it's not a Jenkins bug or a vSphere plugin bug.

          Show
          pjdarton pjdarton added a comment - "it works for me" I know it's not much comfort if it doesn't work for you, but it does work.  FYI there's (now) lots of information on the plugin's wiki page regarding how to get Windows VMs to work.  Windows makes things non-trivial, but it's not a Jenkins bug or a vSphere plugin bug.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            khakunin manohar joshi
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: