1 Answer
- Newest
- Most votes
- Most comments
0
I have seen this several times with Linux machines. Usually its due to lack of memory. You may need to increase the instance type to prevent this from re-occuring.
Relevant content
- Accepted Answerasked a year ago
- asked 8 months ago
- asked a year ago
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 9 months ago
Thanks for your reply. I also think so. But I hope I can confirm it. Where can I check the log information?
Select the instance in AWS Console and look in the Monitoring tab. In particular how is CPU utilisation looking?
There are other metrics (such as memory) that aren't displayed, you'll need to setup CloudWatch agent to collect these https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html