1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Sounds like a problem with the underlying host. You need to stop and start (NOT Reboot) the instance. Then it will get a new host.
beantwortet vor 2 Jahren
Relevanter Inhalt
AWS OFFICIALAktualisiert vor einem Jahr- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 7 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
Thanks! This issue can be solved by 'stop' and 'start' or 'reboot' instance. Any possible reasons to cuase this issue, how can I optimize my instance to prevent this issue?
I'm not sure if you can. A Kernal panic can cause it, so if you avoid that, you have done everything you can. This is just a risk you take when hosting applications (anywhere, not just on AWS). You can mitigate the issue with Instance recovery or other monitoring options. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-recover.html