I created a new Ubuntu 22.02 LTS instance two days ago. Instance type T2.Medium.
Every night at about 08:20 UTC I get an error message in the log 'eth0 Could not set route: Connection Timed Out'. up until this point my log is full of standard docker messages about mounts being deactivated and the application is running fine.
All normal messages have stopped, docker isn't deactivating various runc.* mounts up until this point. once that eth0 could not set route message appears the runc messages stop
after that the instance is unreachable and fails the instance checks, I am unable to stop it gracefully. Once it is force stopped, and restarted then it was fine again, until that time the next day when network connectivity is lost. This has happened two days in a row.
There is no indication in the syslog except that eth0 timed out, and fails. I've had machines ssh'd into it and they get disconnected.
AWS OFFICIALUpdated a year ago
thanks. I am flying close to the limit about 85% utilized. I'll give that a try.
Pls Let me know your results...
interesting, would not expect the network to drop on low memory like that, but with an 8GB instance it survived the day so guess that is it.
Thats great news and thanks for letting me know.. Yeah I have seen it before in mytime within AWS resource constraints can cause EC2's to become unresponsive. You should be set now. You could experiment with t3.medium as its cheaper etc.. Good luck