control: tags -1 moreinfo Am 22.11.2014 um 23:33 schrieb brian m. carlson: > retitle 770644 systemd: systemd is completely unusable after a fatal signal > # Justification: breaks the whole system, not suitable for release > severity 770644 serious > kthxbye > > On Sat, Nov 22, 2014 at 09:34:03PM +0000, brian m. carlson wrote: >> Package: systemd >> Version: 215-6 >> Severity: important >> >> I'm trying to start strongswan: >> >> castro ok % sudo service strongswan start >> Failed to get D-Bus connection: No such file or directory >> >> Okay: >> >> castro ok # systemctl start dbus >> Failed to get D-Bus connection: No such file or directory >> >> So I start dbus by hand (à la /etc/init.d/dbus), and: >> >> castro ok # service dbus restart >> Failed to restart dbus.service: Launch helper exited with unknown return >> code 1 >> castro ok # service freeradius restart >> Failed to restart freeradius.service: Launch helper exited with unknown >> return code 1 >> castro ok # sudo telinit u >> Failed to execute operation: Launch helper exited with unknown return code >> 1 >> >> Perhaps systemctl needs to learn a non-dbus way to talk to systemd. >> telinit should be using signals, not dbus, to signal init. >> >> systemd also does not fix itself even after receiving a SIGHUP, SIGUSR1, >> or SIGTERM. > > Even better is this: > > castro ok % sudo shutdown -r now > Failed to open initctl FIFO: No such device or address > Failed to talk to init daemon. > > I just noticed that the issue is that systemd called assert. I've > attached an image of the console when this happened. I don't think I > need to explain why using assert in /sbin/init is a bad idea. >
Can you provide steps how this issue can be reproduced? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
