|
||||||||
|
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.
You can have it even if the Slave is not launched as a service: I made a test launching an infinite loop always with the same job (approx 1.5hrs), after some loops I took the error.
At the same time ping works perfectly (so it's not a network problem), and all the process where alive (no trace of crash/restart/etc in logs).
I got all the logs if you need.
Update: We where really unlucky with the previous test, we had a bigger problem with the machines it was not a Jenkins one.