Proxmox v6.3-3 Problem

[lps90]

Hi guys

My server machine was having problems and crashing (proxmox v6.3-3) and the only problem in the logs it was "unexpected cpu time".
So I decided to format it to see if the problem was solved (formated again with proxmox v6.3-3).
But the same problem is still happening...

"lxcfs[807]: proc_fuse.c: 1018: proc_stat_read: cpu3 from /lxc/300/ns has unexpected cpu time: 17884 in /proc/stat, 18408 in cpuacct.usage_all; unable to determine idle time"

I read several threads about this issue.
Basically i really want to know if this is a problem or if i can just ignore this message.

Details:
Proxmox v6.3-3 (up-to-date)
Intel i9-9900k
128Gb ram
2x samsung 970 evo nvme

 

[oguz]

hi,

could you please post the output from pveversion -v?

is it only this container that's spamming the log? (300)
can you also post the container config from pct config 300

 

[lps90]

pveversion -v output:

proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-4
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-8
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1


pct config 300 output:

arch: amd64
cores: 4
cpulimit: 4
hostname: RustServer
memory: 8192
net0: name=eno1,bridge=vmbr0,firewall=1,gw=192.168.3.1,hwaddr=DE:E6:30:F0:E3:9D,ip=192.168.3.50/24,rate=25,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-300-disk-0,size=15G
swap: 512
unprivileged: 1


For now it is just this container 300 that is spamming the log...

 

[lps90]

And the same problem is happening...
Server is crashing after some time.
I'll leave some log files uploaded, maybe you can tell me what is really the problem (i'm loosing my mind!)

 

[lps90]

Any possible solution?
Update: Now it is doing the same with other containers.

 

[lps90]

This "lxcfs[807]: proc_fuse.c: 1018: proc_stat_read: cpu3 from /lxc/300/ns has unexpected cpu time: 17884 in /proc/stat, 18408 in cpuacct.usage_all; unable to determine idle time" thing is now happening with all my proxmox dedicated servers (4x OVH/Soyoustart and 2x HomeMachines).

*Another thing i notice is that this is happening basically with game server containers (CsGo, Rust, Ark: survival evolved...)

Is this a general "problem"?
It is an important warning?

 

[oguz]

this error shouldn't be fatal, according to [0]

cores: 4
cpulimit: 4

you could try disabling/commenting the cpulimit variable in the config to see if it changes anything. i'd also restart lxcfs and the containers. then check if you see anything weird in the logs or if it crashes again


[0]: https://github.com/lxc/lxcfs/issues/283

 

[lps90]

"you could try disabling/commenting the cpulimit variable in the config to see if it changes anything"
Nothing changes. Some of the lxc containers do not even use cpulimit.