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 <[email protected]>: > 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 <[email protected]>: >> >>> 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 <[email protected]>: >>> >>> 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 >>>> [email protected]. >>>> 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 > [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
