Bug 798684
Summary: | Random delay on Fedora shut-down | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Saurav Sengupta <sauravsengupta17> | ||||
Component: | systemd | Assignee: | systemd-maint | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 16 | CC: | dennis, johannbg, metherid, mschmidt, notting, plautrba, systemd-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-03-02 11:56:47 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Saurav Sengupta
2012-02-29 15:09:52 UTC
The delay also often occurs after a YUM operation, such as installing or updating packages. What does the command "systemctl list-jobs" print immediately after logging in? Nothing. 0 jobs listed. I have also confirmed that the delay sometimes occurs even a long time after login. However, I am unable to find any particular usage pattern that causes it. Save this script as /lib/systemd/system-shutdown/debug.sh: #!/bin/sh mount / -o rw,remount dmesg > /dmesg.txt mount / -o ro,remount Make it executable (chmod +x /lib/systemd/system-shutdown/debug.sh). Then boot with the following kernel command line parameters: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 Reproduce the delay on shutdown. After booting back, attach the resulting /dmesg.txt file here. Thanks. OK, I'll do this and report back. If I can get a delay after a short session, well and good, otherwise I don't know when I'll be able to get a delay, because of the random nature of the problem. Created attachment 567038 [details]
dmesg debug output for delayed shut-down
I have attached the dmesg output from a delayed shut-down. I have also kept a copy of the output from a normal shut-down. I can provide that too, and/or a diff, if you want. NetworkManager did not quit after SIGTERM and was killed by SIGKILL after a timeout of 90 s. *** This bug has been marked as a duplicate of bug 739836 *** |