Red Hat Bugzilla – Bug 41330
Whenever I shutdown (using shutdown -n now, halt, or reboot), system flushes ipcahins and says INIT: no more processes on this runlevel.
Last modified: 2007-04-18 12:33:19 EDT
Description of Problem:
I am filing this bug on behalf of acustomer who called. He will post to
this bug report ASAP.
What happened was he performed a Custom Installation (I think--Can you
verify this Steven?)--installing everything. The install appeare dto end
normally and he rebooted.
After that whenever he tried to shutdown or reboot, no matter how, he got
the following error after the ipchains were flushed:
INIT: no more processes on this runlevel
He would then turn off the system, which was partially halted.
Every reboot this was happening
Steps to Reproduce:
1. Log in to GNOME/KDE
2. Choose shutdown or reboot, or log in as root and enter halt. shutdown -h
3. INIT: no more processes on this runlevel
had to manually power down system, causing an fsck on reboot....
Wanted computer to power off...
I investigated his rc.d directory and everything looked okay.
BUT, rc0.d and rc6.d DID NOT contain the sym-links to killall and halt. or
I had the customer create these sym-links and he was then able to
successfully shutdown with shutdown -r now... It DID NOT, however, reboot.
It powered off his system instead.
I had him reboot (he boots into runlevel 5) and checked the rc5.d. The
sym-link to rc.local was missing. I had him create this sym-link.
Again, he will post shortly...
p.s. I told him not to reinstall just yet until a developer gives the go
It appears the installer did not properly finish its post install routines.
He has an new Athalon-based system...
This sounds like very strange behavior. I would tell him to reinstall, doing
the exact same process and see if the same thing happens again.
Closing due to inactivity. Please reopen if you have more information.
Please reopen this bug.
I have the same problem on 7.1, it hangs at the same point.
P-III system with SCSI.
Older versions of RH worked fine.
How can I trace where things go wrong ? /var/log/messages is useless here...
(Oh yes, I'm not going to reinstall, this is not supposed to be like MS)
I was able to fix it.
It was due to some incompatability between the 6.2 and 7.1 layout of the initscripts.
rc6.d should contain links to killall and reboot; it didnt