Re: ssh slaves connection timeout
Hi, thank you! Yes I can confirm that using the 3.4.x kernel on the master it works! Br, Andras On Wednesday, October 22, 2014 10:26:24 PM UTC-7, Guillaume Boucherie wrote: > > For me it was link to linux kernel used. See this bug for more information > : https://issues.jenkins-ci.org/browse/JENKINS-14332 > > Regards > > Guillaume Boucherie > > Guillaume > > 2014-10-22 23:05 GMT+02:00 Kanstantsin Shautsou >: > >> Do you have any logs? In http://your_jenkins_url/log and jenkins.log ? >> >> On Friday, May 23, 2014 6:07:17 PM UTC+3, Guillaume Boucherie wrote: >>> >>> Hi, >>> >>> I made more tests and I find something very interesting. >>> When I launch the slave with a custom script the communication between >>> master and slave never stopped. >>> But when I launch the slave with Jenkins buit in ssh connection I have >>> problems. >>> >>> So maybe there is a problem in trilead-ssh2 library ? >>> Anyone as an idea about this ? >>> >>> Thanks >>> >>> Guillaume >>> >>> >>> 2014-05-23 10:24 GMT+02:00 Guillaume Boucherie : >>> Hi, My slaves are on the same VPC as my master. I try with a very low restricted Security Group that allow all traffic from all port and protocol without success. Anyway I will try to fixed the tcp port used as you say. Thanks Guillaume 2014-05-22 18:32 GMT+02:00 Gareth Bowles : We have masters and slaves set up in VPC at my job. The only thing to > make sure of is that the master / slave communication port is open in > your > security groups; this should be set to a fixed value via the "TCP port > for > JNLP slave agents" field in http://yourjenkins/configureSecurity > (even though the field description mentions JNLP, this port is used for > SSH > connection as well). > > Are your slaves running in the same VPC as your master (this is the > case for me) ? If not, there might be some additional network access > issues. > > > On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: >> >> After more research and test I find that the problem is link to AWS >> VPC. >> I'm did a simple test, running two instance in AWS (one for master >> and one for slave) and create a job that simply echo 1000 times "Lorem >> ipsum dolor sit amet, consectetur adipiscing elit. Maecenas et.". >> When I did this on AWS VPC I can reproduce the problem after 2-3 job >> execution, on classic EC2 its never failed. >> >> Does anyone have already trying to setup a Jenkins master/slave in >> AWS VPC ? >> >> Thanks >> >> Guillaume Boucherie >> >> >> Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : >>> >>> Hi, >>> >>> I'm facing very unstable ssh connection between master/slaves on my >>> Jenkins installation. >>> Both master and slaves are AWS instance that run on AWS Linux system. >>> After some time the ssh connection stop, current job that run are >>> freeze and failed after 15min. >>> I attached the stacktrace from jenkins.log >>> >>> Does anybody face the same problem ? >>> Maybe its related to ssh configuration ? >>> I'm running Jenkins 1.554.1 and salve version used is 2.36. >>> >>> Thanks >>> Guillaume Boucherie >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-use...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-use...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
For me it was link to linux kernel used. See this bug for more information : https://issues.jenkins-ci.org/browse/JENKINS-14332 Regards Guillaume Boucherie Guillaume 2014-10-22 23:05 GMT+02:00 Kanstantsin Shautsou : > Do you have any logs? In http://your_jenkins_url/log and jenkins.log ? > > On Friday, May 23, 2014 6:07:17 PM UTC+3, Guillaume Boucherie wrote: >> >> Hi, >> >> I made more tests and I find something very interesting. >> When I launch the slave with a custom script the communication between >> master and slave never stopped. >> But when I launch the slave with Jenkins buit in ssh connection I have >> problems. >> >> So maybe there is a problem in trilead-ssh2 library ? >> Anyone as an idea about this ? >> >> Thanks >> >> Guillaume >> >> >> 2014-05-23 10:24 GMT+02:00 Guillaume Boucherie : >> >>> Hi, >>> >>> My slaves are on the same VPC as my master. >>> I try with a very low restricted Security Group that allow all traffic >>> from all port and protocol without success. >>> Anyway I will try to fixed the tcp port used as you say. >>> Thanks >>> >>> Guillaume >>> >>> >>> 2014-05-22 18:32 GMT+02:00 Gareth Bowles : >>> >>> We have masters and slaves set up in VPC at my job. The only thing to make sure of is that the master / slave communication port is open in your security groups; this should be set to a fixed value via the "TCP port for JNLP slave agents" field in http://yourjenkins/configureSecurity (even though the field description mentions JNLP, this port is used for SSH connection as well). Are your slaves running in the same VPC as your master (this is the case for me) ? If not, there might be some additional network access issues. On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: > > After more research and test I find that the problem is link to AWS > VPC. > I'm did a simple test, running two instance in AWS (one for master and > one for slave) and create a job that simply echo 1000 times "Lorem ipsum > dolor sit amet, consectetur adipiscing elit. Maecenas et.". > When I did this on AWS VPC I can reproduce the problem after 2-3 job > execution, on classic EC2 its never failed. > > Does anyone have already trying to setup a Jenkins master/slave in AWS > VPC ? > > Thanks > > Guillaume Boucherie > > > Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : >> >> Hi, >> >> I'm facing very unstable ssh connection between master/slaves on my >> Jenkins installation. >> Both master and slaves are AWS instance that run on AWS Linux system. >> After some time the ssh connection stop, current job that run are >> freeze and failed after 15min. >> I attached the stacktrace from jenkins.log >> >> Does anybody face the same problem ? >> Maybe its related to ssh configuration ? >> I'm running Jenkins 1.554.1 and salve version used is 2.36. >> >> Thanks >> Guillaume Boucherie >> > -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. >>> >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
Do you have any logs? In http://your_jenkins_url/log and jenkins.log ? On Friday, May 23, 2014 6:07:17 PM UTC+3, Guillaume Boucherie wrote: > > Hi, > > I made more tests and I find something very interesting. > When I launch the slave with a custom script the communication between > master and slave never stopped. > But when I launch the slave with Jenkins buit in ssh connection I have > problems. > > So maybe there is a problem in trilead-ssh2 library ? > Anyone as an idea about this ? > > Thanks > > Guillaume > > > 2014-05-23 10:24 GMT+02:00 Guillaume Boucherie >: > >> Hi, >> >> My slaves are on the same VPC as my master. >> I try with a very low restricted Security Group that allow all traffic >> from all port and protocol without success. >> Anyway I will try to fixed the tcp port used as you say. >> Thanks >> >> Guillaume >> >> >> 2014-05-22 18:32 GMT+02:00 Gareth Bowles > >> : >> >> We have masters and slaves set up in VPC at my job. The only thing to >>> make sure of is that the master / slave communication port is open in your >>> security groups; this should be set to a fixed value via the "TCP port for >>> JNLP slave agents" field in http://yourjenkins/configureSecurity (even >>> though the field description mentions JNLP, this port is used for SSH >>> connection as well). >>> >>> Are your slaves running in the same VPC as your master (this is the case >>> for me) ? If not, there might be some additional network access issues. >>> >>> >>> On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: After more research and test I find that the problem is link to AWS VPC. I'm did a simple test, running two instance in AWS (one for master and one for slave) and create a job that simply echo 1000 times "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Maecenas et.". When I did this on AWS VPC I can reproduce the problem after 2-3 job execution, on classic EC2 its never failed. Does anyone have already trying to setup a Jenkins master/slave in AWS VPC ? Thanks Guillaume Boucherie Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : > > Hi, > > I'm facing very unstable ssh connection between master/slaves on my > Jenkins installation. > Both master and slaves are AWS instance that run on AWS Linux system. > After some time the ssh connection stop, current job that run are > freeze and failed after 15min. > I attached the stacktrace from jenkins.log > > Does anybody face the same problem ? > Maybe its related to ssh configuration ? > I'm running Jenkins 1.554.1 and salve version used is 2.36. > > Thanks > Guillaume Boucherie > -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> jenkinsci-use...@googlegroups.com . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
Hi, have you solved this issue? We have the exact same issue. Thanks, Andras On Friday, May 23, 2014 8:07:17 AM UTC-7, Guillaume Boucherie wrote: > > Hi, > > I made more tests and I find something very interesting. > When I launch the slave with a custom script the communication between > master and slave never stopped. > But when I launch the slave with Jenkins buit in ssh connection I have > problems. > > So maybe there is a problem in trilead-ssh2 library ? > Anyone as an idea about this ? > > Thanks > > Guillaume > > > 2014-05-23 10:24 GMT+02:00 Guillaume Boucherie >: > >> Hi, >> >> My slaves are on the same VPC as my master. >> I try with a very low restricted Security Group that allow all traffic >> from all port and protocol without success. >> Anyway I will try to fixed the tcp port used as you say. >> Thanks >> >> Guillaume >> >> >> 2014-05-22 18:32 GMT+02:00 Gareth Bowles > >> : >> >> We have masters and slaves set up in VPC at my job. The only thing to >>> make sure of is that the master / slave communication port is open in your >>> security groups; this should be set to a fixed value via the "TCP port for >>> JNLP slave agents" field in http://yourjenkins/configureSecurity (even >>> though the field description mentions JNLP, this port is used for SSH >>> connection as well). >>> >>> Are your slaves running in the same VPC as your master (this is the case >>> for me) ? If not, there might be some additional network access issues. >>> >>> >>> On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: After more research and test I find that the problem is link to AWS VPC. I'm did a simple test, running two instance in AWS (one for master and one for slave) and create a job that simply echo 1000 times "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Maecenas et.". When I did this on AWS VPC I can reproduce the problem after 2-3 job execution, on classic EC2 its never failed. Does anyone have already trying to setup a Jenkins master/slave in AWS VPC ? Thanks Guillaume Boucherie Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : > > Hi, > > I'm facing very unstable ssh connection between master/slaves on my > Jenkins installation. > Both master and slaves are AWS instance that run on AWS Linux system. > After some time the ssh connection stop, current job that run are > freeze and failed after 15min. > I attached the stacktrace from jenkins.log > > Does anybody face the same problem ? > Maybe its related to ssh configuration ? > I'm running Jenkins 1.554.1 and salve version used is 2.36. > > Thanks > Guillaume Boucherie > -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe >>> . >>> To unsubscribe from this group and all its topics, send an email to >>> jenkinsci-use...@googlegroups.com . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
Hi, I made more tests and I find something very interesting. When I launch the slave with a custom script the communication between master and slave never stopped. But when I launch the slave with Jenkins buit in ssh connection I have problems. So maybe there is a problem in trilead-ssh2 library ? Anyone as an idea about this ? Thanks Guillaume 2014-05-23 10:24 GMT+02:00 Guillaume Boucherie < guillaume.bouche...@gmail.com>: > Hi, > > My slaves are on the same VPC as my master. > I try with a very low restricted Security Group that allow all traffic > from all port and protocol without success. > Anyway I will try to fixed the tcp port used as you say. > Thanks > > Guillaume > > > 2014-05-22 18:32 GMT+02:00 Gareth Bowles : > > We have masters and slaves set up in VPC at my job. The only thing to >> make sure of is that the master / slave communication port is open in your >> security groups; this should be set to a fixed value via the "TCP port for >> JNLP slave agents" field in http://yourjenkins/configureSecurity (even >> though the field description mentions JNLP, this port is used for SSH >> connection as well). >> >> Are your slaves running in the same VPC as your master (this is the case >> for me) ? If not, there might be some additional network access issues. >> >> >> On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: >>> >>> After more research and test I find that the problem is link to AWS VPC. >>> I'm did a simple test, running two instance in AWS (one for master and >>> one for slave) and create a job that simply echo 1000 times "Lorem ipsum >>> dolor sit amet, consectetur adipiscing elit. Maecenas et.". >>> When I did this on AWS VPC I can reproduce the problem after 2-3 job >>> execution, on classic EC2 its never failed. >>> >>> Does anyone have already trying to setup a Jenkins master/slave in AWS >>> VPC ? >>> >>> Thanks >>> >>> Guillaume Boucherie >>> >>> >>> Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : Hi, I'm facing very unstable ssh connection between master/slaves on my Jenkins installation. Both master and slaves are AWS instance that run on AWS Linux system. After some time the ssh connection stop, current job that run are freeze and failed after 15min. I attached the stacktrace from jenkins.log Does anybody face the same problem ? Maybe its related to ssh configuration ? I'm running Jenkins 1.554.1 and salve version used is 2.36. Thanks Guillaume Boucherie >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
Hi, My slaves are on the same VPC as my master. I try with a very low restricted Security Group that allow all traffic from all port and protocol without success. Anyway I will try to fixed the tcp port used as you say. Thanks Guillaume 2014-05-22 18:32 GMT+02:00 Gareth Bowles : > We have masters and slaves set up in VPC at my job. The only thing to > make sure of is that the master / slave communication port is open in your > security groups; this should be set to a fixed value via the "TCP port for > JNLP slave agents" field in http://yourjenkins/configureSecurity (even > though the field description mentions JNLP, this port is used for SSH > connection as well). > > Are your slaves running in the same VPC as your master (this is the case > for me) ? If not, there might be some additional network access issues. > > > On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: >> >> After more research and test I find that the problem is link to AWS VPC. >> I'm did a simple test, running two instance in AWS (one for master and >> one for slave) and create a job that simply echo 1000 times "Lorem ipsum >> dolor sit amet, consectetur adipiscing elit. Maecenas et.". >> When I did this on AWS VPC I can reproduce the problem after 2-3 job >> execution, on classic EC2 its never failed. >> >> Does anyone have already trying to setup a Jenkins master/slave in AWS >> VPC ? >> >> Thanks >> >> Guillaume Boucherie >> >> >> Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : >>> >>> Hi, >>> >>> I'm facing very unstable ssh connection between master/slaves on my >>> Jenkins installation. >>> Both master and slaves are AWS instance that run on AWS Linux system. >>> After some time the ssh connection stop, current job that run are freeze >>> and failed after 15min. >>> I attached the stacktrace from jenkins.log >>> >>> Does anybody face the same problem ? >>> Maybe its related to ssh configuration ? >>> I'm running Jenkins 1.554.1 and salve version used is 2.36. >>> >>> Thanks >>> Guillaume Boucherie >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/hWNTI4xRy_A/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
We have masters and slaves set up in VPC at my job. The only thing to make sure of is that the master / slave communication port is open in your security groups; this should be set to a fixed value via the "TCP port for JNLP slave agents" field in http://yourjenkins/configureSecurity (even though the field description mentions JNLP, this port is used for SSH connection as well). Are your slaves running in the same VPC as your master (this is the case for me) ? If not, there might be some additional network access issues. On Thursday, May 22, 2014 5:05:25 AM UTC-7, Guillaume Boucherie wrote: > > After more research and test I find that the problem is link to AWS VPC. > I'm did a simple test, running two instance in AWS (one for master and one > for slave) and create a job that simply echo 1000 times "Lorem ipsum dolor > sit amet, consectetur adipiscing elit. Maecenas et.". > When I did this on AWS VPC I can reproduce the problem after 2-3 job > execution, on classic EC2 its never failed. > > Does anyone have already trying to setup a Jenkins master/slave in AWS VPC > ? > > Thanks > > Guillaume Boucherie > > > Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : >> >> Hi, >> >> I'm facing very unstable ssh connection between master/slaves on my >> Jenkins installation. >> Both master and slaves are AWS instance that run on AWS Linux system. >> After some time the ssh connection stop, current job that run are freeze >> and failed after 15min. >> I attached the stacktrace from jenkins.log >> >> Does anybody face the same problem ? >> Maybe its related to ssh configuration ? >> I'm running Jenkins 1.554.1 and salve version used is 2.36. >> >> Thanks >> Guillaume Boucherie >> > -- 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. For more options, visit https://groups.google.com/d/optout.
Re: ssh slaves connection timeout
After more research and test I find that the problem is link to AWS VPC. I'm did a simple test, running two instance in AWS (one for master and one for slave) and create a job that simply echo 1000 times "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Maecenas et.". When I did this on AWS VPC I can reproduce the problem after 2-3 job execution, on classic EC2 its never failed. Does anyone have already trying to setup a Jenkins master/slave in AWS VPC ? Thanks Guillaume Boucherie Le lundi 5 mai 2014 11:32:23 UTC+2, Guillaume Boucherie a écrit : > > Hi, > > I'm facing very unstable ssh connection between master/slaves on my > Jenkins installation. > Both master and slaves are AWS instance that run on AWS Linux system. > After some time the ssh connection stop, current job that run are freeze > and failed after 15min. > I attached the stacktrace from jenkins.log > > Does anybody face the same problem ? > Maybe its related to ssh configuration ? > I'm running Jenkins 1.554.1 and salve version used is 2.36. > > Thanks > Guillaume Boucherie > -- 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. For more options, visit https://groups.google.com/d/optout.
ssh slaves connection timeout
Hi, I'm facing very unstable ssh connection between master/slaves on my Jenkins installation. Both master and slaves are AWS instance that run on AWS Linux system. After some time the ssh connection stop, current job that run are freeze and failed after 15min. I attached the stacktrace from jenkins.log Does anybody face the same problem ? Maybe its related to ssh configuration ? I'm running Jenkins 1.554.1 and salve version used is 2.36. Thanks Guillaume Boucherie -- 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. For more options, visit https://groups.google.com/d/optout. May 05, 2014 10:10:40 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel jenkins-slave-linux-1 java.net.SocketException: Connection timed out at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) at java.net.SocketOutputStream.write(SocketOutputStream.java:159) at com.trilead.ssh2.crypto.cipher.CipherOutputStream.flush(CipherOutputStream.java:75) at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:193) at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:107) at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:666) at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:377) at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:952) at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:85) at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2310) at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2323) at java.io.ObjectInputStream$BlockDataInputStream.readUTFBody(ObjectInputStream.java:3063) at java.io.ObjectInputStream$BlockDataInputStream.readUTF(ObjectInputStream.java:2864) at java.io.ObjectInputStream.readUTF(ObjectInputStream.java:1072) at java.io.ObjectStreamClass.readNonProxy(ObjectStreamClass.java:671) at java.io.ObjectInputStream.readClassDescriptor(ObjectInputStream.java:830) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1601) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) 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) May 05, 2014 10:10:40 AM hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor monitor WARNING: Failed to monitor jenkins-slave-linux-1 for Architecture java.io.IOException: Sorry, this connection is closed. at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:647) at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:438) at com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1876) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1785) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1285) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1230) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1426) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1576) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:350) at hudson.remoting.Command.writeTo(Command.java:83) at hudson.remoting.ClassicCommandTransport.write(ClassicCommandTransport.java:52) at hudson.remoting.Channel.send(Channel.java:528) at hudson.remoting.Request.callAsync(Request.java:208) at hudson.remoting.Channel.callAsync(Channel.java:749) at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:76) at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:280) Caused by: java.net.SocketException
