• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Blocker
• Component/s: core, remoting, ssh-slaves-plugin
• Labels:

  • remoting
• Environment:

  jenkins-1.509.4 with remoting-2.36
  ssh-slaves-1.2

1. 3.4.83-70.111.amzn1.x86_64_kernel_params.txt

   21 kB

   2014-09-18 12:20

2. sysctl_3.13.txt

   24 kB

   2014-09-18 09:58

3. sysctl_3.2.txt

   22 kB

   2014-09-18 09:58

[JENKINS-14332] Repeated channel/timeout errors from Jenkins slave

Olivier Lamy created issue - 2012-07-06 09:45

Olivier Lamy made changes - 2012-07-06 09:47

Priority

Original: Major [ 3 ]

New: Blocker [ 1 ]

Oleg Nenashev made changes - 2014-05-19 09:21

Assignee

New: Oleg Nenashev [ oleg_nenashev ]

Oleg Nenashev made changes - 2014-05-19 09:24

Component/s		New: master-slave [ 15489 ]
Component/s		New: ssh-slaves [ 15578 ]
Description		New: The issue appears on my custom build of the Jenkins core, but seems it could be reproduced on newest versions as well. We've experienced a network overloading, which has let to the exception in the PingThread on Jenkins master, which has closed the communication channel. However, the slave stills online and takes jobs, but any remote action fails (see logs above) => All scheduled builds fail with an error The issue affects ssh-slaves only:     Linux SSH slaves are "online", but all jobs on the fail with the error above     Windows services have reconnected automatically...     Windows JNLP slaves have reconnected as well
Environment		New: jenkins-1.509.4 with remoting-2.36 ssh-slaves-1.2

Oleg Nenashev made changes - 2014-05-19 09:25

Description

Original: The issue appears on my custom build of the Jenkins core, but seems it could be reproduced on newest versions as well. We've experienced a network overloading, which has let to the exception in the PingThread on Jenkins master, which has closed the communication channel. However, the slave stills online and takes jobs, but any remote action fails (see logs above) => All scheduled builds fail with an error The issue affects ssh-slaves only:     Linux SSH slaves are "online", but all jobs on the fail with the error above     Windows services have reconnected automatically...     Windows JNLP slaves have reconnected as well

New: The issue appears on my custom build of the Jenkins core, but seems it could be reproduced on newest versions as well. We've experienced a network overloading, which has let to the exception in the PingThread on Jenkins master, which has closed the communication channel. However, the slave stills online and takes jobs, but any remote action fails (see logs above) => All scheduled builds fail with an error The issue affects ssh-slaves only: * Linux SSH slaves are "online", but all jobs on the fail with the error above * Windows services have reconnected automatically... * Windows JNLP slaves have reconnected as well

Daniel Beck made changes - 2014-09-01 14:43

Labels

New: remoting

Guillaume Boucherie made changes - 2014-09-18 09:58

Attachment		New: sysctl_3.2.txt [ 26865 ]
Attachment		New: sysctl_3.13.txt [ 26866 ]

Trevor Baker made changes - 2014-09-18 12:20

Attachment

New: 3.4.83-70.111.amzn1.x86_64_kernel_params.txt [ 26867 ]

Oleg Nenashev made changes - 2014-09-29 12:16

Assignee

Original: Oleg Nenashev [ oleg_nenashev ]

R. Tyler Croy made changes - 2016-07-25 23:50

Workflow

Original: JNJira [ 144964 ]

New: JNJira + In-Review [ 176234 ]

Jesse Glick made changes - 2016-12-12 14:37

Link

New: This issue relates to JENKINS-1948 [ JENKINS-1948 ]

Load more newer history items