Closed copolycube closed 3 years ago
This actually seems to be an issue on the SSM Document, not on the SSM agent. Closing the issue here since this project seems to be only related to the agent...
"Exit Code 196 means "Reboot With Dependency Failure", meaning the operation fails for the reason some package update patch manager tries to install on your instance fails because that package update has dependency on packages that are explicitly rejected (and blocked) by the baseline.
Here is a scenario where Exit Code 196 is observed: the patch baseline rejects some package "A", and the rejected patches action is selected as "Block", then if patch manager finds a package "B" that meets the criteria specified in your baseline, and updating "B" requires installing "A", the updates fails with Exit Code 196.
Edited by: ziyelinaws on Jan 21, 2021 8:20 AM "
Hello,
I'm not sure where would be the best place to ask a question I am currently facing with the AWS document run through the ssm agent "AWS-RunPatchBaseline", feel free to close the issue if this is not the proper place !
I am facing some issue with the SSM maintenance windows I configured and am progressively rolling out over a fleet of several hundreds of servers. I tried to segregate the issues as I encounter them and will hence focus on a single one I observed and I'm not able to find informations about it online so far.
All my maintenance windows are configured to "RebootIfNeeded", but I observe recurrently the following message :
[ERROR]: Patching Operation failed with exit code 196 but instance needs reboot
Would you know how I should interpret this ? Would anyone have a clue on the possible mitigations ? Those instance have been deployed manually (no cloudformation involved, no terraform involved), and where not rebooted externally.
Thanks in advance for your help !
Log extract from the end of the stdout logs pushed to an s3 bucket (sparing you the beginning with the multiple installation stages) :