- 최신
- 최다 투표
- 가장 많은 댓글
When you see an instance failing status checks, try stopping and starting the instance. If the source of the problem was something like the underlying hardware, this approach will typically fix those transient issues. If you see this problem consistently, then it's likely something that you're running inside the instance that is causing it to be unreachable. More details on what the status checks are actually checking here.
It's difficult to say what is happening to your instance; but I would suggest using the EC2 Serial Console to troubleshoot.
Thanks for the reply, but even I can't connect. the strange thing that the status says "System Accessibility Check Passed", but I can't access it, the application is stopped. When I boot, it goes back to normal. I've already reported it to aws, but no one returns. As this service is a test to migrate my company's services, I worry about the level of support if I have a bigger problem. Because of this, maybe they are losing a great future customer.
If (when you reboot) everything goes back to normal then it points to "something" on the instance that is running amok. Start collecting operating system and application logs; looking at metrics (particularly CPU/memory/swap) - all the things that are going to cause the instance to have processes that stop or crash or otherwise are constrained because something else is consuming all resources.
관련 콘텐츠
AWS 공식업데이트됨 3년 전
Thanks for the link, I'm checking out the possibilities. I've already started it 4 times during 8 days, and the problem returns, I'm not running anything abnormal from ec2, it uses 1/3 of the resources (cpu, memory, disk), maybe I'll pay a support to have a more service enlightening, after all I'm testing between aws and gcp. I worry about support in cases like this, after all I'm looking to migrate more than 100 services. This same service is running on gcp , without any failures.