LXC Debian 10 to 11 => systemd failure

M

mkaatman

Active Member
Apr 22, 2016
12
0
41
123
Switched apt/sources.list and apt/source.list.d from buster to bullseye and did apt update && apt full-upgrade and I end with a systemd failure.

Only thing really installed is wireguard.


Bash: 
    Created symlink /etc/systemd/system/sysinit.target.wants/systemd-pstore.service -> /lib/systemd/system/systemd-pstore.service.
    Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
    Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
    Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
    dpkg: error processing package systemd (--configure):
     installed systemd package post-installation script subprocess returned error exit status 73
    dpkg: dependency problems prevent configuration of systemd-sysv:
     systemd-sysv depends on systemd; however:
      Package systemd is not configured yet.

    dpkg: error processing package systemd-sysv (--configure):
     dependency problems - leaving unconfigured
    Setting up dmsetup (2:1.02.175-2.1) ...
    Errors were encountered while processing:
     systemd
     systemd-sysv
    E: Sub-process /usr/bin/dpkg returned an error code (1)
 
Last edited:
Hi,

I tested it here... works as expected! what is your LXC config look like pct config CTID? and can you provide us with the output of pveversion -v?

EDIT:
the sources.* from the LXC as well
Bash: 
grep '' /etc/apt/sources.list &&  grep '' /etc/apt/sources.list.d/*
 
Last edited:
Thanks for taking a look. Here are the items you requested.

Code: 
root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-3-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-10
pve-kernel-5.13: 7.1-7
pve-kernel-5.11: 7.0-10
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-2
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-5
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-1
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1


Code: 
root@pve:~# pct config 109
arch: amd64
cores: 1
features: nesting=1
hostname: wireguard
memory: 1024
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.2.1,hwaddr=62:3B:E2:11:FB:C6,ip=192.168.2.2/24,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-109-disk-2,size=8G
swap: 1024
unprivileged: 0
lxc.cgroup2.devices.allow: c 10:200 rwm
lxc.mount.entry: /dev/net dev/net none bind,create=dir


Code: 
root@wireguard:~# grep '' /etc/apt/sources.list &&  grep '' /etc/apt/sources.list.d/*
deb http://ftp.debian.org/debian buster main contrib

deb http://ftp.debian.org/debian buster-updates main contrib

deb http://security.debian.org buster/updates main contrib

deb http://deb.debian.org/debian buster-backports main
grep: /etc/apt/sources.list.d/*: No such file or directory
 
No, I had swapped them all to bullseye prior to the upgrade.

Code: 
deb http://deb.debian.org/debian bullseye main
deb-src http://deb.debian.org/debian bullseye main
deb https://deb.debian.org/debian-security bullseye-security main contrib
deb-src https://deb.debian.org/debian-security bullseye-security main contrib
deb http://deb.debian.org/debian bullseye-updates main
deb-src http://deb.debian.org/debian bullseye-updates main
deb http://deb.debian.org/debian bullseye-backports main
deb-src http://deb.debian.org/debian bullseye-backports main
 
mkaatman said:
No, I had swapped them all to bullseye prior to the upgrade.
Click to expand...

But the output inside your container shows buster repos. You need to change them there too, if you want to upgrade your LXC from buster to bullseye.
 
  • Like
Reactions: nqnz
Yes, I'm showing what they are before I started the upgrade. I changed them to bullseye prior to starting within the LXC. (If I hadn't it would have just upgraded buster to the latest packages)
 
Last edited:
In the Debian 10 lxc you have to change the sources to:

Code: 
deb http://ftp.debian.org/debian bullseye main contrib

deb http://ftp.debian.org/debian bullseye-updates main contrib

deb http://security.debian.org bullseye-security main contrib

then upgrade by using apt update -y && apt full-upgrade -y commands. However, you can test that on a test LXC container in your Proxmox VE to see if the issue is repeatable.
 
Just tried it again with your 3 lines. Repeatable.

I think these might be my problem but I don't understand what they are.

Code: 
Setting up systemd (247.3-6) ...
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e/system.journal.
Detected unsafe path transition /var/log -> /var/log/journal during canonicalization of /var/log/journal/d46b5b6aa1b44656b1a8994a8c36a29e/system.journal.

Somehow it seems my ownership on a lot of files is wrong.

Just a temporary test I did:
chown -R root:root /
SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create --prefix /var/log/journal

Now apt full-upgrade -y completes.

Weird, I don't know how the ownership got messed up. I also don't know how to restore ownership to what it should actually be instead of root:root.

Lastly, I noticed a peculiar message during upgrade.

Error! The /var/lib/dkms/wireguard/1.0.20210219/5.10.0-11-amd64/x86_64/dkms.conf for module wireguard includes a BUILD_EXCLUSIVE directive which
does not match this kernel/arch. This indicates that it should not be built.

This post helped me figure that out.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950684
 
Last edited:
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
Back