AaPanel Load Status read Host instead VPS on Debian 12 (Proxmox LXC)

aaP_kotakomputer.ceo

Proxmox - LXC Debian 12. Aapanel installed inside LXC Debian 12 read Proxmox Host CPU Avg Load, instead VPS CPU Avg load. While Debian 11 has no issue.

Solution using "ExecStart=/usr/bin/lxcfs -l /var/lib/lxcfs/" has no effect on Proxmox 8.4.1.
The "top" command report right cpu load, so this issue may not related to LXC, but how aaPanel interact to Debian 12.
Try to update aaPanel Stable 7.0.20 to aaPanel Beta 7.38.0 but still error.

Any suggestion to fix this issue?

aaPanel_Kern

Hello,
This should be caused by system problems. aaPanel is a system running environment that is read directly
Is it normal to use VM directly?

aaP_kotakomputer.ceo

aaPanel_Kern

But the "top" command read VPS load instead Node load. Here is the ss of Proxmox Node, aapanel Load Status and top-command. This bug only happen on Debian 12/Ubuntu 22, while Debian 11/Ubuntu 20 working fine.

aaPanel_Kern

Hello,
It is recommended that you use the VM first to check whether it is normal. The Debian-12 used by the LXC container may be caused by the information of the Proxmox node directly mapping.
aaPanel is system information obtained through the python library.

aaP_kotakomputer.ceo

It is not normal, for Node with 64 vcpu and Load Avg 0.5 mean 32 vcpu in use. Then VPS with 8 core and real Load Avg 25%, will show Load Status 400% in RED Color, because Load Avg become 32 vcpu instead 2 vcpu (8 x 25% = 2 cpu).

Again.. This does not happen on Debian 11/Ubuntu 20.04, only problem on Debian 12/Ubuntu 22.

aaPanel is system information obtained through the python library.

As you described above, also some one has similar issue and suggest solution, please check here: https://github.com/lxc/lxc/issues/4372