2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
0
I think it was a buddy version of SSM agent.
Since rebooting and upgrading the issue went away.
0
Hello.
If you connect to Windows EC2 via RDP and check the SSM logs, are there any logs that can help identify the cause?
Also, although it is not Windows, the blog below states that there was a disk capacity problem when the same error occurred.
https://dev.to/awscommunity-asean/aws-ssm-agent-connection-error-3kn9
Contenido relevante
- OFICIAL DE AWSActualizada hace 3 años
- OFICIAL DE AWSActualizada hace 9 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 2 años
Thanks Riku, I see similar issues in the SSM Agent Error logs along with other errors about data channels.. I think i saw others about file handlers.. Im going to try the usual Windows trick switch it off and on again to see if its resolved... Loads of disk free.. Saw that one too
A reboot fixed it.. Good old windows