java.io.IOException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • 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.
    via by Mac Cer,
  • 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.
    via by Mac Cer,
  • Jenkins slave terminated error message
    via by Lily Fu,
  • Unable to startup slave post master upgrade to 1.576
    via by Sudhakar.Shanmugam,
  • Error with termination of remote channel
    via by chris hemphill,
  • Communication problem with slave is not notified by email
    via by Rui Fernando Hayashi,
  • Windows XP slave agent launch failure on 1.519
    via by Jonathan Daugherty,
  • difficulty connecting to Mac slave
    via by Dan Tenenbaum,
    • 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)

    Users with the same issue

    Unknown visitor
    Unknown visitor1 times, last one,
    Unknown UserUnknown User
    19 times, last one,
    Unknown visitor
    Unknown visitor1 times, last one,
    ex00ex00
    1 times, last one,
    eti22eti22
    1 times, last one,
    10 more bugmates