Bug#755581: systemd: emergency mode infinite loop after systemd upgrade

[Johannes Schauer]

Hi Michael,

sorry that it took me two days to come back to you but I was attending the
Debian Bootstrap sprint and could not afford to reboot my laptop and end up
with a possibly broken system these days.

Quoting Michael Biebl (2014-08-19 16:15:31)
> Johannes, it seems that we tracked this issue down. Sorry it took so long.
> 
> The problem is an active syslog.socket when emergency mode is entered.
> Each log message then tries to start rsyslog.service which conflicts
> with the emerge service (due to the dependencies rsyslog.service has).
> 
> We need to make sure that syslog.socket is stopped when the emergency
> mode is entered.
> 
> Adding Conflicts=syslog.socket to emergency.service [1] seems to be an
> acceptable workaround.
> 
> It would be great if you can confirm that this also fixes the problem of
> the failing emergency mode for you.

I added Conflicts=syslog.socket to the [Unit] section of
/lib/systemd/system/emergency.service and can confirm that after the boot
failed, I now get correctly dropped into emergency mode.

Thanks a lot for fixing this!

I see that you closed this bugreport. Is the issue of my filesystems not being
mounted tracked under another bug?

cheers, josch