How Can We Help?
< All Topics
Print

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
cron
crond		Restart the container in order to restore the process
expectCould be caused by git fetch, git pull or git gc processes (probably, due to the project’s big size or slow connection)
git
Initiate Update from GIT with the appropriate button next to your project in a dashboard or just wait for the next auto-deploy being run (if enabled) to restore the git process automatically
git-remote-http
gitlab-projects		Could be caused by git fetch, git pull or git gc processes (probably, due to the project big size or slow connection)
jem
Most likely, one of the latter operations you’ve performed via BitssCloud dashboard (e.g. application deploy, SSL installation, engine change, etc) haven’t been accomplished – just initiate it one more time
nscd
ssh
sshd
systemd
systemd-journal
taskrunner		Restart container in order to restore the process

Table of Contents