|
||||||||
|
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/d/optout.

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 the log above) => All scheduled builds fail with an error
The issue affects ssh-slaves only:
I'm not sure if there's any Linux specifics in the issue.![]()
On my installation default TCP timeouts exceed the PingThread timeout on the master, hence there could be a collision on the server side