Shutdown via SSH - Suppress Daemon Messages?

[Justin Mercier]

Hi, I have exhausted Google and these forums for an answer, hopefully someone out there knows the answer.

I am trying to remotely shutdown three Integrity servers running HP-UX 11i via SSH. I have a RHEL server that subscribes to my building's UPS for power or environmental issues, at which point the server then sends shutdown commands via SSH.

Unfortunately, the problem is that my HP-UX systems are hanging the shutdown script by keeping the connection open with the daemon shutdown messages (i.e. "Stop NFS server subsytem...", etc).

How can I suppress this behavior? I have looked in HP-UX sshd's config, I've tried backgrounding scripts, I even commented out the 'link' entry in inittab.

I think this capability it actually pretty cool but in my case it is creating a monster problem in that the servers are not shutting down when HVAC or AC becomes an issue. Thanks in advance!

Justin Mercier

[Steven E. Protter]

Shalom Justin,

You don't supress this behavior, you solve the problem thats causing it.

Normally when you shut down a system, nfs.server, then nfs.client then nfs.core shut down in that order.

I believe the third is failing.

Normally these errors are caused by network configuration and the systems should have trouble starting as well.

You might find its easier to diagnose problems by conncting directly to the LAN console if available of these systems. You should check the syslog.log file on the systems for clues as to what the actual problem is.

It is perfectly acceptable however to shut down systems with ssh. I do it all the time. At some point in the process, output is redirected to the console, which is why I'm recommending you use it. You may find that the process is continuing merrily along its way and the last screen message that made it to ssh is the nfs message.

If you state the model number of the system available I or more likely others will get back to you and give recommendations.

Console setup is part of the documents for all servers on http://docs.hp.com

SEP

[Justin Mercier]

Thanks for your help.

I don't have a LAN console... all of my systems connect to a rackmount KVM console. This is where I normally would expect the system messages to display as the primary console. I am not trying to turn off init's system messages, I just do not want them going to the SSH session. But if I understand correctly, this is what would happen normally of there is a problem with a daemon's shutdown? I'm looking at rc.log and syslog.log now, but nothing stands out.

I am using the Integrity rx2600 system rather than the DL-380 that I am more comfortable with. I am more experienced with Sun, SGI, and Linux type systems that normally only behave this way if you set them up to use a serial or network console.

Your last suggestion highlights my lack of thorough knowledge with these systems. I'll refer to the documents that you suggest. There are certainly quite a few, and I am in Baghdad trying to not to get shot.

[Justin Mercier]

Okay, I read up on the console setup and I went into EFI and set the input, output, and error console to VGA exclusively. That was alreasy set but it also have a pseudo-terminal device setup for input and error. Maybe I just broke ILO. I also looked at the daemon messages and everything is starting and stopping, save a small complaint from FontServer about not having Japanese fonts installed. I'm not sweating that one.

So I went ahead and did an ssh shutdown test and once again I have all my daemon shutdown messages printing again. All of them are OK or N/A. I have to admit, I really do not like this feature since I can't seem to turn it off.

Perhaps my answer is to uninstall HP-UX SSH and go with the OpenSSH I already know and love.

Cheers,

Justin