EC2 OOM / ENOSPC / Resource Exhaustion Diagnostic Troubleshooter
Use the interactive troubleshooter below to identify your EC2 OOM, ENOSPC, or resource exhaustion symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | no space left — growpart failed | /growpart.31171': No space left on device FAILED: failed to make temp dir | There is not enough free disk space on the volume for growpart to create the temporary directory it needs to perform the partition resize. | Free up some disk space and then try again. |
| 2 | Out of memory / OOM — OOM killer terminating processes | [115879.769795] Out of memory: kill process 20273 (httpd) score 1285879 / Killed process 1917 (php-cgi) | The system completely exhausted its available memory, triggering the OOM killer to terminate the httpd and php-cgi processes to reclaim RAM. | N/A |