You are not logged in.

#1 2019-09-09 15:39:56

vendion
Member
From: Tennessee, USA
Registered: 2010-03-10
Posts: 201
Website

Systemd-nspawn containers fail to boot after recent update

After a recent update to my running kernel and SystemD that was recently pushed to core trying to boot a Systemd-Nspawn container fails which a fairly vague (at least to me error message).

Kernel Version: 5.2.13.arch1-1
SystemD Version: 243.0-1

Trying to boot a pre existing container that was bootable before this update, results in the following error message from `machinectl`

# sudo machinectl start centos
Failed to check whether image centos exists: Unit dbus-org.freedesktop.machine1.service failed to load properly: File exists.

This container image does exist under /var/lib/machines/centos, and there is a container settings file under /etc/systemd/nspawn/centos.nspawn to setup various binds and other settings.

Checking the logs for both the container itself (systemd-nspawn@centos.service) and the DBus process(?) shows the following:

[~]─> sudo journalctl -u systemd-nspawn@centos --since today
-- Logs begin at Sun 2019-04-14 19:57:07 EDT, end at Mon 2019-09-09 11:34:32 EDT. --
-- No entries --
[~]─> sudo journalctl -u dbus-org.freedesktop.machine1.service --since today
-- Logs begin at Sun 2019-04-14 19:57:07 EDT, end at Mon 2019-09-09 11:35:04 EDT. --
Sep 09 10:06:59 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:06:59 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:06:59 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:06:59 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:10 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:16 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:49 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:49 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:54 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:54 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:54 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:54 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:07:54 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:43 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:43 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:43 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:43 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:43 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:46 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:47 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:49 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:51 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:57 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:57 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:57 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:10:57 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
-- Reboot --
Sep 09 10:51:06 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:51:29 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:52:50 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:53:02 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 10:56:39 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.
Sep 09 11:30:43 Vili systemd[1]: dbus-org.freedesktop.machine1.service: Two services allocated for the same bus name org.freedesktop.machine1, refusing operation.

If I do a busctl --list, I do see an instance of "org.freedesktop.machine1" listed but its connection shows as "(activatable)"

org.freedesktop.machine1           - -               -                (activatable) -                         -       -  

As such I'm not sure how to make heads or tails of this. Before it's asked, I have not tried downgrading the kernel and all the systemd packages yet as I would try and workout if there is something wrong on my end or a bug that needs reporting first.

Offline

#2 2019-09-10 00:46:24

glitsj16
Member
Registered: 2015-04-26
Posts: 36

Re: Systemd-nspawn containers fail to boot after recent update

Is /usr/lib/systemd/system/dbus-org.freedesktop.machine1.service a symlink to /usr/lib/systemd/system/systemd-machined.service (as it's supposed to be)?

Offline

#3 2019-09-10 12:07:37

vendion
Member
From: Tennessee, USA
Registered: 2010-03-10
Posts: 201
Website

Re: Systemd-nspawn containers fail to boot after recent update

Yes it is

[~]─> ls -l  /usr/lib/systemd/system/dbus-org.freedesktop.machine1.service
lrwxrwxrwx 1 root root 24 Sep  3 06:10 /usr/lib/systemd/system/dbus-org.freedesktop.machine1.service -> systemd-machined.service

Offline

#4 2019-09-11 10:47:46

vendion
Member
From: Tennessee, USA
Registered: 2010-03-10
Posts: 201
Website

Re: Systemd-nspawn containers fail to boot after recent update

I just downgraded SystemD, and all the SystemD-* packages that was installed, to 242.84-2-arch and the nspawn containers are working again so does definitely appear to be a bug in the newer version that was installed.

Offline

Board footer

Powered by FluxBB