Am 14.05.2018 um 01:23 schrieb Meeuwissen Olaf: > Hi, > > Michael Biebl writes: > >> Am 11.05.2018 um 08:10 schrieb Meeuwissen Olaf: >>> Hi, >>> >>> Thanks for the quick follow-up. >>> >>> Michael Biebl writes: >>> >>>> Control: tags -1 + moreinfo >>>> >>>>> I have set up unattended-upgrades to reboot my machine at 04:00 when >>>>> necessary. Internally, unattended-upgrades runs >>>>> >>>>> /sbin/shutdown -r 04:00 >>>>> >>>>> trying to achieve this. This fails as evidenced by these (dated) log >>>>> messages >>>>> >>>>> Apr 25 06:55:18 easy apt.systemd.daily[38369]: Found >>>>> /var/run/reboot-required, rebooting >>>>> Apr 25 06:55:18 easy apt.systemd.daily[38369]: Failed to connect to >>>>> bus: No such file or directory >>>> >>>> What's the output of >>>> systemctl status dbus.socket dbus.service systemd-logind.service >>> >>> $ sudo systemctl status dbus.socket dbus.service systemd-logind.service >>> Unit dbus.socket could not be found. >>> Unit dbus.service could not be found. >>> * systemd-logind.service - Login Service >>> Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; >>> vendor preset: enabled) >>> Active: inactive (dead) >>> Condition: start condition failed at Fri 2018-05-11 04:00:25 JST; 10h ago >>> `- ConditionPathExists=/lib/systemd/system/dbus.service was >>> not met >>> Docs: man:systemd-logind.service(8) >>> man:logind.conf(5) >>> http://www.freedesktop.org/wiki/Software/systemd/logind >>> http://www.freedesktop.org/wiki/Software/systemd/multiseat >>> >>> Yes, I don't have dbus installed. Nothing I have installed has a >>> dependency on it that is Depends: or more important. I don't install >>> Recommends: and actively remove them unless other installed packages >>> declare a (Pre-)Depends: >>> >>> Based on my understanding of the relevant section[1] in the Debian >>> Policy, I would argue that systemd-sysv needs a Depends: dbus. >>> >>> [1]: >>> https://www.debian.org/doc/debian-policy/#binary-dependencies-depends-recommends-suggests-enhances-pre-depends >>> >>> The Recommends: that systemd declares looks fine as I have not observed >>> any other breakage. >>> >>> FTR, after I install dbus, I get >>> >>> $ sudo shutdown -r 04:00 >>> Shutdown scheduled for Sat 2018-05-12 04:00:00 JST, use 'shutdown -c' to >>> cancel. >>> >> >> Scheduled shutdowns require systemd-logind, which in turn requires >> dbus. > > In my initial bug report I included > > root@debian:~$ shutdown -r 04:00 > Failed to connect to bus: No such file or directory > root@debian:~$ shutdown -r > Failed to connect to bus: No such file or directory > root@debian:~$ shutdown > Failed to connect to bus: No such file or directory > > What is scheduled about the last two commands? The implicit "now"?
Please read the manual for shutdown carefully: "If no time argument is specified, +1 is implied." So yes, all the examples you gave are scheduled shutdowns. If you use shutdown -h now (no scheduled shutdown), it should work without dbus. You said that shutdown is completely broken for you, are you implying that -h now does not work for you? -- 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