-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop job blocks shutdown #298
Comments
Are you running a patch job and then initiating a shutdown? |
Yes, sort of. That's the/a shutdown that the patch job triggered. It might specifically be that a restart was already required before the patch job could run though. I'd need to hunt down a server that currently needs a restart to test that theory. Let me know if that would be useful. |
Hmm, if the agent itself initiated the reboot that should not hang, the only time it will hang right now that I know of is if the agent is executing another task like say apt-get, right now it wont cancel those processes if issued a shutdown command from systemd. Ill see if I can reproduce this. Just to double check, you arent trying to reboot from a pre or post script are you? |
Also if you have the agent logs from the patch job that would be helpful. |
I'm not. Here's an example log:
|
Ok, so it looks like the job works fine, but during the reboot it takes an extra 90s because the agent wont stop. |
With this flag customers can choose to disable the configuration management for OS Login cert based authentication.
Hi,
I'm running agent version 20210217.00-g1 on Ubuntu 20.04, and when a patch job is deployed, shutdown appears to be blocked by the OSConfig Agent for 90s. Below is the serial terminal output:
Thank you-
The text was updated successfully, but these errors were encountered: