Bill Davidsen wrote:
After I booted my FC11 test system and did an update, I tried to shutdown and got this failure. I clicked system->shutdown->shutdown_button and the system hung. An investigation of the log shows that attached behavior.
If I log out and click the shutdown button it works, so it seems to only happen when using the button while logged in.
Running 'shutdown -h' as root also works.
[snip]
Apr 29 09:46:39 fc11s1 init: tty4 main process (1443) killed by TERM signal Apr 29 09:46:39 fc11s1 init: tty5 main process (1444) killed by TERM signal Apr 29 09:46:39 fc11s1 init: tty2 main process (1454) killed by TERM signal Apr 29 09:46:39 fc11s1 init: tty3 main process (1467) killed by TERM signal Apr 29 09:46:39 fc11s1 init: tty6 main process (1468) killed by TERM signal Apr 29 09:46:39 fc11s1 init: rc0 main process (5306) killed by TERM signal Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
[snip]
I chased ConsoleKit, gnome-session, and a few others when I saw this bug on my systems. I didn't get anywhere. It's a challenging bug to chase, because it doesn't always happen. Although I think it may be more reproducible when going from runlevel 5 to runlevel 3, maybe because if something's broken, it gets killed anyway in runlevel 0 or runlevel 6 when shutdown or reboot actually shuts down or reboots.
Anyway, I've seen people ask about this bug on this list (with various subject lines, but always essentially the same thing). I've seen other people file bugs and get them marked as duplicate. I've seen people add themselves as CCs on existing bugs. Even if I'm really stupid, I'd think at least some of the people interested in this bug are pretty bright. The fact that nobody seems to have a handle on exactly what's going on is kind of scary.
For me, the power button and ACPI still team up to provide a graceful shutdown, but that seems a bit inelegant.
--- On Thu, 4/30/09, Allen Kistler an037-ooai8@yahoo.com wrote:
From: Allen Kistler an037-ooai8@yahoo.com Subject: Re: Can't stop log To: fedora-test-list@redhat.com Date: Thursday, April 30, 2009, 11:38 AM Bill Davidsen wrote:
After I booted my FC11 test system and did an update,
I tried to shutdown and got this failure. I clicked system->shutdown->shutdown_button and the system hung. An investigation of the log shows that attached behavior.
If I log out and click the shutdown button it works,
so it seems to only happen when using the button while logged in.
Running 'shutdown -h' as root also works.
[snip]
Apr 29 09:46:39 fc11s1 init: tty4 main process (1443)
killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty5 main process (1444)
killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty2 main process (1454)
killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty3 main process (1467)
killed by TERM signal
Apr 29 09:46:39 fc11s1 init: tty6 main process (1468)
killed by TERM signal
Apr 29 09:46:39 fc11s1 init: rc0 main process (5306)
killed by TERM signal
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING:
Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
[snip]
I chased ConsoleKit, gnome-session, and a few others when I saw this bug on my systems. I didn't get anywhere. It's a challenging bug to chase, because it doesn't always happen. Although I think it may be more reproducible when going from runlevel 5 to runlevel 3, maybe because if something's broken, it gets killed anyway in runlevel 0 or runlevel 6 when shutdown or reboot actually shuts down or reboots.
Anyway, I've seen people ask about this bug on this list (with various subject lines, but always essentially the same thing). I've seen other people file bugs and get them marked as duplicate. I've seen people add themselves as CCs on existing bugs. Even if I'm really stupid, I'd think at least some of the people interested in this bug are pretty bright. The fact that nobody seems to have a handle on exactly what's going on is kind of scary.
For me, the power button and ACPI still team up to provide a graceful shutdown, but that seems a bit inelegant.
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
If you take another look at the attachment sent by Bill, the cultprit seems to be selinux not allowing shutdown. However, the updates might have fixed it? Don't know why but I have seen several of my rawhide machines doing this, but I did not bother to check what was going on and just pressed power button so that they could shutdown all the way.
I know my bad, but I see it only on two of the five machines and others do shutdown properly so it seems to me that not all users out there are experiencing the same trouble(s).
Regards,
Antonio
On Thu, Apr 30, 2009 at 01:38:30PM -0500, Allen Kistler wrote:
Bill Davidsen wrote:
After I booted my FC11 test system and did an update, I tried to shutdown and got this failure. I clicked system->shutdown->shutdown_button and the system hung. An investigation of the log shows that attached behavior.
Ah, I just filed https://bugzilla.redhat.com/show_bug.cgi?id=498514 and posted a message asking if I am the only one seeing that. It appears the same issue.
Apr 29 09:46:39 fc11s1 gnome-session[1652]: WARNING: Unable to stop system: Not privileged for action: org.freedesktop.consolekit.system.stop no
But I never seen that with selinux off. It still gets stuck apparently in hald-addon-input waiting for something.
I chased ConsoleKit, gnome-session, and a few others when I saw this bug on my systems. I didn't get anywhere. It's a challenging bug to chase, because it doesn't always happen.
How frequently it seem to depend on a kernel. 2.6.29.1-111.fc11 looks to be a pretty good at it.
Michal
-
Allen Kistler -
Antonio Olivares -
Michal Jaegermann