loading...empty;done;/oom-killer-non-leaking-processes/:-uriNon-Leaking Processes | iNET.elastic Dev Docs

OOM Killer Resolutions: Non-Leaking Processes

Processes, listed in this section, could be terminated by OOM killer in attempt to free RAM for other operations, though commonly they do not cause memory leak problems by themselves:

ProcessResolution
112x4Restart container in order to restore the process
112x6Restart container in order to restore the process
ahnRestart container in order to restore the process
anytermdRestart container in order to restore the process
apache2Restart container in order to restore the process
apparmor-profilRestart container in order to restore the process
beam.smpRestart container in order to restore the process
dbus-daemonRestart container in order to restore the process
firewall.shRestart container in order to restore the process
freshclamRestart container in order to restore the process
gettyRestart container in order to restore the process
inimuxsockRestart container in order to restore the process
install-infoRestart container in order to restore the process
iojsRestart container in order to restore the process
iptables-saveRestart container in order to restore the process
kindlegenRestart container in order to restore the process
Lxz6Restart container in order to restore the process
mdaRestart container in order to restore the process
mingettyRestart container in order to restore the process
namedRestart container in order to restore the process
nanoRestart container in order to restore the process
nheqminer_cpuRestart container in order to restore the process
nrsysmondRestart container in order to restore the process
pidproxyRestart container in order to restore the process
PM2Restart container in order to restore the process
postmasterRestart container in order to restore the process
rndRestart container in order to restore the process
rpc.statdRestart container in order to restore the process
rpcbindRestart container in order to restore the process
rpmRestart container in order to restore the process
rsmainRestart container in order to restore the process
rsyslogdRestart container in order to restore the process
run-partsRestart container in order to restore the process
running-in-contRestart container in order to restore the process
saslauthdRestart container in order to restore the process
sedRestart container in order to restore the process
semoduleRestart container in order to restore the process
sendmailRestart container in order to restore the process
serviceRestart container in order to restore the process
shRestart container in order to restore the process
simplehttp.pyRestart container in order to restore the process
sleepRestart container in order to restore the process
startpar-upstarRestart container in order to restore the process
statusRestart container in order to restore the process
stressRestart container in order to restore the process
stunnelRestart container in order to restore the process
supervisordRestart container in order to restore the process
syslog-ngRestart container in order to restore the process
tesseractRestart container in order to restore the process
upstart-file-brRestart container in order to restore the process
upstart-socket-Restart container in order to restore the process
upstart-udev-brRestart container in order to restore the process
valhalla_run_roRestart container in order to restore the process
xinetdRestart container in order to restore the process

What’s next?