Dec 26 15:36:33 bristlebane systemd[1]: systemd-reboot.service: Service lacks both ExecStart= and ExecStop= setting. Refusing. Dec 26 15:36:33 bristlebane systemd-logind[4551]: System is rebooting. Dec 26 15:36:33 bristlebane systemd[1]: systemd-reboot.service: Service lacks both ExecStart= and ExecStop= setting. Refusing. Dec 26 15:36:33 bristlebane systemd-logind[4551]: Error during inhibitor-delayed operation (already returned success to client): Unit systemd-reboot.service has a bad unit file setting. Similar messages for shutdown.
After `systemctl daemon-reexec` it works for me (systemctl poweroff).
The first reboot, initially only logged off worked after i kexec rebooted
(In reply to josef.95 from comment #1) > After `systemctl daemon-reexec` > it works for me (systemctl poweroff). Unless I missed it (and it's not saved to any of my logs) would be nice to get a warning about this.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ed1c7de237ae5d2aff784d9c7fcd4df7fb43a6d6 commit ed1c7de237ae5d2aff784d9c7fcd4df7fb43a6d6 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2018-12-27 06:35:41 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2018-12-27 06:35:41 +0000 sys-apps/systemd: reexec in pkg_postinst Closes: https://bugs.gentoo.org/673778 Package-Manager: Portage-2.3.52_p18, Repoman-2.3.12_p30 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-apps/systemd/systemd-240.ebuild | 6 ++++++ sys-apps/systemd/systemd-9999.ebuild | 6 ++++++ 2 files changed, 12 insertions(+)
I still have the same issue. Is it already fixed in the standard portage tree?
The solution is to run systemctl daemon-reexec after upgrading system. The current ebuild does this automatically.
(In reply to Mike Gilbert from comment #6) > The solution is to run systemctl daemon-reexec after upgrading system. The > current ebuild does this automatically. Thanks
