Skip to content

v1.1.15 — Fix per-site RAM showing 0

Latest
Latest

Choose a tag to compare

View all tags
@ethandacat ethandacat released this 14 May 06:49
v1.1.15
6549526

Fix: per-site RAM showing 0 KB for running sites

Affects multi-worker processes (gunicorn, node cluster, php-fpm) that survived a panel restart.

Root cause

On panel restart, recoverProcesses() added only the master PID to the site's cgroup. Workers that were already forked before the cgroup was created weren't moved in, so memory.current only counted the tiny master process (~a few MB) or returned 0.

Fixes

  1. recoverProcesses() now scans the master's entire process group and moves every worker into the cgroup immediately — so memory.current is accurate right after restart.

  2. sampleProcs() falls back to summing /proc/*/status RSS by process group when the cgroup is still empty — so RAM is shown correctly even on panels that haven't restarted yet.

Update and restart your panel to fix viewpol and any other multi-worker sites showing 0 KB.

Assets 2
Loading