|
||||||||
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.
As requested by Kohsuke Kawaguchi attached is the stack-trace I'm seeing:
This eventually leads to a bunch of slaves no longer appearing to be connected to our master jenkins, restarting the master does not affect this, and we need to restart the slaves individually. Notably this does not affect all our slaves. (But the ones that are affected, are always the same ones!)