Bug 619927

Summary: systemd destroys ability to shutdown/restart a machine
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: lpoetter, metherid, mschmidt
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-01 13:57:36 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:

Description Michal Jaegermann 2010-07-30 21:55:43 UTC 
Description of problem:

After a boot with systemd my machine does not stop anymore after "halt" or "shutdown -h now" and does not reboot after "reboot" or "shutdown -r now". A text messages from such actions, observed on a system console, end up like that:
.....
Starting Kill All Processes...
Not stopping monitoring, this is dangerous operation.  Please use force-stop to override.

After that a system is dead with a power swith as the only possible operation; "dangerous" or not.

On other occasions before "Not stopping monitoring ..." the following line may appear:

Stopping System Initialization

but an overall outcome is the same.

Rebooting with "init=/sbin/upstart" restores an ability to shutdown.  This hits bug 618678 (power off on reboot) but at least it does not hang.

Version-Release number of selected component (if applicable):
systemd-4-4.fc14

How reproducible:
always

Additional info:
"Not stopping monitoring, this is dangerous operation." should really read
"Not stopping monitoring. This is a dangerous operation." regardless of a wisdom of such action.
Comment 1 Michal Schmidt 2010-08-01 07:56:08 UTC 
Duplicate of bug 605519?
Comment 2 Michal Jaegermann 2010-08-01 13:57:36 UTC 
(In reply to comment #1)
> Duplicate of bug 605519?    

Yes, indeed it is.

*** This bug has been marked as a duplicate of bug 605519 ***