java.io.IOException: Unexpected termination of the channel

Jenkins JIRA | Mac Cer | 3 years ago
  1. 0

    Hello, I am currently receiving this Error during builds. SEVERE: I/O error in channel <CHANNEL_NAME> java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This happens after the "Multi Configuration" Build ran successfully when Jenkins tries to archive the artifacts. The slave channel automatically reconnects but the build job is stuck indefinitely at the "archive artifacts" stage and has to be manually aborted. The slave channel in Question is a HP-UX B.11.31 ia64. A couple of important things to note: 1) This slave can also be used by an older jenkins instance running 1.431. 2) The Job being used was migrated from this old jenkins instance 3) The Job is a multi config job and builds successfully on all other architectures (SuSe, Solaris, Red-Hat) 4) The job runs successfully on the older jenkins instance! 5) There are no network issues responsible for the termination of the channel 6) Java issues on the slave are also not likely as I mentioned the exact same slave can be used without incident from the other jenkins instance Of course, I used a different FS root so that each jenkins instance could set up their own slave.jars etc. But other than that, the slave works without problems when building this job using the old jenkins instance but it will always fail on this slave during the "archive artifacts" stage of the build.

    Jenkins JIRA | 3 years ago | Mac Cer
    java.io.IOException: Unexpected termination of the channel
  2. 0

    Hello, I am currently receiving this Error during builds. SEVERE: I/O error in channel <CHANNEL_NAME> java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This happens after the "Multi Configuration" Build ran successfully when Jenkins tries to archive the artifacts. The slave channel automatically reconnects but the build job is stuck indefinitely at the "archive artifacts" stage and has to be manually aborted. The slave channel in Question is a HP-UX B.11.31 ia64. A couple of important things to note: 1) This slave can also be used by an older jenkins instance running 1.431. 2) The Job being used was migrated from this old jenkins instance 3) The Job is a multi config job and builds successfully on all other architectures (SuSe, Solaris, Red-Hat) 4) The job runs successfully on the older jenkins instance! 5) There are no network issues responsible for the termination of the channel 6) Java issues on the slave are also not likely as I mentioned the exact same slave can be used without incident from the other jenkins instance Of course, I used a different FS root so that each jenkins instance could set up their own slave.jars etc. But other than that, the slave works without problems when building this job using the old jenkins instance but it will always fail on this slave during the "archive artifacts" stage of the build.

    Jenkins JIRA | 3 years ago | Mac Cer
    java.io.IOException: Unexpected termination of the channel
  3. 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
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Jenkins slave terminated error message

    Google Groups | 3 years ago | Lily Fu
    java.io.IOException: Unexpected termination of the channel
  6. 0

    Unable to startup slave post master upgrade to 1.576

    Google Groups | 2 years ago | Sudhakar.Shanmugam
    java.io.IOException: Unexpected termination of the channel

  1. ex00 1 times, last 2 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:2553)
    2. java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
    3. java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
    3 frames
  3. Hudson :: Remoting Layer
    SynchronousCommandTransport$ReaderThread.run
    1. hudson.remoting.Command.readFrom(Command.java:92)
    2. hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
    3. hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
    3 frames