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:

Process Resolution
adt Restart container in order to restore the process
cron
crond
expect Could be caused by git fetch, git pull or git gc processes (probably, due to the project big size or slow connection)
git Initiate 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-http Could be caused by git fetch, git pull or git gc processes (probably, due to the project big size or slow connection)
gitlab-projects
jem Most likely, one of the latter operations you’ve performed via Apiqcloud dashboard (e.g. application deploy, SSL installation, engine change, etc) haven’t been accomplished - just initiate it one more time
nscd Restart container in order to restore the process
ssh
sshd
systemd
systemd-journal
taskrunner
  • OOM Killer Resolutions: Common Cases
  • 0 användare blev hjälpta av detta svar
Hjälpte svaret dig?

Relaterade artiklar

OOM Killer Issues Troubleshooting

  When receiving an OOM killer load alert notification via email, the next step you should...

OOM Killer Resolutions: Processes with High Risk of Memory Leak

Pay special attention to the processes in this group as to the most probable cause of your...