|
||||||||
|
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.
Slave disconnects had seemed to reduce occurrence for me for awhile there, but I'm now again experiencing intermittent disconnects.
I connected to the slave directly, and found slave.jar was still running. It seems this causes an issue, because if I tell the Master to reconnect to the Slave, it launched a second slave.jar instance on the slave, rather than reconnecting to the already running instance. And then, of course, the job(s) that were running, never get their status updated.
It seems to me that Ping is simply unreliable, as it's what's killing the instance connections, it would appear.
Log: https://gist.github.com/intel352/0fd5ff26205a3e456c39