PCT list not working

mathx

Renowned Member
Jan 15, 2014
172
3
83
Something is out of sync

cant pct list:

can't open '/sys/fs/cgroup/cpuacct/lxc/741/ns/cpuacct.stat' - No such file or directory

how to fix?


proxmox-ve: 5.4-2 (running kernel: 4.15.18-20-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-8
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-6
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 
hi,

did you try to reboot?
what's on container 741?
 
I fear rebooting the whole server as nothing may work afterwards if this problem is deep. Also I come from a culture of "reboot as last resort as you may not get access to the machine afterwards" (even with BMC/IPMI).

Nothing special but a deb9.8 container 741. Something is corrupt on this server, been having odd issues ever since though I have done nothing special to it ever. I will move all the containers off and reinstall it.
 
i'd also check for hardware issues to avoid future problems.
 
update: was finally able to move 741 off the server and pct destroy 741 it, and now I can pct list. However, I still dont trust the server due to repeated situations where I pct enter into a CT and get "proc not mounted" whereas ssh'ing in works ok. something bizarre is afoot. and now has started occuring on another PVE host.
 
This continues to happen on multiple 5.x hosts where /proc disappears to certain contexts (ie pct enter for eg, while SSH in works -- probably because SSH is inheriting a working context from the daemon whereas pct enter is a new context initliaization). Will report if it occurs in 6.x. Dont have enough experience yet with 6.x hosts/ct's.

Due to this problem, I am not trusting any upgrades from 5.x to 6.x, but doing full reinstalls. A lot more work.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!