Non-Leaking Processes
OOM Killer Resolutions: Non-Leaking Processes
The processes listed below can be terminated by the OOM killer while it attempts to free memory for other operations. These processes usually do not cause memory-leak problems by themselves.
On this page
Non-Leaking Process Resolutions
For each process in this category, restart the container to restore the terminated process.
| Process | Resolution |
|---|---|
112x4 | Restart the container to restore the process. |
112x6 | Restart the container to restore the process. |
ahn | Restart the container to restore the process. |
anytermd | Restart the container to restore the process. |
apache2 | Restart the container to restore the process. |
apparmor-profil | Restart the container to restore the process. |
beam.smp | Restart the container to restore the process. |
dbus-daemon | Restart the container to restore the process. |
firewall.sh | Restart the container to restore the process. |
freshclam | Restart the container to restore the process. |
getty | Restart the container to restore the process. |
inimuxsock | Restart the container to restore the process. |
install-info | Restart the container to restore the process. |
iojs | Restart the container to restore the process. |
iptables-save | Restart the container to restore the process. |
kindlegen | Restart the container to restore the process. |
Lxz6 | Restart the container to restore the process. |
mda | Restart the container to restore the process. |
mingetty | Restart the container to restore the process. |
named | Restart the container to restore the process. |
nano | Restart the container to restore the process. |
nheqminer_cpu | Restart the container to restore the process. |
nrsysmond | Restart the container to restore the process. |
pidproxy | Restart the container to restore the process. |
PM2 | Restart the container to restore the process. |
postmaster | Restart the container to restore the process. |
rnd | Restart the container to restore the process. |
rpc.statd | Restart the container to restore the process. |
rpcbind | Restart the container to restore the process. |
rpm | Restart the container to restore the process. |
rsmain | Restart the container to restore the process. |
rsyslogd | Restart the container to restore the process. |
run-parts | Restart the container to restore the process. |
running-in-cont | Restart the container to restore the process. |
saslauthd | Restart the container to restore the process. |
sed | Restart the container to restore the process. |
semodule | Restart the container to restore the process. |
sendmail | Restart the container to restore the process. |
service | Restart the container to restore the process. |
sh | Restart the container to restore the process. |
simplehttp.py | Restart the container to restore the process. |
sleep | Restart the container to restore the process. |
startpar-upstar | Restart the container to restore the process. |
status | Restart the container to restore the process. |
stress | Restart the container to restore the process. |
stunnel | Restart the container to restore the process. |
supervisord | Restart the container to restore the process. |
syslog-ng | Restart the container to restore the process. |
tesseract | Restart the container to restore the process. |
upstart-file-br | Restart the container to restore the process. |
upstart-socket- | Restart the container to restore the process. |
upstart-udev-br | Restart the container to restore the process. |
valhalla_run_ro | Restart the container to restore the process. |
xinetd | Restart the container to restore the process. |
Recovery Guidance
- Use the exact process name from the OOM notification to find the matching table entry.
- Restart the affected container to restore the terminated process.
- Confirm that the container returns to the running state after restart.
- Continue monitoring RAM usage because a different process may have caused the original memory shortage.
- When OOM events repeat, review the Common Cases and Memory Leak Processes documentation.
Important: These processes are usually victims of memory pressure rather than the original source of the problem. A container restart restores them but may not remove the underlying cause of repeated OOM events.