instance is going unaccessible with a health check failure after a week after scheduler deployed.

Question

Hi,
This is regarding the AWS EC2 instance we have launched under our aws account. Instance ID is i-075037668099bd31d.

This has our under development project demo deployment and it has a process which is deployed like a scheduler which connects for third party APIs like 
WooCommers, Shopify and etc. There are considerable number of REST API calles we trigger with this sceduler process.  However we noticed that
i-075037668099bd31d instance is going unaccessible with a health check failure after a week after scheduler deployed.

Even though we have optimized memory handling of our scheduler process, still this EC2 instance health check fail issue comes in. 
Therefore if would be great if you can let us know what was 
the exact issue for health check failure on this instance.

Further I have CC this to my developer as well.

Thank you.
Natoli.

Answer

There might be a lot of reasons for health check to fail, like CPU, memory, disk, network, kernel, etc. So, have you already confirmed that the memory is the issue here? 
If not, check these below documentations and troubleshoot accordingly.\
[+] https://repost.aws/knowledge-center/ec2-linux-status-check-failure\
[+] https://repost.aws/knowledge-center/ec2-linux-status-check-failure-os-errors

I also recommend setting up atop and sar on the instance to monitor the resource utilization at OS level. You can later use this to investigate if there were any spikes in resource utilization during the time of incident.\
[+] https://repost.aws/knowledge-center/ec2-linux-configure-monitoring-tools

instance is going unaccessible with a health check failure after a week after scheduler deployed.

関連するコンテンツ