Bug 59949

Summary:	Completely breaks down if it fails to start dbus.service
Product:	systemd	Reporter:	Michael Biebl <mbiebl>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED FIXED	QA Contact:	systemd-bugs
Severity:	major
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Michael Biebl 2013-01-28 01:44:39 UTC

Version: 197 (F18)

Seems my selinux fs labels got hosed somehow in my F18 VM. As a result, on next reboot, systemd failed to start dbus.service and went completely nuts trying to start it over and over again. All I could do was to forcefully reboot (and start with selinux=0 and forcing a relabel).

You can easily "simulate" the problem by using
ExecStart=/bin/false in dbus.service.

systemd should behave much better in such a case. The least it can do is to stop trying after a while and offer a rescue shell or just continue to boot, since systemd should still be basically functional without a running dbus system bus.

Comment 1 Lennart Poettering 2013-02-04 21:11:13 UTC

I accidentally fucked up the restart suppression logic. This is fixed in git now (and I think michich backported that to F18), with that in place C-A-d at least should work fine still...

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.