The process stops with code 137
Confirm an OOM shutdown, reduce memory consumed, and avoid a restart loop.
Code 137 generally corresponds to a SIGKILL, often sent when the container exceeds its memory limit. It can also follow a forced stop from the panel.
Step-by-step procedure
-
Check the context
Look for a memory spike, Killed or a reboot right after a heavy task.
-
Limit loads
Reduce cache, concurrency, batch size or number of workers. Avoid loading large files entirely in RAM.
-
Check for a leak
Monitor if memory continually increases even without activity.
-
Adapt the offer
Increase the RAM only when normal and optimized consumption still exceeds the limit.