topic Re: system crash in Operating System - HP-UX

system crash

lawrenzo_1 — Thu, 03 Nov 2005 16:15:57 GMT

Hello,

We have just had a system crash and wanted to know a couple of things:

1> I have checked syslog and the below error displayed:

Nov 3 21:06:56 spbe895a vmunix: DIAGNOSTIC SYSTEM WARNING:
Nov 3 21:06:56 spbe895a vmunix: The diagnostic logging facility has started receiving excessive
Nov 3 21:06:56 spbe895a vmunix: errors from the I/O subsystem. I/O error entries will be lost
Nov 3 21:06:56 spbe895a vmunix: until the cause of the excessive I/O logging is corrected.
Nov 3 21:06:56 spbe895a vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Nov 3 21:06:56 spbe895a vmunix: in stm to start it.
Nov 3 21:06:56 spbe895a vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Nov 3 21:06:56 spbe895a vmunix: to determine which I/O subsystem is logging excessive errors.

What is the best way to determine the error through stm as the server has much I/O devices.

2> other than checking /var/tombstones and syslog and dmesg - where else i good to investigate for errors etc?

Thanks

Re: system crash

Raj D. — Thu, 03 Nov 2005 16:24:34 GMT

Hi Lawrenzo,

1.
You can find good information in /var/adm/crash/crash.0 if its first crash, or crash.1 or so.

log a call to HP , they will give a script collection.sh and crashinfo (binary executable file).

Copy the crashinfo in /var/adm/crash/ and run collection.sh and send the tar.gz file to HP. They will say quickly the reason for the crash.

2. Also check /var/opt/resmon/log/event.log file for any error log.

3. Check /etc/shutdownlog

Hope this will help.

Cheers,
Raj.

Re: system crash

lawrenzo_1 — Thu, 03 Nov 2005 16:37:16 GMT

great stuff - just what I was looking for

Thanks