| 2017-11-23 01:25:29 |
Tim Penhey |
description |
Observed during prodstack 4.5 upgrade, a number of agents would get stuck attempting to restart for the agent upgrade.
The engine report and goroutine output from the agent pointed at the logsender.
It would get stuck initiating the websocket protocol where it was waiting forever for a response for the server after the server stopped listening to it, in a similar way to bug 1732587. |
Observed during prodstack 4.5 upgrade, a number of agents would get stuck attempting to restart for the agent upgrade.
The engine report and goroutine output from the agent pointed at the logsender.
It would get stuck initiating the websocket protocol where it was waiting forever for a response for the server after the server stopped listening to it, in a similar way to bug 1732587.
To see if this is what is causing the agent to be wedged, ssh in to the machine and run 'juju-goroutines'.
There should be approximately 15-20, and one will be in a tcp read from the logsender. |
|
