|
||||||||
|
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.
Our team is facing the connection reset issue, too. We've tried various version of Jenkins, ranging from 1.4xx to 1.6xx, but the issue seems somewhat random:
Before the issue happens, the slave works well. However, several slaves are just don't work. Tried re-create slave VMs, doesn't help much. Newly created slave would suffer the issue after working well for 1 or 2 days.
Build lasts from several minutes to hours, usually connection reset happens 1~2 hours after build starts, (long-lasting jobs) but slave is not offline.
What's wired, one of our master/slaves never suffered from such issue. It's using 1.469 – Change new server to this version doesn't help.
—
We are using Windows 7 Enterprise 64bit on LAN, all slaves are hosted on vSphere. Slaves are connected via web start/install as service.
—
Edit: It turns out we have made a silly mistake. Previously we are using Windows Server 2003/2008, which doesn't have Power Option set to "sleep every 30 min", which is the default option of Windows 7.
We found the power option issue by examine all system events at time when socket timeout happened on each master/slave.