Field guide to command line failures · reference only, nothing hosted here
CliHelper

Exit code 137, and what actually consumed the memory.

Killed

Exit code 137 is 128 plus 9

Signal 9 is SIGKILL. Nothing handles it and nothing is flushed, so the process simply stops.

Confirm it was the OOM killer

dmesg -T | grep -i 'killed process' journalctl -k --since '1 hour ago' | grep -i oom

Read the limits that were hit

ulimit -a cat /sys/fs/cgroup/memory.max 2>/dev/null cat /sys/fs/cgroup/memory/memory.limit_in_bytes 2>/dev/null

Several different limits produce SIGKILL: the kernel OOM killer, a cgroup ceiling, and ulimit -v.

Out of memory and out of disk look similar in a log line but behave differently. Killed with no disk-full message points at memory.

Scope: failure mode: Exit code 137, and what actually consumed the memory.

CliHelper documents failure modes of third-party command line tools. No software is stored or distributed here.

Terms Privacy Contact support@clihelper.pro