[SOLVED] Proxmox lxc start issue after apt upgrade

B

BurningSquirrel-de

Member
May 25, 2021
38
4
13
Essen, Germany
Hello,

after apt full-upgrade and reboot of the host, my lxc do not start anymore.

Log shows:

Bash: 
lxc-start 70561 20221117092904.334 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type u nsid 0 hostid 100000 range 65536
lxc-start 70561 20221117092904.335 INFO     confile - ../src/lxc/confile.c:set_config_idmaps:2267 - Read uid map: type g nsid 0 hostid 100000 range 65536
lxc-start 70561 20221117092904.342 INFO     lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor
lxc-start 70561 20221117092904.343 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "70561", config section "lxc"
lxc-start 70561 20221117092904.325 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 70561 lxc pre-start produced output: objdump on /usr/lib/systemd/systemd failed: open3: exec of objdump -p /var/lib/lxc/70561/rootfs/usr/lib/systemd/systemd failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 455.
lxc-start 70561 20221117092904.331 ERROR    conf - ../src/lxc/conf.c:run_buffer:321 - Script exited with status 2
lxc-start 70561 20221117092904.331 ERROR    start - ../src/lxc/start.c:lxc_init:847 - Failed to run lxc.hook.pre-start for container "70561"
lxc-start 70561 20221117092904.331 ERROR    start - ../src/lxc/start.c:__lxc_start:2008 - Failed to initialize container "70561"
lxc-start 70561 20221117092904.331 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxc/hooks/lxc-pve-poststop-hook" for container "70561", config section "lxc"
lxc-start 70561 20221117092904.606 INFO     conf - ../src/lxc/conf.c:run_script_argv:337 - Executing script "/usr/share/lxcfs/lxc.reboot.hook" for container "70561", config section "lxc"
lxc-start 70561 20221117092905.108 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:306 - The container failed to start
lxc-start 70561 20221117092905.108 ERROR    lxc_start - ../src/lxc/tools/lxc_start.c:main:311 - Additional information can be obtained by setting the --logfile and --logpriority options

Mark on:
Bash: 
lxc-start 70561 20221117092904.325 DEBUG    conf - ../src/lxc/conf.c:run_buffer:310 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 70561 lxc pre-start produced output: objdump on /usr/lib/systemd/systemd failed: open3: exec of objdump -p /var/lib/lxc/70561/rootfs/usr/lib/systemd/systemd failed: No such file or directory at /usr/share/perl5/PVE/Tools.pm line 455.

Has someone an idea?

Regards
 
Hello,

All LXCs have the same results? Please provide us with the container config (pct config CTID) and the output of pveversion -v as well
 
Hi Moayad,

all LXCs same result, VMs working.

config:
Bash: 
arch: amd64
cores: 1
features: nesting=1
hostname: cSrv-Mosquitto
memory: 1024
nameserver: 10.0.0.8
net0: name=eth0,bridge=vmbr2,firewall=1,hwaddr=92:9E:AB:42:4F:E7,ip=dhcp,ip6=auto,type=veth
onboot: 1
ostype: debian
rootfs: local-zfs:subvol-70601-disk-0,size=8G
searchdomain: extern.mydomain.de
startup: order=51,up=30
swap: 1024
unprivileged: 1

pveversion:
Code: 
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-13 (running version: 7.2-13/c1285997)
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-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-7
libpve-guest-common-perl: 4.2-1
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-10
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.1
pve-cluster: 7.2-2
pve-container: 4.3-3
pve-docs: 7.2-3
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
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-8
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
 
I had the same after updating today. This was on a Hetzner server.
 
Last edited:
I had the same problem, after installing binutils the error message changed to this:
Code: 
# lxc-start -n 201 -F
lxc-start: 201: ../src/lxc/conf.c: run_buffer: 321 Script exited with status 255
lxc-start: 201: ../src/lxc/network.c: lxc_create_network_priv: 3427 No such device - Failed to create network device
lxc-start: 201: ../src/lxc/start.c: lxc_spawn: 1843 Failed to create the network
lxc-start: 201: ../src/lxc/start.c: __lxc_start: 2074 Failed to spawn container "201"
lxc-start: 201: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: 201: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

pct config 201:
Code: 
arch: amd64
cores: 3
features: nesting=1
hostname: services2
memory: 2048
net0: name=eth0,bridge=vmbr0,gw=192.168.193.1,hwaddr=B2:70:13:0F:B6:8C,ip=192.168.193.43/24,tag=193,type=veth
onboot: 1
ostype: debian
rootfs: local-zfs:subvol-201-disk-0,mountoptions=lazytime,size=16G
swap: 0
unprivileged: 1

pveversion -v:
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
openvswitch-switch: 2.15.0+ds1-2+deb11u1
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

I use openvswitch.
ovs-vsctl show:
Code: 
7e6748ac-cd86-41bb-8871-13bfe1b649a6
    Bridge vmbr0
        Port vlan1
            tag: 1
            Interface vlan1
                type: internal
        Port enp3s0
            trunks: [1, 193]
            Interface enp3s0
        Port vmbr0
            Interface vmbr0
                type: internal
    ovs_version: "2.15.0"

After I enable the firewall in CT, the container starts working; when I disable the firewall, I get the error message again.

A similar problem occurs if I try to boot a VM instead of CT:

Code: 
RTNETLINK answers: Operation not supported
TASK ERROR: command '/sbin/bridge fdb append AA:EB:24:B9:21:4F dev tap501i0 master static' failed: exit code 255

Unlike CT, however, VM will still start.
 
Last edited:
Had the same issue after updating proxmox an hour ago. Found this and installing "binutils" fixed it.

Is this the official way to fix it or just a workaround?
 
HUGE thank you to this thread. Installing binutils AND rebooting the node solved my container issues.
 
Had a similar issue, could not get LXC container to start after upgrading to 7.2-14 from 7.2-11

The errors I got were as follows:
-------------------------------
run_buffer: 321 Script exited with status 2
lxc_init: 847 Failed to run lxc.hook.pre-start for container "120"
__lxc_start: 2008 Failed to initialize container "120"
TASK ERROR: startup for container '120' failed
-------------------------------

Thanks to this post I did this:
apt-get install binutils

Started LXC container and it started up without error.
 
This morning, I have updated Proxmox to 7.2-14 and no LXC started. The binutils fixed it.
 
I had the same issue, no containers would start and all my services were down. What is odd is the update is still available without the fix included. How many more will screw up their systems for no good reason.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom