Common Cases
OOM Killer Resolutions: Common Cases
Use the process name from the OOM notification to identify the appropriate resolution for commonly terminated platform processes.
On this page
Common Process Resolutions
Review the table below and match the terminated process name with its recommended recovery action.
| Process | Resolution |
|---|---|
adt |
Restart the container to restore the process. |
cron |
Restart the container to restore the process. |
crond |
Restart the container to restore the process. |
expect |
The termination may be caused by git fetch, git pull, or git gc, especially when the project is large or the network connection is slow. |
git |
Start a Git update from the dashboard using the update button beside the project, or wait for the next enabled auto-deploy cycle to restore the Git process automatically. |
git-remote-http |
The termination may be caused by git fetch, git pull, or git gc, especially when the project is large or the network connection is slow. |
gitlab-projects |
The termination may be caused by git fetch, git pull, or git gc, especially when the project is large or the network connection is slow. |
jem |
A recent dashboard operation, such as application deployment, SSL installation, or engine change, may not have completed. Start the same operation again. |
nscd |
Restart the container to restore the process. |
ssh |
Restart the container to restore the process. |
sshd |
Restart the container to restore the process. |
systemd |
Restart the container to restore the process. |
systemd-journal |
Restart the container to restore the process. |
taskrunner |
Restart the container to restore the process. |
General Guidance
- Use the exact process name shown in the OOM notification.
- Restart the container when the resolution requires restoring a terminated system process.
- For Git-related processes, retry the repository update or allow enabled auto-deploy to run again.
- For
jem, repeat the dashboard operation that may have been interrupted. - Continue monitoring memory after recovery to confirm that the OOM condition does not return.
Repeated OOM events: When the same process is terminated repeatedly, review the related Memory Leak Processes and Non-Leaking Processes guides to investigate the underlying memory shortage.