CLOSED: Lxc strange status

diaolin

Renowned Member
Jul 7, 2008
332
8
83
Trentino Italy
Hi,
in a strange case i've a running container that generates an error while asking

pct list

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

and despite i cannot list any of other container status in the web interface.
If i list each container manually the result is ok and only one does this error

I've searched into /sys/fs/cgroup/memory/lxc/ and i find only
107-12 and 107-13 as directories containing the ns dir

Take a look at the screenshot please, i think is more clear than my poor english

Anyone has similar problems?

Tx, Diaolin




pct config 107
arch: amd64
cores: 1
features: mount=nfs;cifs,nesting=1
hostname: sbbbeta.meles.net
memory: 8192
mp0: store:107/vm-107-disk-1.raw,mp=/home,acl=1,backup=1,size=10G
net0: name=eth0,bridge=vmbr1,firewall=1,hwaddr=6E:04:2A:C7:80:56,ip=192.168.81.107/24,type=veth
net1: name=eth1,bridge=vmbr0,firewall=1,gw=185.161.193.1,hwaddr=02:AD:11:82:36:1C,ip=185.161.193.39/24,type=veth
net2: name=eth2,bridge=vmbr0,firewall=1,hwaddr=42:62:E8:72:85:31,ip=10.10.193.39/16,type=veth
onboot: 1
ostype: debian
rootfs: store:107/vm-107-disk-0.raw,acl=1,size=8G
swap: 8192


# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-23
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
 

Attachments

  • lxc-staus.png
    lxc-staus.png
    74.9 KB · Views: 7
Hi,

First of all, have you edit or can you explain what did you before comes the problem?

Could you try to upgrade your PVE node to PVE 6.3-x [1] then reboot your node and see if the issue is solved, by following this command:
Bash:
apt update && apt dist-upgrade

[1] https://forum.proxmox.com/threads/proxmox-ve-6-3-available.79687/
 

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!