OOM Killer Resolutions: Common Cases

Examine the following table to get resolutions for some of the most common processes being killed by the OOM tool:

ProcessResolution
adtRestart container in order to restore the process
cronRestart container in order to restore the process
crondRestart container in order to restore the process
expectCould be caused by git fetch, git pull or git gc processes (probably, due to the project big size or slow connection)
gitInitiate Update from GIT with the appropriate button next to your project in dashboard or just wait for the next auto-deploy being run (if enabled) to restore the git process automatically
git-remote-httpCould be caused by git fetch, git pull or git gc processes (probably, due to the project big size or slow connection)
gitlab-projectsCould be caused by git fetch, git pull or git gc processes (probably, due to the project big size or slow connection)
jemMost likely, one of the latter operations you’ve performed via Jelastic dashboard (e.g. application deploy, SSL installation, engine change, etc) haven’t been accomplished - just initiate it one more time
nscdRestart container in order to restore the process
sshRestart container in order to restore the process
sshdRestart container in order to restore the process
systemdRestart container in order to restore the process
systemd-journalRestart container in order to restore the process
taskrunnerRestart container in order to restore the process

What’s next?