Re: Unexpected termination of the channel
Hi Did you able to resolve this issue. I'm facing the same issue. Thanks, Madhawa On Thursday, May 5, 2016 at 5:51:39 PM UTC+5:30, Jordi Andreu Miralles wrote: > > Hi, > > we are suffering in the last days timeouts and sudden death of our slave > intances in Amazon EC2. > > I'm observed that the Response Time in Node list page is over 3ms and > later we get "Time out for last n try" > > Finally in the node status page we get an Exception: > > 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$PeekInputStream.readFully(ObjectInputStream.java:2325) > at > java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) > at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) > at java.io.ObjectInputStream.(ObjectInputStream.java:299) > at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) > at > hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) > at > hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) > > Jenkins version: 1.651.1 > amazon ec2 plugin version: 1.31 > > Any idea how to solve this problem? > > Best regards, > > Jordi > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/29c59c77-e1a8-44d6-a286-c60803671010%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins slave (EC2 AWS plugin) fails occasionally when build takes too long with error "Caused: java.io.IOException: Unexpected termination of the channel"
I added ClientAliveInterval and ClientAliveCountMax parameters to the sshd
configuration on our Jenkins agents to help prevent disconnects. I also
removed the monitoring plugin since we didn't use it. I had noticed
JavaMelody errors in the Jenkins log file at the same time the Jenkins
agent disconnected.
On Monday, September 11, 2017 at 6:32:30 PM UTC-7, K S wrote:
>
> I have Jenkins configured to launch EC2 instances (via AWS plugin) to
> execute a build.
> The actual build steps use the Execute Shell method, and launch ansible
> scripts.
>
> I find that if the ansible script runs for too long, the Jenkins slave on
> the EC2 system goes down.
> The Jenkins GUI shows this error:
>
> Connection was broken
>
> java.io.EOFException
> at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2638)
> at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3113)
> at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853)
> at java.io.ObjectInputStream.(ObjectInputStream.java:349)
> at
> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> at
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
> Caused: java.io.IOException: Unexpected termination of the channel
> at
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)
>
>
>
>
> Some googling lead to this page:
> https://wiki.jenkins.io/display/JENKINS/Remoting+issue
> It suggests I check these log files:
> 1) connection logs on master - I checked these, and they have the same
> information as stack trace.
> 2) slave logs - I do not know where to find these. *The locations
> suggested do not exist on my slave.*
>
> I even inspected the files that the slave java process opens, and the only
> file that seems like a log file ends up being empty:
>
> ubuntu@ip-172-31-93-175:~/support$ ps auxww | grep java | grep slave
> ubuntu25235 8.0 0.5 12211452 157616 ? Ssl 22:23 0:05 java
> -jar /tmp/slave.jar
> ubuntu@ip-172-31-93-175:~/support$ sudo lsof | grep 25235 | grep -i log |
> awk '{print $NF}' | sort | uniq
> /home/ubuntu/support/all_2017-09-11_22.23.07.log
> ubuntu@ip-172-31-93-175:~/support$ cat
> /home/ubuntu/support/all_2017-09-11_22.23.07.log
> ubuntu@ip-172-31-93-175:~/support$
>
>
>
> Has anyone run into this issue or know how or where to find the java slave
> logs?
>
> Thanks so much.
>
>
> *VERSION INFO:*
> *Master:*
> Jenkins ver. 2.60.2
> Java: openjdk version "1.8.0_131"
>
> *Build node:*
> Launched via: AWS plugin:
> https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin (latest version)
>
> Ec2 instance running Ubuntu 14.04 and Java 8:
> ubuntu@ip-172-31-93-175:~$ cat /etc/*release* | grep VERSION
> VERSION="14.04.5 LTS, Trusty Tahr"
> VERSION_ID="14.04"
> ubuntu@ip-172-31-93-175:~$ *java -version*
> java version "1.8.0_144"
> Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
>
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/1c82b22f-c02c-4f01-9efb-6093bf8dbcf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Jenkins slave (EC2 AWS plugin) fails occasionally when build takes too long with error "Caused: java.io.IOException: Unexpected termination of the channel"
The ansible script is minimal and runs a yocto build process.
Are you suggesting ansible interacting with this plugin could be a problem?
On Tuesday, September 12, 2017 at 12:50:26 PM UTC-4, Joshua Noble wrote:
>
> I've had great success with the EC2 plugin. Might I suggest using
> Hashicorp Packer to build an AMI, and have the EC2 plugin launch that AMI?
> That will let you remove Ansible (or any provision tool) out of the
> equation and save on agent provisioning time. I know that when our cluster
> scales up another node using the EC2 plugin, we generally need that node
> online ASAP.
>
> On Monday, September 11, 2017 at 9:32:30 PM UTC-4, K S wrote:
>>
>> I have Jenkins configured to launch EC2 instances (via AWS plugin) to
>> execute a build.
>> The actual build steps use the Execute Shell method, and launch ansible
>> scripts.
>>
>> I find that if the ansible script runs for too long, the Jenkins slave on
>> the EC2 system goes down.
>> The Jenkins GUI shows this error:
>>
>> Connection was broken
>>
>> java.io.EOFException
>> at
>> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2638)
>> at
>> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3113)
>> at
>> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853)
>> at java.io.ObjectInputStream.(ObjectInputStream.java:349)
>> at
>> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
>> at
>> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
>> at
>> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
>> Caused: java.io.IOException: Unexpected termination of the channel
>> at
>> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)
>>
>>
>>
>>
>> Some googling lead to this page:
>> https://wiki.jenkins.io/display/JENKINS/Remoting+issue
>> It suggests I check these log files:
>> 1) connection logs on master - I checked these, and they have the same
>> information as stack trace.
>> 2) slave logs - I do not know where to find these. *The locations
>> suggested do not exist on my slave.*
>>
>> I even inspected the files that the slave java process opens, and the
>> only file that seems like a log file ends up being empty:
>>
>> ubuntu@ip-172-31-93-175:~/support$ ps auxww | grep java | grep slave
>> ubuntu25235 8.0 0.5 12211452 157616 ? Ssl 22:23 0:05 java
>> -jar /tmp/slave.jar
>> ubuntu@ip-172-31-93-175:~/support$ sudo lsof | grep 25235 | grep -i log
>> | awk '{print $NF}' | sort | uniq
>> /home/ubuntu/support/all_2017-09-11_22.23.07.log
>> ubuntu@ip-172-31-93-175:~/support$ cat
>> /home/ubuntu/support/all_2017-09-11_22.23.07.log
>> ubuntu@ip-172-31-93-175:~/support$
>>
>>
>>
>> Has anyone run into this issue or know how or where to find the java
>> slave logs?
>>
>> Thanks so much.
>>
>>
>> *VERSION INFO:*
>> *Master:*
>> Jenkins ver. 2.60.2
>> Java: openjdk version "1.8.0_131"
>>
>> *Build node:*
>> Launched via: AWS plugin:
>> https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin (latest
>> version)
>>
>> Ec2 instance running Ubuntu 14.04 and Java 8:
>> ubuntu@ip-172-31-93-175:~$ cat /etc/*release* | grep VERSION
>> VERSION="14.04.5 LTS, Trusty Tahr"
>> VERSION_ID="14.04"
>> ubuntu@ip-172-31-93-175:~$ *java -version*
>> java version "1.8.0_144"
>> Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
>> Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
>>
>>
>>
>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/f234ccf9-d175-4a56-8f10-8190710f1937%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Jenkins slave (EC2 AWS plugin) fails occasionally when build takes too long with error "Caused: java.io.IOException: Unexpected termination of the channel"
I've had great success with the EC2 plugin. Might I suggest using Hashicorp
Packer to build an AMI, and have the EC2 plugin launch that AMI? That will
let you remove Ansible (or any provision tool) out of the equation and save
on agent provisioning time. I know that when our cluster scales up another
node using the EC2 plugin, we generally need that node online ASAP.
On Monday, September 11, 2017 at 9:32:30 PM UTC-4, K S wrote:
>
> I have Jenkins configured to launch EC2 instances (via AWS plugin) to
> execute a build.
> The actual build steps use the Execute Shell method, and launch ansible
> scripts.
>
> I find that if the ansible script runs for too long, the Jenkins slave on
> the EC2 system goes down.
> The Jenkins GUI shows this error:
>
> Connection was broken
>
> java.io.EOFException
> at
> java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2638)
> at
> java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3113)
> at
> java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853)
> at java.io.ObjectInputStream.(ObjectInputStream.java:349)
> at
> hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> at
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
> Caused: java.io.IOException: Unexpected termination of the channel
> at
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)
>
>
>
>
> Some googling lead to this page:
> https://wiki.jenkins.io/display/JENKINS/Remoting+issue
> It suggests I check these log files:
> 1) connection logs on master - I checked these, and they have the same
> information as stack trace.
> 2) slave logs - I do not know where to find these. *The locations
> suggested do not exist on my slave.*
>
> I even inspected the files that the slave java process opens, and the only
> file that seems like a log file ends up being empty:
>
> ubuntu@ip-172-31-93-175:~/support$ ps auxww | grep java | grep slave
> ubuntu25235 8.0 0.5 12211452 157616 ? Ssl 22:23 0:05 java
> -jar /tmp/slave.jar
> ubuntu@ip-172-31-93-175:~/support$ sudo lsof | grep 25235 | grep -i log |
> awk '{print $NF}' | sort | uniq
> /home/ubuntu/support/all_2017-09-11_22.23.07.log
> ubuntu@ip-172-31-93-175:~/support$ cat
> /home/ubuntu/support/all_2017-09-11_22.23.07.log
> ubuntu@ip-172-31-93-175:~/support$
>
>
>
> Has anyone run into this issue or know how or where to find the java slave
> logs?
>
> Thanks so much.
>
>
> *VERSION INFO:*
> *Master:*
> Jenkins ver. 2.60.2
> Java: openjdk version "1.8.0_131"
>
> *Build node:*
> Launched via: AWS plugin:
> https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin (latest version)
>
> Ec2 instance running Ubuntu 14.04 and Java 8:
> ubuntu@ip-172-31-93-175:~$ cat /etc/*release* | grep VERSION
> VERSION="14.04.5 LTS, Trusty Tahr"
> VERSION_ID="14.04"
> ubuntu@ip-172-31-93-175:~$ *java -version*
> java version "1.8.0_144"
> Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
>
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/cccf48eb-f780-443e-8f51-828c8a5e3f6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jenkins slave (EC2 AWS plugin) fails occasionally when build takes too long with error "Caused: java.io.IOException: Unexpected termination of the channel"
I have Jenkins configured to launch EC2 instances (via AWS plugin) to
execute a build.
The actual build steps use the Execute Shell method, and launch ansible
scripts.
I find that if the ansible script runs for too long, the Jenkins slave on
the EC2 system goes down.
The Jenkins GUI shows this error:
Connection was broken
java.io.EOFException
at
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2638)
at
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3113)
at
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853)
at java.io.ObjectInputStream.(ObjectInputStream.java:349)
at
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
at
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59)
Caused: java.io.IOException: Unexpected termination of the channel
at
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73)
Some googling lead to this
page: https://wiki.jenkins.io/display/JENKINS/Remoting+issue
It suggests I check these log files:
1) connection logs on master - I checked these, and they have the same
information as stack trace.
2) slave logs - I do not know where to find these. *The locations
suggested do not exist on my slave.*
I even inspected the files that the slave java process opens, and the only
file that seems like a log file ends up being empty:
ubuntu@ip-172-31-93-175:~/support$ ps auxww | grep java | grep slave
ubuntu25235 8.0 0.5 12211452 157616 ? Ssl 22:23 0:05 java -jar
/tmp/slave.jar
ubuntu@ip-172-31-93-175:~/support$ sudo lsof | grep 25235 | grep -i log |
awk '{print $NF}' | sort | uniq
/home/ubuntu/support/all_2017-09-11_22.23.07.log
ubuntu@ip-172-31-93-175:~/support$ cat
/home/ubuntu/support/all_2017-09-11_22.23.07.log
ubuntu@ip-172-31-93-175:~/support$
Has anyone run into this issue or know how or where to find the java slave
logs?
Thanks so much.
*VERSION INFO:*
*Master:*
Jenkins ver. 2.60.2
Java: openjdk version "1.8.0_131"
*Build node:*
Launched via: AWS
plugin: https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin (latest
version)
Ec2 instance running Ubuntu 14.04 and Java 8:
ubuntu@ip-172-31-93-175:~$ cat /etc/*release* | grep VERSION
VERSION="14.04.5 LTS, Trusty Tahr"
VERSION_ID="14.04"
ubuntu@ip-172-31-93-175:~$ *java -version*
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/2e551b74-cab8-4098-8352-1c37d833ef9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Unexpected termination of the channel
Hi, the stacktrace that I can see in the job log: ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-usersjava.lang.NullPointerException <http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException> at jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:42) <http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties=method> at jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58) <http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract=method> at jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42) <http://stacktrace.jenkins-ci.org/search/?query=jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown=method> at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:882) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun=method> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run=method> at hudson.model.Run.execute(Run.java:1738) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute=method> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run=method> at hudson.model.ResourceController.execute(ResourceController.java:98) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute=method> at hudson.model.Executor.run(Executor.java:410) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run=method> another job has this one: ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users hudson.remoting.RequestAbortedException <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:297) <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request.abort=method> at hudson.remoting.Channel.terminate(Channel.java:847) <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.terminate=method> at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.SynchronousCommandTransport$ReaderThread.run=method> at ..remote call to Basic Slave - M3Medium - jdk 1.7 (i-dfb5c155)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416) at hudson.remoting.Request.call(Request.java:172) at hudson.remoting.Channel.call(Channel.java:780) at hudson.FilePath.act(FilePath.java:979) at hudson.FilePath.act(FilePath.java:968) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by: 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$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) El dijous, 5 maig de 2016 14:21:39 UTC+2, Jordi Andreu Miralles va escriure: > > Hi, > > we are suffering in the last days timeouts and sudden death of our slave > intances in Amazon EC2. >
Unexpected termination of the channel
Hi, we are suffering in the last days timeouts and sudden death of our slave intances in Amazon EC2. I'm observed that the Response Time in Node list page is over 3ms and later we get "Time out for last n try" Finally in the node status page we get an Exception: 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$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Jenkins version: 1.651.1 amazon ec2 plugin version: 1.31 Any idea how to solve this problem? Best regards, Jordi -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e9744e1a-9602-4093-9940-cfb585065e74%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Caused by: java.io.IOException: Unexpected termination of the channel
Hi, Some times i got the below error and some times i didn't got what is the problem.My Jenkins version is 1.528 FATAL: Unable to delete script file /var/folders/qd/x3ltyqxs05n_t6btw8wd_gbmgp/T/hudson6356242655423798889.sh hudson.util.IOException2http://stacktrace.jenkins-ci.org/search?query=hudson.util.IOException2: remote file operation failed:/var/folders/qd/x3ltyqxs05n_t6btw8wd_gbmgp/T/hudson6356242655423798889.sh at hudson.remoting.Channel@25e258af at hudson.FilePath.act(FilePath.java:905)http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=methodat hudson.FilePath.act(FilePath.java:882)http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=methodat hudson.FilePath.delete(FilePath.java:1291)http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.deleteentity=methodat hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:101)http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.CommandInterpreter.performentity=methodat hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60)http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.CommandInterpreter.performentity=methodat hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.BuildStepMonitor$1.performentity=methodat hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.performentity=methodat hudson.model.Build$BuildExecution.build(Build.java:199)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.buildentity=methodat hudson.model.Build$BuildExecution.doRun(Build.java:160)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.doRunentity=methodat hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=methodat hudson.model.Run.execute(Run.java:1603)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=methodat hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.runentity=methodat hudson.model.ResourceController.execute(ResourceController.java:88)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=methodat hudson.model.Executor.run(Executor.java:247)http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=methodCaused by: hudson.remoting.ChannelClosedExceptionhttp://stacktrace.jenkins-ci.org/search?query=hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:516)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.sendentity=methodat hudson.remoting.Request.call(Request.java:129)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request.callentity=methodat hudson.remoting.Channel.call(Channel.java:714)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.callentity=methodat hudson.FilePath.act(FilePath.java:898)http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.actentity=method... 13 more Caused by: java.io.IOExceptionhttp://stacktrace.jenkins-ci.org/search?query=java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.SynchronousCommandTransport$ReaderThread.runentity=methodCaused by: java.io.EOFException http://stacktrace.jenkins-ci.org/search?query=java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2595)http://stacktrace.jenkins-ci.org/search/?query=java.io.ObjectInputStream$BlockDataInputStream.peekByteentity=methodat java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)http://stacktrace.jenkins-ci.org/search/?query=java.io.ObjectInputStream.readObject0entity=methodat java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)http://stacktrace.jenkins-ci.org/search/?query=java.io.ObjectInputStream.readObjectentity=methodat hudson.remoting.Command.readFrom(Command.java:92)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Command.readFromentity=methodat hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.ClassicCommandTransport.readentity=methodat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.SynchronousCommandTransport$ReaderThread.runentity=methodFATAL: hudson.remoting.RequestAbortedException: java.io.IOException
Re: Jenkins exit code 143 - due to Unexpected termination of the channel
Hi, On 22/01/2013 00:02, BobTheBuilder wrote: Hello, I have a long running build that never runs to completion on the slave computer, it gets Maven JVM terminated unexpectedly with exit code 143. Exit codes over 128 signify that the process died due to a signal. exitcode = 128 + signal number. That would be signal 25. Assuming that you have a standard linux distribution that would be SIGXFSZ. http://www.lindevdoc.org/wiki/SIGXFSZ Does your build create large files? If so then maybe your jenkins master or slave is running in an environment where an rlimit has been placed on file size. Regards Richard It does not terminate in the same spot, some times it terminates in 5 minutes others 30+ minutes (usually 21-22). If I run the Maven build on my machine, it runs just fine, completing in 82-92 minutes. The Jenkins master log says INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java, -Xrs, -Djava.awt.headless=true, -cp, /opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar, hudson.maven.agent.Main, /opt/ltsapps/maven, /opt/ltsapps/jenkins-1.424.2/slave.jar, /opt/ltsapps/jenkins/maven-interceptor.jar, 46746, /opt/ltsapps/jenkins/maven2.1-interceptor.jar] java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037) 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.Channel$ReaderThread.run(Channel.java:1031) Various Google searches say to check the cpu and memory usage and possibly add more. However from what I've observed, our machine has 4 CPUs and lots of free memory that never seems to get used, so I don't think thats it. I've also tried the -Xms500m -Xmx550m options with no impact. I've also found sites that referrence problems with Jenkins clients using SSH (http://jenkins.361315.n4.nabble.com/fai ... 36397.html) to communicate with the master but we're using Lauch slave agents via Java Web Start. Please note, I will not be able to switch to SSH without an approval from Congress. :) Our Maven goals and options are: clean verify -U -e -Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true -Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200 -Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true -Dstory.paths.to.include=stories/sf/baf/pmmt/stories/rules/**/*.story MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true Any help would be appreciated. Thank you. -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html Sent from the Jenkins users mailing list archive at Nabble.com.
Re: Jenkins exit code 143 - due to Unexpected termination of the channel
128+25=153 not 143 the signal is 15 not 25 Richard On 2013-01-22, at 04:13, Richard Mortimer ri...@oldelvet.org.uk wrote: Hi, On 22/01/2013 00:02, BobTheBuilder wrote: Hello, I have a long running build that never runs to completion on the slave computer, it gets Maven JVM terminated unexpectedly with exit code 143. Exit codes over 128 signify that the process died due to a signal. exitcode = 128 + signal number. That would be signal 25. Assuming that you have a standard linux distribution that would be SIGXFSZ. http://www.lindevdoc.org/wiki/SIGXFSZ Does your build create large files? If so then maybe your jenkins master or slave is running in an environment where an rlimit has been placed on file size. Regards Richard It does not terminate in the same spot, some times it terminates in 5 minutes others 30+ minutes (usually 21-22). If I run the Maven build on my machine, it runs just fine, completing in 82-92 minutes. The Jenkins master log says INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java, -Xrs, -Djava.awt.headless=true, -cp, /opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar, hudson.maven.agent.Main, /opt/ltsapps/maven, /opt/ltsapps/jenkins-1.424.2/slave.jar, /opt/ltsapps/jenkins/maven-interceptor.jar, 46746, /opt/ltsapps/jenkins/maven2.1-interceptor.jar] java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037) 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.Channel$ReaderThread.run(Channel.java:1031) Various Google searches say to check the cpu and memory usage and possibly add more. However from what I've observed, our machine has 4 CPUs and lots of free memory that never seems to get used, so I don't think thats it. I've also tried the -Xms500m -Xmx550m options with no impact. I've also found sites that referrence problems with Jenkins clients using SSH (http://jenkins.361315.n4.nabble.com/fai ... 36397.html) to communicate with the master but we're using Lauch slave agents via Java Web Start. Please note, I will not be able to switch to SSH without an approval from Congress. :) Our Maven goals and options are: clean verify -U -e -Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true -Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200 -Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true -Dstory.paths.to.include=stories/sf/baf/pmmt/stories/rules/**/*.story MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true Any help would be appreciated. Thank you. -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html Sent from the Jenkins users mailing list archive at Nabble.com.
Re: Jenkins exit code 143 - due to Unexpected termination of the channel
On 22/01/2013 10:47, Richard Lavoie wrote: 128+25=153 not 143 the signal is 15 not 25 Damn! Indeed it is. That'll teach me to send messages before first coffee of the day. Well signal 15 is SIGTERM. My initial thought was that the issue would have been due to the kernel OOM (out of memory) killer killing things. https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError That normally uses SIGKILL (9) but maybe it can use SIGTERM in some scenarios. A quick search showed SIGTERM being used in kernel 2.4 but that doesn't seem to be done in the latest linux kernels. ftp://ftp.kernel.org/pub/linux/kernel/people/marcelo/linux-2.4/mm/oom_kill.c Anyhow the solution will likely lie in finding the cause/source of the SIGTERM. Regards Richard Richard On 2013-01-22, at 04:13, Richard Mortimer ri...@oldelvet.org.uk wrote: Hi, On 22/01/2013 00:02, BobTheBuilder wrote: Hello, I have a long running build that never runs to completion on the slave computer, it gets Maven JVM terminated unexpectedly with exit code 143. Exit codes over 128 signify that the process died due to a signal. exitcode = 128 + signal number. That would be signal 25. Assuming that you have a standard linux distribution that would be SIGXFSZ. http://www.lindevdoc.org/wiki/SIGXFSZ Does your build create large files? If so then maybe your jenkins master or slave is running in an environment where an rlimit has been placed on file size. Regards Richard It does not terminate in the same spot, some times it terminates in 5 minutes others 30+ minutes (usually 21-22). If I run the Maven build on my machine, it runs just fine, completing in 82-92 minutes. The Jenkins master log says INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java, -Xrs, -Djava.awt.headless=true, -cp, /opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar, hudson.maven.agent.Main, /opt/ltsapps/maven, /opt/ltsapps/jenkins-1.424.2/slave.jar, /opt/ltsapps/jenkins/maven-interceptor.jar, 46746, /opt/ltsapps/jenkins/maven2.1-interceptor.jar] java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037) 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.Channel$ReaderThread.run(Channel.java:1031) Various Google searches say to check the cpu and memory usage and possibly add more. However from what I've observed, our machine has 4 CPUs and lots of free memory that never seems to get used, so I don't think thats it. I've also tried the -Xms500m -Xmx550m options with no impact. I've also found sites that referrence problems with Jenkins clients using SSH (http://jenkins.361315.n4.nabble.com/fai ... 36397.html) to communicate with the master but we're using Lauch slave agents via Java Web Start. Please note, I will not be able to switch to SSH without an approval from Congress. :) Our Maven goals and options are: clean verify -U -e -Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true -Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200 -Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true -Dstory.paths.to.include=stories/sf/baf/pmmt/stories/rules/**/*.story MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true Any help would be appreciated. Thank you. -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html Sent from the Jenkins users mailing list archive at Nabble.com.
Re: Jenkins exit code 143 - due to Unexpected termination of the channel
Hello, Given the significant variation in time range that the JBehave test runs, I wouldn't expect the problem to be file size. If it was, it would fail around the same spot. However wanting to investigate all possibilities, I ran a ulimit -a and here's what I came up with: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 106496 max locked memory (kbytes, -l) 32 max memory size (kbytes, -m) unlimited open files (-n) 4096 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 10240 cpu time (seconds, -t) unlimited max user processes (-u) 106496 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Earlier in the day, I pulled down the heap dump from the master. Unfortunately it was over 770 megs and I don't have an editor capable of opening a file that large (my laptop is Windows). I'm in the process of requesting some different text editing software. Given the possibility of the heap dump containing confidential information, I'm not posting it to the site. When I'm able to view the output then I'll worry about it. :) -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347p4652500.html Sent from the Jenkins users mailing list archive at Nabble.com.
Jenkins exit code 143 - due to Unexpected termination of the channel
Hello, I have a long running build that never runs to completion on the slave computer, it gets Maven JVM terminated unexpectedly with exit code 143. It does not terminate in the same spot, some times it terminates in 5 minutes others 30+ minutes (usually 21-22). If I run the Maven build on my machine, it runs just fine, completing in 82-92 minutes. The Jenkins master log says INFO: PMMT-SystemTest-Milestone3 #814 main build action completed: FAILURE Jan 17, 2013 1:38:37 PM hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel Channel to Maven [/usr/lib/jvm/java/bin/java, -Xrs, -Djava.awt.headless=true, -cp, /opt/ltsapps/jenkins/maven-agent.jar:/opt/ltsapps/jenkins/classworlds.jar, hudson.maven.agent.Main, /opt/ltsapps/maven, /opt/ltsapps/jenkins-1.424.2/slave.jar, /opt/ltsapps/jenkins/maven-interceptor.jar, 46746, /opt/ltsapps/jenkins/maven2.1-interceptor.jar] java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1037) 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.Channel$ReaderThread.run(Channel.java:1031) Various Google searches say to check the cpu and memory usage and possibly add more. However from what I've observed, our machine has 4 CPUs and lots of free memory that never seems to get used, so I don't think thats it. I've also tried the -Xms500m -Xmx550m options with no impact. I've also found sites that referrence problems with Jenkins clients using SSH (http://jenkins.361315.n4.nabble.com/fai ... 36397.html) to communicate with the master but we're using Lauch slave agents via Java Web Start. Please note, I will not be able to switch to SSH without an approval from Congress. :) Our Maven goals and options are: clean verify -U -e -Dtest.machine.qualifier=Z -Dtarget.environment.alias=dev1 -Drest.skip=true -Dfirefox.skip=true -Dchrome.skip=true -Drunner.timeout.in.seconds=25200 -Drunner.threads.to.use=1 -Ppmmt -DtestFailureIgnore=true -Dstory.paths.to.include=stories/sf/baf/pmmt/stories/rules/**/*.story MAVEN_OPTS is set to: -Xrs -Djava.awt.headless=true Any help would be appreciated. Thank you. -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-exit-code-143-due-to-Unexpected-termination-of-the-channel-tp4652347.html Sent from the Jenkins users mailing list archive at Nabble.com.
[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449
Hi Richard The last attempted version we used was 1.450 I believe. We could take a later version if that makes it easier. We are currently stuck at running 1.441 on Winstone only. Thanks again. On Tue, Feb 28, 2012 at 5:20 PM, oldel...@java.net (JIRA) nore...@jenkins-ci.org wrote: [ https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159639#comment-159639] Richard Mortimer commented on JENKINS-12037: If I build a test version for you with a 5 second heartbeat timeout are you able to test it? If so is there any particular Jenkins version that you would be testing with so that I can build a matching cli jar file. Regarding the -s parameter being ignored I vaguely remember that there is a bug reported in JIRA where it does not wait if there is already a queued instance of the same job. From what you describe this may not be applicable to your circumstances but it could. CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449 -- Key: JENKINS-12037 URL: https://issues.jenkins-ci.org/browse/JENKINS-12037 Project: Jenkins Issue Type: Bug Components: cli Environment: * Running on SLES9 Linux server with 4 CPUs and plenty of diskspace. * Tomcat 7.0.22 * JDK 1.6.0_14 * Only ONE Master configuration - no slaves are configured * 3 Executors - (one less than the max number of CPUs) Reporter: mark streit Attachments: Tomcat7_Jenkins1449_logs.zip We reported an issue some time back that was also listed as fixed in Jenkins 1.441: Log: [FIXED JENKINS-11130] SEVERE: I/O error in channel Chunked connection when using jenkins-cli.jar Perhaps another bug should NOT be submitted so I have added the following comments below the line to the original defect 11130 comments section in case it can be reviewed/re-opened. We did NOT try to make any adjustments to the Tomcat configuration: Tomcat Connector connectionUploadTimeout but we are also now seeing the same problem with Winstone when at this same 1.441 level. We did revert to the 1.438 version of the CLI (leaving the WAR at 1.441 running in Winstone) and that is serving asthe current workaround. We have downloaded and installed the LATEST 1.441 release that lists the fix for this problem. Currently we were running 1.438 on Winstone only (since with Tomcat 6 or 7, we had experienced the error HOWEVER yet under Winstone, it worked OK so that was our workaround - while running 1.438). Now with Jenkins 1.441 - we are getting the ERROR again and NOW WITH BOTH Winstone and the Tomcat configurations). We have left the Jenkins 1.441 WAR file in place running on Winstone, and reverted the CLI jar file back to the 1.438 version for now and that appears to work again with Winstone. Checked Manifest of CLI jar downloaded with the 1.441 WAR installation: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: kohsuke Build-Jdk: 1.6.0_26 Main-Class: hudson.cli.CLI Jenkins-CLI-Version: 1.441 Under Tomcat 7, we get this stacktrace: Started by command line [workspace] $ /bin/bash -xe /opt/apache-tomcat-7.0.22_jenkins/temp/hudson3281734817830.sh + /opt/Sun/jdk1.6.0_14/bin/java -jar /opt/Sun/jdk1.6.0_14/lib/jenkins-cli.jar -s http://11.22.33.44:8082/jenkins/ build XYZ_Project-SharedLibs -s -p SVN_PATH=trunk Dec 5, 2011 12:59:11 PM hudson.remoting.Channel$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://11.22.33.44:8082/jenkins/cli java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109) Exception in thread main hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy2.main(Unknown Source) at hudson.cli.CLI.execute(CLI.java:200) at hudson.cli.CLI._main(CLI.java:330) at hudson.cli.CLI.main(CLI.java:245) Caused
