reassign 758914 systemd
thanks
I've forwarded your mail to the bug. In future please send bug
follow-ups to the bug's email address (as the Reply-To header says), not
just to the individual developer who has responded, so that other
developers can see what's going on.
On 23/08/14 03:30, Bzzzz wrote:
> Setting up dbus (1.8.6-1) ...
> Job for dbus.service canceled.
> invoke-rc.d: initscript dbus, action "start" failed.
...
> Setting up php5-fpm (5.6.0~rc4+dfsg-4) ...
> insserv: warning: current stop runlevel(s) (empty) of script
> `php5-fpm' overrides LSB defaults (0 1 6).
> insserv: warning: current stop runlevel(s) (empty) of script
> `php5-fpm' overrides LSB defaults (0 1 6).
> Job for php5-fpm.service canceled.
> invoke-rc.d: initscript php5-fpm, action "start" failed.
...
> Setting up cups-daemon (1.7.5-1) ...
> Job for cups.service canceled.
> invoke-rc.d: initscript cups, action "start" failed.
You're getting identical symptoms for each service that is started, not
just dbus, so I don't think this is a dbus bug: something has got
confused in systemd.
>From your earlier mail mentioning emergency mode, it sounds as though
systemd is trying to be in emergency mode (which conflicts with other
system services, hence starting those services fails).
Reassigning to systemd. The systemd maintainers will probably want more
information, here are my guesses at useful things you could say in advance:
* whether you deliberately booted in emergency mode or it happened as a
side-effect of something else
* whether you logged-in normally or into the emergency shell
* how long ago you switched from sysvinit to systemd (this boot or a
previous boot?)
* the Journal contents ("journalctl -ba > journal.txt" and send
journal.txt - but check that there isn't anything in there that
shouldn't be public)
* output of "systemctl status -a > status.txt" (same thing applies)
systemd maintainers: if systemd is in emergency mode, would it be
desirable for it to accept and ignore attempts to start services, so
people can `dpkg -i` a package to try to get their system back on its feet?
Regards,
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
