--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhfqWQO_wg-6sh8DJhsJBXPJ5biwiScdrEcZNH%3DOBqkRTA%40mail.gmail.com.
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 are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d2abc458-42a7-4e76-b919-04222bf49cc8o%40googlegroups.com.