topic Re: shutdown and reboot on redhat es4 in Operating System - Linux

shutdown and reboot on redhat es4

Tammy Liang — Fri, 08 Sep 2006 09:59:07 GMT

I can not shut down redhat es4 via both
"shutdown -r now" and "reboot" run as root.
I see the "The system is going down for reboot NOW!", but nothing happen. It does not stop any process.

Thanks for any reply...

Tammy

Re: shutdown and reboot on redhat es4

Vipulinux — Fri, 08 Sep 2006 10:24:56 GMT

Hi Tammy

What kind of hardware do you use and what applications are u using. How much time do you wait after the command.

when u issue the command to reboot the system it will stop all the running applications...so possibly the OS is not able to kill a particular process.

Try diagnosing which process is hanfing.

Also try using init 6 and see the events that occur after this in /var/log/messeges

Cheers
Vipul

Re: shutdown and reboot on redhat es4

Steven E. Protter — Fri, 08 Sep 2006 11:55:43 GMT

Shalom Tammy,

Something is preventing the system from shutting down.

Common cause is trying the command from inside an NFS share or remote drive that needds to be umounted.

See /var/log/messages for more data and details.

SEP

Re: shutdown and reboot on redhat es4

Tammy Liang — Fri, 08 Sep 2006 12:20:33 GMT

It is HP Proliant DL380. I did reboot few weeks ago w/o issue.

I stoped all applications and still have problem to shutdown the system.

[root@test1]# shutdown -r now
Broadcast message from root (pts/0) (Fri Sep 8 13:20:26 2006):
The system is going down for reboot NOW!
[root@test1]#

I checked /var/log/messages file and see
shutting down for system reboot. But the system still not comes down.

Sep 8 13:20:26 test1 shutdown: shutting down for system reboot
Sep 8 13:22:22 akroragc su(pam_unix)[22801]: session closed for user oracle
Sep 8 13:22:25 akroragc su(pam_unix)[28457]: session opened for user root by a342675(uid=0)
[root@test1 log]#

Any idea?

Re: shutdown and reboot on redhat es4

IT_2007 — Fri, 08 Sep 2006 13:08:01 GMT

do you have any nfs mount on this server? shutdown command goes gracefully. check /var/log/messages.

Logon with another session and check what process is holding it?

Re: shutdown and reboot on redhat es4

Tammy Liang — Fri, 08 Sep 2006 13:21:23 GMT

No, there is no nfs mount. The session is not close after I run shutdown command.
Can not see any abnormal messages in /var/log/messages file. I even stop all applications before I run shutdown/reboot command.

Re: shutdown and reboot on redhat es4

Lakshmi Narayanan — Tue, 19 Sep 2006 10:32:03 GMT

Dear Tammy,
if you want to shutdown your pc then it should be like this:
shutdown -h now
OR
init 0
OR
poweroff
OR
halt
OR
in GNOME or in KDE desktop, click Actions button and in task bar and select Logout and select Shutdown

If you want to reboot the system again after shutting down all your modules then if should be like this:
init 6
OR
shutdown -r
OR
reboot
OR
in GNOME or in KDE desktop, click Action button in task bar and select Logout and select Restart your computer

try with this, hope you may solve your problem.
Bye,
Have a nice day

Re: shutdown and reboot on redhat es4

Matthew Holdsworth — Tue, 24 Jul 2007 09:53:48 GMT

Hi there,

We had a slightly similar problem today with our DL380 running RH 3.4.4-2.

I initiated a 'shutdown -r -y -g0'. I used the -y and -g0 because it's habit from using Solaris but it didnt complain so thought it would work.

Anyways, it seemed to be shutting down nicely and my window to the system died off as expected. 20 minutes later I still could not connect to the server. Went into the computer room to find it sitting there in what looked like a standby state. The power button was amber.
Pressed the power button and it booted back up nicely.

Does anyone know why it would not have rebooted backup automatically?

Regards

Matt

Re: shutdown and reboot on redhat es4

skt_skt — Tue, 24 Jul 2007 14:43:20 GMT

i use "shutdown -ry 0".

I had pahsed a problem like the server did not go down after this command. I saw the brodcast came. Only the next day i could realise that the server was not rebotted.

The reason was shutdown was trying to stop OpC and it could not.I had a problem with OpC and as soon i bounced the OpC the server went through the real reboot phase