|
||||||||
|
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.
I'm seeing something very close to this on Jenkins 1.594. Our server is running on a CentOS VM, the slaves are Windows 7 VMs running via JNLP as a service. The slave VMs were "moved over" from our Hudson (2.2.1; also running on CentOS) server where we are NOT seeing this issue. The Hudson service as well as files/directories were deleted before the VMs were set up as Jenkins nodes. The Hudson and Jenkins instances are running on different CentOS VMs.
We see the problem on all of our Jenkins Windows 7 slaves, and it occasionally occurs multiple times per day per node. My impression is that it is very likely to happen if the slaves sit idle for a long time (say 4+ hours). Once we get a failure, subsequent builds on the same node will run normally.