[JIRA] [remoting] (JENKINS-31735) Remoting : NioChannelHub is not currently running

5 views
Skip to first unread message

manoharsj@gmail.com (JIRA)

unread,
Nov 25, 2015, 12:00:02 AM11/25/15
to jenkinsc...@googlegroups.com
manohar joshi created an issue
 
Jenkins / Bug JENKINS-31735
Remoting : NioChannelHub is not currently running
Issue Type: Bug Bug
Assignee: Kohsuke Kawaguchi
Components: remoting, vsphere-cloud-plugin, windows-slaves-plugin
Created: 25/Nov/15 4:59 AM
Environment: Master
Jenkins slave on Ubuntu 12.04

Slave
Windows 2008 R2 Server
JRE 1.8
Labels: remoting niochanelhub windows
Priority: Major Major
Reporter: manohar joshi

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.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

dbeck@cloudbees.com (JIRA)

unread,
Nov 26, 2015, 9:31:01 AM11/26/15
to jenkinsc...@googlegroups.com

vinayshah@hotmail.com (JIRA)

unread,
Mar 4, 2016, 1:35:01 PM3/4/16
to jenkinsc...@googlegroups.com

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

vishnudutt_yadav@outlook.com (JIRA)

unread,
Nov 24, 2016, 12:02:03 AM11/24/16
to jenkinsc...@googlegroups.com

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)

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

pjdarton@gmail.com (JIRA)

unread,
Sep 24, 2019, 5:42:03 AM9/24/19
to jenkinsc...@googlegroups.com
pjdarton closed an issue as Cannot Reproduce
 

"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.

Change By: pjdarton
Status: Open Closed
Assignee: Kohsuke Kawaguchi
Resolution: Cannot Reproduce
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages