Description of problem: Installed: systemd.x86_64 0:8-1.fc14 systemd-sysvinit.x86_64 0:8-1.fc14 systemd-units.x86_64 0:8-1.fc14 [root@vmrawhide64 ~]# shutdown -r now Failed to issue method call: Unit reboot.service failed to load. See logs for details. Failed to talk to init daemon. [root@vmrawhide64 ~]# tail /var/log/messages Aug 26 08:53:59 vmrawhide64 kernel: systemd[1]: Accepted connection on private bus. Aug 26 08:53:59 vmrawhide64 kernel: systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.StartUnit() on /org/freedesktop/systemd1 Aug 26 08:53:59 vmrawhide64 kernel: systemd[1]: Trying to enqueue job reboot.target/start Aug 26 08:53:59 vmrawhide64 kernel: systemd[1]: Added job reboot.target/start to transaction. Aug 26 08:53:59 vmrawhide64 kernel: systemd[1]: Got D-Bus request: org.freedesktop.DBus.Local.Disconnected() on /org/freedesktop/DBus/Local
Low priority? System shutdown & bootup is screwed with the systemd-8-1.fc14 update :-( The update doesn't update the symbolic link /etc/systemd/system/default.target. The file it was pointing to is no longer in /etc/systemd/system but in /lib//systemd/system. After fixing the symbolic link by hand the system seems to bootup and shutdown normally again.
Bugzilla's priority field is often ignored, I rarely set it. I seem to have and okay /etc/systemd/system, but still no reboot. [root@vmrawhide64 ~]# ls -l /etc/systemd/system total 16 lrwxrwxrwx. 1 root root 33 Aug 26 08:51 ctrl-alt-del.target -> /lib/systemd/system/reboot.target lrwxrwxrwx. 1 root root 37 Aug 9 16:13 default.target -> /lib/systemd/system/multi-user.target lrwxrwxrwx. 1 root root 34 Aug 26 08:51 display-manager.service -> /lib/systemd/system/prefdm.service drwxr-xr-x. 2 root root 4096 Aug 9 10:20 getty.target.wants drwxr-xr-x. 2 root root 4096 Aug 9 10:20 graphical.target.wants lrwxrwxrwx. 1 root root 33 Aug 26 08:51 kbrequest.target -> /lib/systemd/system/rescue.target drwxr-xr-x. 2 root root 4096 Aug 23 16:49 multi-user.target.wants drwxr-xr-x. 2 root root 4096 Jul 16 10:07 sockets.target.wants
(In reply to comment #0) > Failed to issue method call: Unit reboot.service failed to load. See logs for > details. This is because of the changes in the unit file language. The old daemon does not understand what "oneshot" means.
Another reason to re-exec the daemon on update? Can than be done now?
"telinit u" doesn't do anything. "kill 1" seemed to do the trick.
My /etc/systemd/system looks different: # ls -lt /etc/systemd/system total 24 lrwxrwxrwx. 1 root root 36 Aug 26 18:17 default.target -> /lib/systemd/system/runlevel5.target lrwxrwxrwx. 1 root root 33 Aug 26 17:06 kbrequest.target -> /lib/systemd/system/rescue.target lrwxrwxrwx. 1 root root 34 Aug 26 17:06 display-manager.service -> /lib/systemd/system/prefdm.service lrwxrwxrwx. 1 root root 33 Aug 26 17:06 ctrl-alt-del.target -> /lib/systemd/system/reboot.target drwxr-xr-x. 2 root root 4096 Aug 25 16:14 multi-user.target.wants drwxr-xr-x. 2 root root 4096 Aug 25 16:14 network.target.wants lrwxrwxrwx. 1 root root 42 Aug 25 16:14 dbus-org.freedesktop.NetworkManager.service -> /lib/systemd/system/NetworkManager.service drwxr-xr-x. 2 root root 4096 Aug 25 13:43 sockets.target.wants drwxr-xr-x. 2 root root 4096 Aug 25 13:43 shutdown.target.wants drwxr-xr-x. 2 root root 4096 Aug 25 13:43 graphical.target.wants drwxr-xr-x. 2 root root 4096 Aug 25 13:43 getty.target.wants I guess runlevel5.target should be graphical.target instead. I'm not sure if the NetworkManager symbolic link is still needed in the latest version?
Should we just add 'systemctl daemon-reexec' to %post of systemd?
It looks like /etc/systemd/system/shutdown.target.wants/plymouth-shutdown.service is a broken symlink on my computer (points to /lib/systemd/system/plymouth-shutdown.service), which seems bad.
(In reply to comment #8) > It looks like > /etc/systemd/system/shutdown.target.wants/plymouth-shutdown.service is a broken > symlink on my computer (points to > /lib/systemd/system/plymouth-shutdown.service), which seems bad. I guess that should point to /lib/systemd/system/plymouth-poweroff.service instead?
I don't have a /etc/systemd/system/shutdown.target.wants at all. I do have: # ls -l /lib/systemd/system/shutdown.target.wants/ lrwxrwxrwx. 1 root root 39 Aug 26 08:51 systemd-update-utmp-shutdown.service -> ../systemd-update-utmp-shutdown.service I'm getting the feeling that managing symbolic links with rpm is not easy.
Ah, I'm not in graphical boot though, perhaps that is the difference?
Confirmed to work on my system: - plymouth-shutdown.service -> /lib/systemd/system/plymouth-poweroff.service - dbus-org.freedesktop.NetworkManager.service symlink no longer needed I'm using graphical boot ("rhgb" kernel parameter [plymouth]) and default target is "graphical" (AKA runlevel 5).
Hmm, I guess I should reexec the daemon on upgrade, to avoid this problem.
(In reply to comment #9) > (In reply to comment #8) > > It looks like > > /etc/systemd/system/shutdown.target.wants/plymouth-shutdown.service is a broken > > symlink on my computer (points to > > /lib/systemd/system/plymouth-shutdown.service), which seems bad. > > I guess that should point to > > /lib/systemd/system/plymouth-poweroff.service > > instead? This seems to work fine, thanks!
If anyone needs additional data, I just applied a batch of updates then tried to use the "restart" button in gnome, that merely got me back to a KDM login screen where I tried to use the Menu entry for restart which was non-responsive, so I did a Ctrl-Alt-F2 to get a new console and typed reboot where merely spewed errors about some message that failed (or something like that). It said to see the logs for details, so here is what appears to be the tail end of my /var/log/messages file from where I started trying to reboot: Aug 26 20:27:02 zooty init[1]: Reloading. Aug 26 20:27:02 zooty kernel: init[1]: Reloading. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/shutdown.target:12] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/shutdown.target:12] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/systemd-update-utmp-shutdown.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty init[1]: Failed to load configuration for systemd-update-utmp-shutdown.service: Bad message Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/systemd-update-utmp-runlevel.service:16] Failed to parse service type: oneshot Aug 26 20:27:02 zooty init[1]: Failed to load configuration for systemd-update-utmp-runlevel.service: Bad message Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/systemd-update-utmp-shutdown.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for systemd-update-utmp-shutdown.service: Bad message Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/systemd-update-utmp-runlevel.service:16] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for systemd-update-utmp-runlevel.service: Bad message Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/plymouth-quit.service:14] Failed to parse service type: oneshot Aug 26 20:27:02 zooty init[1]: Failed to load configuration for plymouth-quit.service: Bad message Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/plymouth-quit.service:14] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for plymouth-quit.service: Bad message Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/rc-local.service:19] Unknown lvalue 'RemainAfterExit' in section 'Service'. Ignoring. Aug 26 20:27:02 zooty init[1]: Failed to load configuration for livesys-late.service: No such file or directory Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/rc-local.service:19] Unknown lvalue 'RemainAfterExit' in section 'Service'. Ignoring. Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for livesys-late.service: No such file or directory Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/sysinit.target:14] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/sysinit.target:14] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/sysinit.service:19] Unknown lvalue 'RemainAfterExit' in section 'Service'. Ignoring. Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/sysinit.service:19] Unknown lvalue 'RemainAfterExit' in section 'Service'. Ignoring. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/killall.service:12] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/killall.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty init[1]: Failed to load configuration for killall.service: Bad message Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/halt.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/killall.service:12] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/killall.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for killall.service: Bad message Aug 26 20:27:02 zooty init[1]: Failed to load configuration for halt.service: Bad message Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/umount.target:12] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/reboot.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty init[1]: Failed to load configuration for reboot.service: Bad message Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/poweroff.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty init[1]: Failed to load configuration for poweroff.service: Bad message Aug 26 20:27:02 zooty init[1]: Failed to load configuration for plymouth-shutdown.service: No such file or directory Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/halt.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for halt.service: Bad message Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/umount.target:12] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/reboot.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for reboot.service: Bad message Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/poweroff.service:15] Failed to parse service type: oneshot Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for poweroff.service: Bad message Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for plymouth-shutdown.service: No such file or directory Aug 26 20:27:02 zooty kernel: init[1]: [/lib/systemd/system/basic.target:14] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty init[1]: [/lib/systemd/system/basic.target:14] Unknown lvalue 'RefuseManualStart' in section 'Unit'. Ignoring. Aug 26 20:27:02 zooty init[1]: Failed to load configuration for distcache.service: No such file or directory Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for distcache.service: No such file or directory Aug 26 20:27:02 zooty init[1]: Failed to load configuration for hal.service: No such file or directory Aug 26 20:27:02 zooty init[1]: Failed to load configuration for xend.service: No such file or directory Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for hal.service: No such file or directory Aug 26 20:27:02 zooty kernel: init[1]: Failed to load configuration for xend.service: No such file or directory Aug 26 20:27:02 zooty init[1]: Unit rpcgssd.service entered maintenance state. Aug 26 20:27:02 zooty kernel: init[1]: Unit rpcgssd.service entered maintenance state. Aug 26 20:28:16 zooty systemd-initctl[2557]: Failed to start unit: Unit reboot.service failed to load. See logs for details. Aug 26 20:28:16 zooty kernel: gnome-panel[1799]: segfault at 7f0fb93f0500 ip 00007f0fb93f0500 sp 00007fff1c9f2c38 error 14 in SYSV00000000 (deleted)[7f0fb9840000+60000] Aug 26 20:28:17 zooty abrt[2561]: saved core dump of pid 1799 (/usr/bin/gnome-panel) to /var/spool/abrt/ccpp-1282868896-1799.new/coredump (26075136 bytes) Aug 26 20:28:17 zooty abrtd: Directory 'ccpp-1282868896-1799' creation detected Aug 26 20:28:17 zooty abrtd: New crash /var/spool/abrt/ccpp-1282868896-1799, processing Aug 26 20:28:17 zooty abrtd: Registered Action plugin 'RunApp' Aug 26 20:28:17 zooty abrtd: RunApp('/var/spool/abrt/ccpp-1282868896-1799','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .') Aug 26 20:28:33 zooty kdm: :0[2568]: Fatal X server IO error: Interrupted system call Aug 26 20:28:33 zooty systemd-initctl[2587]: Failed to start unit: Unit reboot.service failed to load. See logs for details. Aug 26 20:28:34 zooty gpm[985]: *** debug [daemon/old_main.c(158)]: selected 1 times Aug 26 20:28:34 zooty gpm[985]: *** debug [daemon/getmousedata.c(60)]: Error in protocol Aug 26 20:29:07 zooty init[1]: Activating special unit ctrl-alt-del.target Aug 26 20:29:07 zooty init[1]: Failed to enqueue ctrl-alt-del.target job: Unit reboot.service failed to load. See logs for details. Aug 26 20:29:07 zooty kernel: init[1]: Activating special unit ctrl-alt-del.target Aug 26 20:29:07 zooty kernel: init[1]: Failed to enqueue ctrl-alt-del.target job: Unit reboot.service failed to load. See logs for details. Aug 26 20:29:28 zooty systemd-initctl[2616]: Failed to start unit: Unit reboot.service failed to load. See logs for details. Aug 26 20:29:37 zooty systemd-initctl[2616]: Failed to start unit: Unit reboot.service failed to load. See logs for details. I also find this in kdm.log: Failed to issue method call: Unit reboot.service failed to load. See logs for details.
systemd-8-3.fc14,initscripts-9.17-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/systemd-8-3.fc14,initscripts-9.17-2.fc14
initscripts-9.17-2.fc14, systemd-8-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.