Closed copolycube closed 3 years ago
IPC file not readable is a confusing error message and we have reduced the severity of the log line to debug: https://github.com/aws/amazon-ssm-agent/commit/bf3772897eb3d74d277c41c88f7a9593d99934c6
Too many files open is a separate issue where the agent reaches a OS limit of number of file handles allowed. We recently made fixes for where the logger was not cleaning up file handles correctly and was released in v3.0.529.0 https://github.com/aws/amazon-ssm-agent/commit/7d282d23e14cb652d0c80b5c989a7af227b4be48
If you still encounter issues with 'too many open files' error, please take a look at this previous ticket https://github.com/aws/amazon-ssm-agent/issues/330. Feel free to open another ticket if you still encounter issues with your setup.
Hello @Thor-Bjorgvinsson and thanks a lot for your answer. I will make sure that all the servers ssm agents are upgraded (I also saw this ipc error in the auto-upgrade tasks so I fear that it's not upgraded everywhere consistently yet).
Hello,
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 so that /tmp be fully writable, and I don't have space issue :
But I observe recurrently the following message (extended extract bellow) in the logs generated locally in
/var/log/amazon/ssm/amazon-ssm-agent.log
:Would anyone have hints on how I should I interpret this, and what resolution could I apply ? What mitigation would you suggest ?
Thanks in advance, any help or suggestion would be greatly appreciated !