WARN: old systemd (< v232) detected.. again

loomes

Renowned Member
May 22, 2018
113
27
68
45
I have some Debian Testing Containers with this Error when i start them.
After some searching and reading i find this: https://git.proxmox.com/?p=pve-cont...;hpb=13b88f5139ff59fe4d951e36dee06e89686a2d5a

OK then i inspect my Testing Containers with this result:
Code:
ldd /bin/systemd-machine-id-setup
        linux-vdso.so.1 (0x00007ffcb5f18000)
        libsystemd-shared-251.so => /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-251.so (0x00007f7b6289b000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7b626bb000)
        libacl.so.1 => /usr/lib/x86_64-linux-gnu/libacl.so.1 (0x00007f7b626b0000)
        libblkid.so.1 => /usr/lib/x86_64-linux-gnu/libblkid.so.1 (0x00007f7b62659000)
        libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f7b6264e000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f7b62613000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7b6260b000)
        libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f7b624c4000)
        libip4tc.so.2 => /usr/lib/x86_64-linux-gnu/libip4tc.so.2 (0x00007f7b624ba000)
        libkmod.so.2 => /usr/lib/x86_64-linux-gnu/libkmod.so.2 (0x00007f7b6249d000)
        liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f7b6247a000)
        libmount.so.1 => /usr/lib/x86_64-linux-gnu/libmount.so.1 (0x00007f7b62417000)
        libcrypto.so.3 => /usr/lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007f7b61f93000)
        libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007f7b61f81000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7b61f77000)
        libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2 (0x00007f7b61f57000)
        libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007f7b61f29000)
        libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 (0x00007f7b61e70000)
        liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f7b61e46000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7b61d03000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7b61ce2000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7b62baf000)
        libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f7b61cb9000)
        libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007f7b61c87000)
        libpcre2-8.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007f7b61be9000)
        libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007f7b61be1000)

libsystemd-shared-251.so is in a place where Proxmox is not searching = Error on start LXC.

PVE Version:
Code:
pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.39-3-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-8
pve-kernel-helper: 7.2-8
pve-kernel-5.15.39-3-pve: 5.15.39-3
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
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-pve1
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-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libqb0: 1.0.5-1
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.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1
 
No stress - thanks for reporting it - at least we do see that it affects more users :)
 
  • Like
Reactions: loomes