Hi, Am 26.09.2013 13:47, schrieb Michael Biebl: > Sep 23 20:48:39 Cunegonde systemd[1]: Reexecuting. > > > Those reload requests are done before systemd has been re-executed.
So, I was finally able to reproduce the issue. The log with the problems related to Reexcuting gave some hints. My initial approach was, to install a minimal wheezy system, install systemd + pcscd + bluez, boot with init=/bin/systemd, make a dist-upgrade to jessie. With that approach, I couldn't reproduce the problem. Apparently there are packages like libselinux which tell init (PID 1) to re-execute during the upgrade and this somehow prevented the issue to show up. What I did to successfully reproduce the issue: - Install minimal wheezy system + systemd + pcscd + bluez. - apt-mark hold udev systemd pcscd bluez - apt-get dist-upgrade to jessie - reboot, with init=/bin/systemd - apt-mark unhold udev systemd pcscd bluez - apt-get dist-upgrade (which now only upgrades the rest) So the sequence of events afaics which leads to the problem is: - systemd is upgraded from v44 to v204 (which had major changes) - pid 1 is systemd v44 - unpack new systemd - a package calls invoke-rc.d foo start, which runs systemctl daemon-reload. This makes the old systemd v44 pick up the new configuration. - A systemctl start foo.service then results in the failure. - After v204 has been fully setup and re-executed in systemd.postint, the problem is gone. So the problem afaics is that we run daemon-reload and start|stop|restart requests while systemd is in an unconfigured|inconsistent state. Upgrading systemd before the upgrade from v44 to v204 would obviously solve that issue, but I don't see an easy why how to enforce that. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
