I've experienced this error in my corporate network where the agent was just so
busy with the Jenkins job that it didn't respond to monitoring and monitoring
rebooted the machine. I don't know aws, but if it's easy to check it could be
worth ruling out
--
You received this message because you
Hi all,
I showed up late to the party, so I'll accept a snub gracefully, but I was
intrigued by the problem of replacing the term "master" and have one further
term I would like to put in the poll if at all possible.
Dispatcher.
This would most correctly apply to the function of taking jobs
