[Pkg-systemd-maintainers] Bug#723936: Bug#723936: Bug#723936: systemd: fails to upgrade - same behavior

Michael Stapelberg stapelberg at debian.org
Sun Oct 27 21:52:34 GMT 2013


control: tags -1 + pending

Hi,

Michael Biebl <biebl at debian.org> writes:
> I found a simpler way to reproduce the problem:
> - have a standard wheezy system with systemd v44 installed and active as
> PID 1
> - apt-get install bluetooth
> - systemctl stop bluetooth.service
> - rm /lib/systemd/system/var-*.mount
> - systemctl daemon-reload
> - systemctl start bluetooth.service
To dump some state into this bugreport:

I suspected that one cannot get rid of .mount units (at least not in
this case), i.e. var-run.mount is loaded in systemd 44 and you cannot
get rid of it until you reboot — both a daemon-reload and a
daemon-reexec will serialize all state, including that the var-run.mount
unit is loaded and part of local-fs.target.

biebl@ suggested to copy var-lock.mount and var-run.mount to
/run/systemd/system/ in systemd.preinst when upgrading from 44 to 204,
which seems to work just fine in my virtual machine:

Preparing to replace systemd 204-5 (using .../systemd_204-5_amd64.deb) ...
Unpacking replacement systemd ...
…
root at debian-sysv:/tmp# systemctl status var-run.mount
var-run.mount - Runtime Directory
   Loaded: loaded (/run/systemd/system/var-run.mount; static)
   Active: inactive (dead)
          start condition failed at Sun 2013-10-27 17:39:52 EDT; 3min 43s ago
    Where: /var/run
     What: /run

root at debian-sysv:/tmp# systemctl status var-lock.mount
var-lock.mount - Lock Directory
   Loaded: loaded (/run/systemd/system/var-lock.mount; static)
   Active: inactive (dead)
          start condition failed at Sun 2013-10-27 17:39:52 EDT; 3min 46s ago
    Where: /var/lock
     What: /run/lock

root at debian-sysv:/tmp# journalctl | tail -100 | grep -i running
Oct 27 17:42:52 debian-sysv systemd[1]: systemd 204 running in system mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
root at debian-sysv:/tmp# reboot

Broadcast message from root at debian-sysv (pts/0) (Sun Oct 27 17:44:04 2013):
The system is going down for reboot NOW!
…
Linux debian-sysv 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64
root at debian-sysv:~# systemctl status var-lock.mount
var-lock.mount
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

root at debian-sysv:~# ls -l /run/systemd/system/
total 0

I pushed this change:
http://anonscm.debian.org/gitweb/?p=pkg-systemd/systemd.git;a=commitdiff;h=75051b6

-- 
Best regards,
Michael




More information about the Pkg-systemd-maintainers mailing list