[SOLVED] Proxmox lxc start issue after apt upgrade

ned said:
installing binutils solved my issue?
Click to expand...
Sorry I should have mentioned, it resolved my issue too. I just wish, knowing what the issue is, that it was included in the update. Many folks may not come to the forum right away and have services down for a long time while they figure it out. Thankfully for me only my two mail servers were down for 30 minutes. My seven domains, on another proxmox box, and name servers were not rebooted after the update.
 
Hello

same here, installing binutils solved issue, thanks !
FYI I install upgrade on almost 10 serveurs, and there is only one wich have this bug
 
Same issue after running apt dist-upgrade.
Installing binutils solved the issue.

@Moyad, maybe this is something that needs to be fixed in the latest Proxmox version?
 
Thanks. Can confirm. Did the last PVE Upgrade (that one with the kernel/qemu 7.2 upgrade) but didn't rebooted yet and the weekly "stop" mode backup job shut down all the LXCs but none of them would come up again and always failed starting. Doing a apt install binutils fixed it.

Code: 
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-14 (running version: 7.2-14/65898fbc)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-7
libpve-guest-common-perl: 4.2-2
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.2
pve-cluster: 7.2-3
pve-container: 4.3-4
pve-docs: 7.2-3
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.1.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-10
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

Code: 
arch: amd64
cores: 1
features: nesting=1
hostname: DokuWiki
memory: 512
nameserver: 192.168.43.1
net0: name=eth0,bridge=vmbr43,firewall=1,gw=192.168.43.1,hwaddr=A6:D9:2B:XX:XX:XX,ip=192.168.43.69/24,type=veth
onboot: 1
ostype: debian
rootfs: ZFS_LXC:subvol-133-disk-0,size=16G
startup: order=10
swap: 512
unprivileged: 1

Code: 
arch: amd64
cores: 1
features: nesting=1
hostname: ZabbixLXC
memory: 2048
nameserver: 192.168.43.1
net0: name=eth0,bridge=vmbr43,firewall=1,gw=192.168.43.1,hwaddr=0E:98:B0:XX:XX:XX,ip=192.168.43.70/24,type=veth
onboot: 1
ostype: debian
rootfs: LVM-Thin:vm-136-disk-0,mountoptions=noatime,size=32G
startup: order=10
swap: 512
unprivileged: 1

Code: 
arch: amd64
cores: 1
features: nesting=1
hostname: PiholeLXC2
memory: 256
nameserver: 192.168.43.1
net0: name=eth0,bridge=vmbr43,firewall=1,gw=192.168.43.1,hwaddr=16:64:F8:XX:XX:XX,ip=192.168.43.72/24,type=veth
onboot: 1
ostype: debian
rootfs: ZFS_LXC:subvol-138-disk-0,mountoptions=noatime,size=32G
startup: order=2
swap: 128
unprivileged: 1
 
Last edited:
This morning I found the updates libpve-common-perl-7.2-8, pve-container-4.3-6 and qemu-server-7.2-11 in the repositories, which solved my Open vSwitch problem.
 
You must log in or register to reply here.
Top Bottom