Bug#850074: systemd: "Freezing execution" mode breaks batch upgrades

Michael Biebl biebl at debian.org
Tue Jan 3 20:19:05 GMT 2017


Am 03.01.2017 um 21:05 schrieb Zack Weinberg:
> Package: systemd
> Version: 232-8
> Severity: normal
> 
> When the systemd package is upgraded, the running instance of systemd is
> likely to go into 'freezing execution' mode, in which it is unresponsive

This means systemd has crashed for some reason. At this point it freezes
execution and doesn't allow any further actions.

> An ideal fix would be for systemd to support seamless upgrades of itself,
> i.e. pid 1 would re-exec itself using the new binary, without losing
> any state. 

Well, that's actually what's already happening. In postinst we run
systemctl daemon-reexec which will start the new binary and transfer the
state from the old process.

For some reason systemd crashed on your system before that happened.

Can you reproduce the crash or do you at least have a core file from the
crash? Do you have a complete journal log?
Which version of systemd was running (not installed) when you attempted
the upgrade?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170103/8a865829/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list