Hello,
after today's upgrade (apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y) to the latest version of Proxmox, our LXC containers are grayed out.
The following error can be seen:
I can restart lxc.service and it will resolve the issue we are having, but this will also restart all LXC container and this is something that we do not want right now. Is there something else we can do to resolve the issue without restarting lxc.service?
Best regards,
after today's upgrade (apt-get update && apt-get upgrade -y && apt-get dist-upgrade -y) to the latest version of Proxmox, our LXC containers are grayed out.
The following error can be seen:
Bash:
root@pmx-ssd01:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-05-19 15:16:19 CEST; 7min ago
Process: 23943 ExecStart=/usr/bin/pvestatd start (code=exited, status=0/SUCCESS)
Main PID: 23953 (pvestatd)
Tasks: 1 (limit: 4915)
Memory: 92.0M
CGroup: /system.slice/pvestatd.service
└─23953 pvestatd
May 19 15:23:29 pmx-ssd01 pvestatd[23953]: lxc status update error: short read on command socket (16 != 0)
May 19 15:23:30 pmx-ssd01 pvestatd[23953]: lxc console cleanup error: short read on command socket (16 != 0)
May 19 15:23:39 pmx-ssd01 pvestatd[23953]: lxc status update error: short read on command socket (16 != 0)
May 19 15:23:39 pmx-ssd01 pvestatd[23953]: lxc console cleanup error: short read on command socket (16 != 0)
May 19 15:23:49 pmx-ssd01 pvestatd[23953]: lxc status update error: short read on command socket (16 != 0)
May 19 15:23:50 pmx-ssd01 pvestatd[23953]: lxc console cleanup error: short read on command socket (16 != 0)
May 19 15:23:59 pmx-ssd01 pvestatd[23953]: lxc status update error: short read on command socket (16 != 0)
May 19 15:23:59 pmx-ssd01 pvestatd[23953]: lxc console cleanup error: short read on command socket (16 != 0)
May 19 15:24:09 pmx-ssd01 pvestatd[23953]: lxc status update error: short read on command socket (16 != 0)
May 19 15:24:10 pmx-ssd01 pvestatd[23953]: lxc console cleanup error: short read on command socket (16 != 0)I can restart lxc.service and it will resolve the issue we are having, but this will also restart all LXC container and this is something that we do not want right now. Is there something else we can do to resolve the issue without restarting lxc.service?
Bash:
root@pmx-ssd01:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.3.18-3-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-2
pve-kernel-helper: 6.2-2
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-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: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-6
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1Best regards,
