Bug#761306: Bug#771101: wheezy -> jessie dist-upgrade failure when systemd is the active PID1

Michael Biebl biebl at debian.org
Thu Nov 27 01:49:24 GMT 2014


control: forcemerge -1 761306

Am 26.11.2014 um 23:06 schrieb Michael Biebl:

> I think, that's the relevant part from the journal, specifically:
> 
>> Nov 26 19:36:57 debian systemd[1]: bind(@run/systemd/notify) failed: Address already in use
>> Nov 26 19:36:57 debian systemd[1]: Failed to reload: Address already in use
> 
> Running lsof /run/systemd/notify, doesn't show any process listening on
> the socket.
> systemd-udevd in v215 uses Type=notify and I suspect it get's stuck in
> State activating since the sd_notify call doesn't succeed.
> 
> I remember Sjoerd running into this issue as well, but I don't remember
> anymore if he found the root cause and how to fix it.

I think it's the same bug as [1] and since this affects the dist-upgrade
from wheezy, I think a RC severity is justified.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761306
-- 
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: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20141127/39795521/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list