Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#5694 - INIT: No Processes left in this runlevel

Attached to Project: Arch Linux
Opened by Christ Schlacta (aarcane) - Saturday, 28 October 2006, 06:46 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I get the error:
INIT No processes left in this runlevel
on shutdown. no identifiable cause. google returns lots of hits for glibc, so I uninstalled glibc 2.5-1 from testing and reinstalled 2.4-4. it still does this. I suspect the problem may be in the kernel26mm , but I can't say for sure and I can't find any evidence anywhere else to back up my suspicion.

I've called this critical since it makes it impossible to safely shutdown a system.
This task depends upon

Closed by  Thomas Bächler (brain0)
Monday, 30 October 2006, 14:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in -rc3-mm1
Comment by Jens Adam (byte) - Saturday, 28 October 2006, 11:11 GMT
Confirmed here with -mm as well.
Comment by Christ Schlacta (aarcane) - Sunday, 29 October 2006, 21:50 GMT
I've managed to temporary solve the problem and allow a decent (though less than ideal) shutdown by doing the following:

in the file /etc/rc.shutdown comment the following lines:

# Terminate all processes
stat_busy "Sending SIGTERM To Processes"
/sbin/killall5 -15 &> /dev/null
/bin/sleep 5
stat_done

stat_busy "Sending SIGKILL To Processes"
/sbin/killall5 -9 &> /dev/null
/bin/sleep 1
stat_done

it has since stopped happening. I believe that this is caused by some call in killall5 returning the wrong information resulting in killall killing everything instead of ignoring the processes it's supposed to.

the problem with this method is that if anything is writing to disk when you shut down, it will not allow you to mount -o remount,ro /, which is nesecary to complete the shutdown with a clean filesystem.
Comment by Christ Schlacta (aarcane) - Monday, 30 October 2006, 04:15 GMT
I felt it nesecary to remind all that the above fix is ONLY SHORT TERM, and after the next kernel update you should UNDO ALL CHANGES to see if it has reverted to proper behavior.

Loading...