![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
core, ssh-slaves |
|
Created:
|
12/Dec/13 1:32 PM
|
|
Description:
|
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.
|
|
Environment:
|
Red Hat Enterprise Linux Server release 6.4 (Santiago)
|
|
Project:
|
Jenkins
|
|
Labels:
|
slave
exception
ssh
|
|
Priority:
|
![Blocker]() Blocker
|
|
Reporter:
|
Mac Cer
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
