Shutdown doesn't work

[GerGon]

Hi gurus..

I have a rp5450 with HPux v.11.0
Since one week ago, the server doesn't shutdown. I don't remember has done something.

I was trying with -hy 0 and -ry 0, but nothing happend.... but the process still alive with "ps" command.

If I have one telnet session opened, it put the same message for shutdown, EXCEPT by, one of those say: "System maintenance about to begin.", while that when the server was working well doesn't put it.

When a do a "reboot", yes it down the server.
I just review the rc.log and all seems well!!

I'm looking for some threads but I can't find some like this.

I send a attach, maybe with it, you can help me, please check it out...

Thanks...

[Jeff Schussele · Accepted solution]

Hi,

Sounds like a stop script is hanging
If you go to the console you should see the last stop script that ran successfully & probably the one that's hanging.
These scripts are in /sbin/rc3[2][1].d and start with "K".
You can get the system to skip this script by entering ctrl-backslash. This will force it to move to the next script.
Then you need to determine the hang cause & fix it.

HTH,
Jeff

[James R. Ferguson]

Hi:

A 'shutdown' invokes the 'sbin/rc?.d' kill scripts to gracefully stop applications. A 'reboot' is really the last (brutal) step of 'shutdown'.

It appears that you have an Oracle database which is waiting for a natural quiet point.

My quess is that the 'shutdown' statement in the 'dbshut' script you call to shutdown the Oracle database simply says "shutdown". You can change that to "shutdown immediate". I think that will solve your problem.

Regards!

...JRF...

[Helen French]

I would think it's hanging or waiting when it tries to stop a process/application. What you have to do is check your /etc/rc.log.old file and check the bottom part, where it logs the system shutdown messages.

Find out which process was waiting for a long time to shutdown or failed. Also, to troubleshoot, after you invoke shutdown command from console, when the server *freeze* up, enter "Ctrl + \" to stop and skip that particular process. Now see which one was failed and what caused the problem.

[Steven E. Protter]

I think one of your shutdown scripts has failed or hung.

You can manually shut down the applications if you wish.

I'd recommend shutting down all databases and making sure they come down clean.

Then you can use the reboot command to suddenly and swiftly bring your machine down.

Also, init 1 from the console might help but probably there will still be a hang.

You will want to look at the shutdown log and see if there are clues there.

SEP

[doug mielke]

My guess is the last message on the console will be something like:
unmounting filesystems,

A cold reboot may get you out of this, but not help with the underlying cause.

run this as a background task before running shutdown

while :
do
ps -ef >> outfile
sleep 5
done


don't put the outfile in /tmp, in case that get's cleaned as part of your scripting.

This will give a list of process running, and you'll see what isn't being killed and hanging the shutdown

[doug mielke]

and it looks like the listener is still runninng, and the stop command started after the shutdown command.

Is Oracle being brought down as part of the shutdown rc scripts?

If so, if you run manually, you may see the error. Also, if you shutdown immediate and that works, try to start up again, then shutdown normally.

also, a
sync
before trying init 1 or killall might save later greif, although this may just be part of Unix lore.

[GerGon]

Yes, the problem was in the db dow script, I don't know why before it work fine and now I got the problem.
But, for the moment, I disabled the option.

Thanks to all, very nice answers and response time.
Thanks a lot..