Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1684803 - machine will not shutdown without pulling plug
Summary: machine will not shutdown without pulling plug
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-02 16:32 UTC by Ray Holme
Modified: 2019-03-17 12:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Ray Holme 2019-03-02 16:32:50 UTC
Description of problem: machine will not shut down normally


Version-Release number of selected component (if applicable): systemd-239-12.git8bca462.fc29.x86_64


How reproducible: 100%


Steps to Reproduce:
1. menu -> shutdown or reboot
2.
3.

Actual results: machine hangs with the fedora "f" in blue for over 5 minutes
  - have to pull plug to shut it down


Expected results: machine will not fully reboot or shutdown without manual power pull


Additional info: I have two machines, mine works fine. About 2 months ago, my second machine (wife's) failed to reboot when I install a new OS (weekly normally). It boots fine, but trying to reboot or shut-it-down just hangs for over several minutes. It stops showing the black screen with the blue F for Fedora in the middle and hangs and hanges ... . This is not a big issue as I can pull the plug here, but this used to work fine. It has continued through at least 4 weekly cycles of OS update and reboot. Perhaps this is a hardware issue, but no other problems occur. Not sure what to send to give more information.

Comment 1 Michal Sekletar 2019-03-04 07:45:23 UTC
You should press Esc key during shutdown to disable graphical plymouth screen and then you should be able to see the job on which systemd got stuck during shutdown. Alternatively you can boot without graphical plymouth by removing "rhgb" parameter from the kernel command line of the Fedora boot entry in the grub menu.

Comment 2 Ray Holme 2019-03-04 12:24:22 UTC
Will try ESC first and report. Thanks.

Comment 3 Ray Holme 2019-03-04 23:13:08 UTC
rebooted multiple times this morning with ESC logging. Of course, the watched pot never boiled.

The 1st time, it hung for a while with the firewall daemon but then it completed after about 30 seconds.
The next two times, it shut down as it should - quickly - but I had just booted and then shutdown
  so nothing normal happened.

I will be running more like normal for a couple days - just sleeping in between sessions - the I will try again.

I suspect heavily that web sites may somehow effect things over a few days, but that sounds crazy to my knowledge of the OS.

Comment 4 Ray Holme 2019-03-05 22:48:51 UTC
OK, two days later and the machine did it again, and I caught it.

Symptoms before I knew it would happen is that "just going to sleep" (SUSPEND) takes almost 30 seconds to get the yellow light of slumber.

So I shutdown the machine and watched (escaped). Don't quote me exactly as I had to write it down.
"A stop job is running for the user manager....for UID 1001"
 a timeout clock is shown (runs about 3 minutes) after which it finally shutsdown in a few seconds properly.

User 1001 is my wife. She just uses Evolution mail and the Firefox browser.
I have no idea what is going on so if you have something for me to try before giving up on this one, please let me know.
I have noticed in the past that her machine has sporadic times when it is slower than a snail 
  - when I run top, it looks like web content and Firefox are using most of the 2 actual cpus.

I do NOT show many videos on my box, so perhaps it is related to unstopped web content.
I could try closing firefox next time I think this is likely, but am otherwise clueless as to what to do.

If there is nothing to glean from this and I can get no more ideas to find out what is going on, you can close it out.

Comment 5 Ray Holme 2019-03-17 12:21:14 UTC
So it would appear that systemd is trying to shutdown Firefox which is busy getting net goop (active sub-pictures in websites)
  as some websites never seem to stop pulling more.

Firefox does not shut down quickly and systemd times it out.

I think this is a bug for Firefox not systemd.

The question is what to report - is systemd sending a HUP signal or what?

Feel free to close this as a systemd bug, but please tell what mechanism systemd is using to tell Firefox so I can report it there.


Note You need to log in before you can comment on or make changes to this bug.