Skip to content

Ec2 instance goes unresponsive - instance unreachablity error - status check failed

0

Hi, my Ec2 instance goes unresponsive - instance unreachablity error - status check failed as a result my EC2 free tier instance has turned unresponsive twice in last 48 hours. I don't see any obvious error in System logs. My instance is running Hestia CP with mail server from same instance as web. Have noticed CPU usage beyond 90+% immediately after rebooting instance. Could this be a reason for unreachablity of Instance? How to fix it?

3 Answers
0

The instance status check fails when the instance load is high, such as memory depletion, as described in this document.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-system-instance-status-check.html#types-of-instance-status-checks

So the reason why we can no longer connect to your instance is because of the heavy load.
Possible countermeasures include using a larger instance size than now or selecting an instance type that is appropriate for the application workload.
https://aws.amazon.com/ec2/instance-types/?nc1=h_ls

Also, if you are able to deploy load balancing workloads, consider deploying an ELB in front of the instances to distribute the load among multiple instances.

EXPERT

answered 3 years ago

0

2/2 checks for system and hardware faults. In either in systems faults stop and reboot the instance. This should replace the faulty EBS image with a new image of an instance. For hardware fault perform a termination of the EC2 and then launch a new EC2 instance.

answered 3 years ago

0

Use CloudWatch the monitor the CPU and Memory Disk and Network Metrics Data points in the Log stream Group. Stop the instance and change the instance type accordingly.

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.