jitsi breaks pct list and pve web console: can't open '/sys/fs/cgroup/cpuacct/lxc/673/ns/cpuacct.stat'

mathx

Renowned Member
Jan 15, 2014
172
3
83
A few days ago I added some sound loopback (aloop) stuff to run jitsi in a container. I put this into the lxc/673.conf

lxc.apparmor.profile: unconfined
lxc.cgroup.devices.allow = c 116:2 rwm
lxc.cgroup.devices.allow = c 116:4 rwm
lxc.cgroup.devices.allow = c 116:3 rwm
lxc.cgroup.devices.allow = c 116:6 rwm
lxc.cgroup.devices.allow = c 116:5 rwm
lxc.cgroup.devices.allow = c 116:1 rwm
lxc.cgroup.devices.allow = c 116:33 rwm

then I mknod'd and chowned the /dev/snd devices in the CT, etc. It all works.

Come back to the host and now pct list wont work:

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

If I shutdown the ct, then all is well. If I start it again, same problem immediately.
 
whats your pveversion -v ?
 
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-12-pve: 4.15.18-36
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-7
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
 
Last edited:
This is a more serious issue: I cannot create new containers and the console is partly broken/not reporting anything about any containers (all greyed out) when this container is running.

To add a container, I had to shut down the offending one temporarily.

Any hints?
 
Last edited:
Bump? Zoom is politically compromised, jitsi is becoming a serious application used by customers. Please advise.
 

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!