Created attachment 875918 [details] Picture of typical screen contents at hang. Description of problem: On my Dell Optiplex 755 desktop, running "systemctl reboot --force" always seems to hang forever. Whatever is going on here seems to be unique to this one system and fedora 20 (fedora 19 installed in a different boot partition on the same machine doesn't have this problem). The last thing printed on the screen when it stops talking always seems to be acpid: exiting I'll attach a picture of the screen and stopwatch app showing it was sitting like this for six minutes :-). Version-Release number of selected component (if applicable): systemd-208-15.fc20.x86_64 How reproducible: Every time I run systemctl reboot --force the same hang happens. Steps to Reproduce: 1. see above 2. 3. Actual results: Hangs forever, requires power cycle to reboot. Expected results: Reboots without waiting for nonsense like systemd user stop jobs which also takes forever and was why I tried --force. Additional info:
http://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1
Created attachment 910767 [details] New screenshot without quiet option in kernel All the suggested debug techniques were useless. A serial console would be very difficult to arrange. The debug shell is apparently dead by the time the shutdown hangs. The shutdown-log.txt file is never created because it hangs before that. What I was able to do was boot without the "quiet" option on the kernel, then see if any additional information showed up on the screen, and it did! It looks very much like systemd has killed the network connection before unmounting the NFS filesystems (I'm using network, not NetworkManager if that matters). All the systems it mentions timing out on are in fact up and working fine. If I waited perhaps two hours, it might actually get through all the NFS timeouts and finish rebooting, but that seems completely contrary to the idea of the --force option :-).
I am not sure about your setup, but if you have root on nfs, than you probably need this patch for network https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=b71c9724
Nope. No root on NFS, just a slew of mounts of other machines around the lab I sometimes need things from. I had actually hoped that --force would utterly ignore network filesystems. I don't even have them automounted in fstab in the hopes that systemd would never find out about them, but it seems to go to fantastic amounts of trouble to discover when things get mounted and seize control of them so it can shut them down "cleanly", even though the odds are high that one or more of them will have gone down and shutdown will then hang even without the --force option.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
A bunch of fixes for device handling went into F22. It would be great if you could test it in F22 or rawhide. I'm afraid that chances of significant changes in this area in anything earlier are slim.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.