java.io.IOException: Unexpected termination of the channel

Jenkins JIRA | Brian J Murrell | 6 years ago
  1. 0

    User list for the Hudson continuous build server.

    gmane.org | 7 months ago
    java.io.IOException: Unexpected termination of the channel
  2. 0

    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 at hudson.remoting.Channel$ReaderThread.run(Channel.java:881) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Channel$ReaderThread.run(Channel.java:875) 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)" Copying slave.jar Launching slave agent <===[HUDSON REMOTING CAPACITY]===>Slave.jar version: 1.372 This is a Unix slave Copied maven-agent.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar 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 root@10.8.3.81 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 root@10.8.3.81 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?

    Jenkins JIRA | 6 years ago | Brian J Murrell
    java.io.IOException: Unexpected termination of the channel
  3. 0

    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 at hudson.remoting.Channel$ReaderThread.run(Channel.java:881) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Channel$ReaderThread.run(Channel.java:875) 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)" Copying slave.jar Launching slave agent <===[HUDSON REMOTING CAPACITY]===>Slave.jar version: 1.372 This is a Unix slave Copied maven-agent.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar 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 root@10.8.3.81 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 root@10.8.3.81 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?

    Jenkins JIRA | 6 years ago | Brian J Murrell
    java.io.IOException: Unexpected termination of the channel
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JENKINS-6817] FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel - Jenkins JIRA

    jenkins-ci.org | 11 months ago
    hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
  6. 0

    [JENKINS-11130] java.io.IOException: Unexpected termination of the channel - SEVERE: I/O error in channel Chunked connection when using jenkins-cli.jar (works on older Hudson version) - Jenkins JIRA

    jenkins-ci.org | 3 weeks ago
    hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel

  1. ex00 1 times, last 3 weeks ago
  2. eti22 1 times, last 1 month ago
  3. pnaranja 1 times, last 5 months ago
8 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.io.EOFException

    No message provided

    at java.io.ObjectInputStream$BlockDataInputStream.peekByte()
  2. Java RT
    ObjectInputStream.readObject
    1. java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570)
    2. java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314)
    3. java.io.ObjectInputStream.readObject(ObjectInputStream.java:368)
    3 frames
  3. Hudson :: Remoting Layer
    Channel$ReaderThread.run
    1. hudson.remoting.Channel$ReaderThread.run(Channel.java:875)
    1 frame