Your message dated Fri, 28 Jun 2019 22:03:20 +0200
with message-id <e181f12d-b04e-ea72-3d6c-3c4a6b30c...@debian.org>
and subject line Re: Bug#931235: shutdown reboots immediately without dbus
has caused the Debian Bug report #931235,
regarding shutdown reboots immediately without dbus
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
931235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-sysv
Version: 241-5
Severity: grave
I have somehow managed to install a buster system with systemd-sysv
(so it boots under systemd) and without dbus (probably because I
installed without recommends).
This has all sorts of ... er... interesting properties. The most
noticeable (and disturbing) one is that `shutdown -r +DELAY` doesn't
work anymore.
root@archive-01:~# shutdown -r +1 "test"
Failed to connect to bus: No such file or directory
root@archive-01:~#
At this point, my SSH connexion froze and the machine stopped
answering pings. I am not exactly sure what happens because I don't
have a console on the server, but I suspect it just did a hard reboot,
because normal shutdown procedures would have killed the sshd process
and therefore closed the connexion (instead of just hanging).
Therefore, not only the +1 minute delay is not respected, but the
shutdown procedure is bypassed completely. The server eventually *did*
reboot so it's not a full crash, but it's still pretty nasty.
I would recommend a hard Depends on dbus for the systemd-sysv package
(which provides the shutdown command) to resolve this problem.
And I think this should be fixed in buster, sorry for the last minute
bug report. :/ I really appreciate your work and systemd is generally
working very well for me, so thank you for that! :)
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd-sysv depends on:
ii systemd 241-5
Versions of packages systemd-sysv recommends:
ii libnss-systemd 241-5
systemd-sysv suggests no packages.
-- debconf-show failed
PS: this bug report was filed on a different machine than the original
one, but the environment should be similar (except the APT policy).
--- End Message ---
--- Begin Message ---
Control: severity -1 normal
Control: tags -1 + wontfix
Hi
Am 28.06.19 um 20:00 schrieb Antoine Beaupre:
> Package: systemd-sysv
> Version: 241-5
> Severity: grave
>
> I have somehow managed to install a buster system with systemd-sysv
> (so it boots under systemd) and without dbus (probably because I
> installed without recommends).
>
> This has all sorts of ... er... interesting properties. The most
> noticeable (and disturbing) one is that `shutdown -r +DELAY` doesn't
> work anymore.
>
> root@archive-01:~# shutdown -r +1 "test"
> Failed to connect to bus: No such file or directory
> root@archive-01:~#
>
> At this point, my SSH connexion froze and the machine stopped
> answering pings. I am not exactly sure what happens because I don't
> have a console on the server, but I suspect it just did a hard reboot,
> because normal shutdown procedures would have killed the sshd process
> and therefore closed the connexion (instead of just hanging).
>
> Therefore, not only the +1 minute delay is not respected, but the
> shutdown procedure is bypassed completely. The server eventually *did*
> reboot so it's not a full crash, but it's still pretty nasty.
>
> I would recommend a hard Depends on dbus for the systemd-sysv package
> (which provides the shutdown command) to resolve this problem.
>
> And I think this should be fixed in buster, sorry for the last minute
> bug report. :/ I really appreciate your work and systemd is generally
> working very well for me, so thank you for that! :)
What you see is expected.
Timed shutdowns/reboots require logind which in turn requires dbus.
The optional dependency on dbus is deliberate (the same way we no longer
have a hard dependency on udev).
We want to make it possible for users to uninstall dbus if they so
desire, which can be useful in certain restricted use cases.
A standard debian installation will have dbus.
If you decide to not use recommends or the standard task, then you are
more likely to be an experienced user.
It's a trade-off certainly, but I don't think timed shutdowns are such a
critical feature that it warrants making dbus a hard depenency atm.
Hope that clarifies.
I'm closing this bug report as what you see is expected behaviour and a
deliberate decision.
Regards,
Michael
--
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
--- End Message ---
