- Newest
- Most votes
- Most comments
Thanks for the answer John.
Exactly as you wrote: it does work correctly for a while, but then becomes "Unhealthy" and is not reachable any more. I cannot SSH into the instance when it is not responding.
Today it got "Unhealthy" at 13.56: https://i.ibb.co/xmnfXNK/Screenshot-2022-03-01-at-21-28-36.png
In the metrics:
- AVERAGE CPU UTILIZATION: it is almost always just above the sustainable zone and there is a high spike burst (AVERAGE CPU UTILIZATION) at 10.30; then smaller spikes after 18.00: https://i.ibb.co/b2MwKJx/Screenshot-2022-03-01-at-21-27-58.png
- REMAINING CPU BURST CAPACITY (PERCENTAGE): the graph goes down from 50% to 0.89% at 13.50: https://i.ibb.co/NWQzkX3/Screenshot-2022-03-01-at-21-28-10.png
(sorry, I am not able to directly insert images).
Yes, it appears that you are running out of resources on that very small instance. You have two options, bump up to a larger instance that can handle the load, or figure out if there's anything you can eliminate to reduce the resources you are using. The easiest thing to do is option number one. Take a snapshot of your instance and then restore it to a "bigger" Lightsail instance type and see if that keeps you out of the "CPU burstable zone".
+1 on John Vold's comment. You might need a bigger instance.
Now it is not reachable for 2 days in a row.
Did you try upgrading the instance size per my other comment?
Just to be sure, it does work correctly for a while, but then becomes "Unhealthy" and is not reachable any more? Are you able to SSH into the instance when it is not responding? Have you checked the "Metrics" tab to see if anything looks strange in there?
Relevant content
- Accepted Answerasked 10 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 years ago
Hi buddy, just wonder if you have solved your problem because I think I ran into something similar.