|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Daniel Beck, I see such behavior on my installations (remoting-2.36). We had to increase the TCP Timeout to minutes due to the extremely unreliable VPN connections between sites, so slaves actually have the 4-minutes timeout. In such case the issue easily appears even if the slave behaves correctly.
BTW, my previous comment applies to the situation, when both WinSW and remoting behave correctly. There could be an issue, so it definitely makes sense to check runaway processes as Daniel proposed.