Skip to content

Supervisor: OOM

Supervisor may go to OOM, find out when checked running apps from managevisor (no running apps)

How to investigate:

systemctl status supervisord.service --no-pager -l
>>
× supervisord.service - LSB: Start/stop supervisor
     Loaded: loaded (/etc/init.d/supervisord; generated)
     Active: failed (Result: oom-kill) since Wed 2026-06-17 19:52:55 UTC; 8h ago
    Process: 1006082 ExecStop=/etc/init.d/supervisord stop (code=exited, status=0/SUCCESS)
        CPU: 5d 1h 13min 3.306s

Jun 17 19:52:54 ... supervisord.service: A process of this unit has been killed by the OOM killer.
Jun 17 19:52:55 ... supervisord[1006082]: Stopping supervisor: supervisord stopped.

dmesg -T | grep -i "killed process"

[Wed Jun 17 19:52:48 2026] Out of memory: Killed process 1315 (server)
  total-vm:31270640kB, anon-rss:27743088kB, file-rss:1792kB, shmem-rss:0kB,
  UID:0 pgtables:56880kB oom_score_adj:0

How to resolve:

sudo systemctl reset-failed supervisord.service
sudo systemctl start supervisord.service
systemctl status supervisord.service --no-pager

Confirmed healthy:

● supervisord.service - LSB: Start/stop supervisor
     Active: active (running) since Thu 2026-06-18 04:22:24 UTC
      Tasks: 307 (limit: 37339)
     Memory: 2.5G

You may need to restart managevisor afterwards:

https://app.clickup.com/2496230/docs/2c5q6-69975/2c5q6-55728