Thanks for the suggestion. One of the ways that we reduced the impact of the disconnects was by clicking the "Relaunch agent" button every few minutes for agents that are disconnected. We implemented that after observing that many times the agent will reconnect when the relaunch agent button is clicked by an administrator. We can certainly double check that there is no async reboot of the agent, but I don't expect there to be one.
On Sat, Aug 8, 2020 at 5:28 AM Steve Carter <[email protected]> wrote: > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/d2abc458-42a7-4e76-b919-04222bf49cc8o%40googlegroups.com > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE7roqJehXGjpABjV7HEssFsSe6SPzh0WHmSsWv6GUN3w%40mail.gmail.com.
