[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave

Mon, 06 May 2013 06:04:14 -0700

Having the same issue, reproduced at every build for a given slave (with nothing relevant in its logs), I tried to disconnect and reconnect the slave:

[05/06/13 14:06:04] Launching slave agent
$ ssh slavedns java -jar ~/bin/slave.jar
<===[JENKINS REMOTING CAPACITY]===<===[JENKINS REMOTING CAPACITY]===>>channel started
channel started
Slave.jar version: 2.22
This is a Unix slave
Slave.jar version: 2.22
This is a Unix slave
Copied maven-agent.jar
Copied maven3-agent.jar
Copied maven3-interceptor.jar
Copied maven-agent.jar
Copied maven-interceptor.jar
Copied maven2.1-interceptor.jar
Copied plexus-classworld.jar
Copied maven3-agent.jar
Copied maven3-interceptor.jar
Copied classworlds.jar
Copied maven-interceptor.jar
Copied maven2.1-interceptor.jar
Copied plexus-classworld.jar
Copied classworlds.jar
Evacuated stdout
Evacuated stdout
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins
(...)java.lang.IllegalStateException: Already connected
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:459)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339)
	at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Connection terminated
channel stopped
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins
(...)java.lang.NullPointerException
	at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:32)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:471)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339)
	at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
channel stopped
Connection terminated

Then the slaved successfully reconnected itself.



It appeared there was looping thread consuming 100% CPU. Killing the process solved the issue. 

Strangely, some system and Java commands were not working (ps, cat, less, jstack, trace, ...) until it has been killed, whereas other commands worked (top, jps, renice, kill, ...). That could explain the weird Jenkins 4s timeout log (java.util.concurrent.TimeoutException: Ping started on 1367743028681 hasn't completed at 1367743268682): the system was partially frozen and with really unstable response times.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to