Status: Resolved (View Workflow)
On some of my build slaves, the java slave runs just fine, on others it dies very shortly (within a second or two) after starting. Hudson says about it:
Connection was broken
java.io.IOException: Unexpected termination of the channel
Caused by: java.io.EOFException
The log for it says:
Connecting to 10.8.3.81
Verifying that java exists
java full version "JRE 1.6.0 IBM Linux build pxa6460sr7-20091215_02 (SR7)"
Launching slave agent
<===[HUDSON REMOTING CAPACITY]===>Slave.jar version: 1.372
This is a Unix slave
I can start the slave manually and it will stay running:
[busy icon spinning]
It will stay running if I start it manually:
- ssh -i ~hudson/.euca/hudson.priv email@example.com java -jar /tmp/slave.jar
<===[HUDSON REMOTING CAPACITY]===>[encyrpted/encoded data removed for privacy]
[stays running, so in another terminal:]
- ssh -i ~hudson/.euca/hudson.priv firstname.lastname@example.org ps -ef | grep java
root 2766 2761 3 12:53 ? 00:00:01 java -jar /tmp/slave.jar
Any ideas how to go about figuring out why it's dying so quickly on only some of my build slaves?
- is related to
JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
|Field||Original Value||New Value|
This issue is related to
For us, the cause of this error was our build slaves (VMs) running out of memory and self-rebooting.
No response from the reporter, so resolving as incomplete.
As Brian has said, the slaves may have OOM.
|Resolution||Incomplete [ 4 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Workflow||JNJira [ 137614 ]||JNJira + In-Review [ 187589 ]|
any news? does upgrading to a recent version of Jenkins solves the problem?