topic Re: Syslog messages in Operating System - HP-UX

Syslog messages

Ali Imran Abbas — Mon, 05 May 2008 19:47:23 GMT

I am getting the following error messages in syslog for some time, does any one has a clue about them?

May 5 14:34:28 HERA vmunix: DIAGNOSTIC SYSTEM WARNING:
May 5 14:34:28 HERA vmunix: The diagnostic logging facility is no longer rec
eiving excessive
May 5 14:34:28 HERA vmunix: errors from the I/O subsystem. 1 I/O error entr
ies were lost.
May 5 14:34:28 HERA vmunix: DIAGNOSTIC SYSTEM WARNING:
May 5 14:34:28 HERA vmunix: The diagnostic logging facility has started rece
iving excessive
May 5 14:34:28 HERA vmunix: errors from the I/O subsystem. I/O error entrie
s will be lost
May 5 14:34:28 HERA vmunix: until the cause of the excessive I/O logging is
corrected.
May 5 14:34:28 HERA vmunix: If the DEMLOG daemon is not active, use the DIAG
SYSTEM command
May 5 14:34:28 HERA vmunix: in SYSDIAG to start it.
May 5 14:34:28 HERA vmunix: If the DEMLOG daemon is active, use the LOGTOOL
utility in SYSDIAG
May 5 14:34:28 HERA vmunix: to determine which I/O subsystem is logging exce
ssive errors.

Can any one give me the clue, whats the real problem is and how to fix it?

Re: Syslog messages

Ramesh S — Tue, 06 May 2008 00:41:20 GMT

Hi

Seems that there is something wrong with system H/W. If the system is configured with EMS, you could check the EMC alerts.

Or use stm to verify which H/W creates those i/o error.

Best Regards,
Ramesh

Re: Syslog messages

whiteknight — Tue, 06 May 2008 01:20:32 GMT

Ali,

It seems your have hardware warning.

How to use LOGTOOL (an example)
---------------------------------

How to decode Hardware errors logged on a 9000/S800 HPUX system.
Supported HP-UX revs = HPUX 8.0, 8.02, 8.06, 9.0, 9.02, 9.04.

o Log onto system as root

o Type "sysdiag"

# sysdiag

o At the DUI prompt type "logtool"

DUI> logtool

o At the LOGTOOL prompt type "status detail"

LOGTOOL> status detail

This will list the number of error logs on the system. Including
time stamp of the 1st log entry and # of records in each log. For
example:

Log File Rec #1 Rec #1 Total
Name Date Time #Records
========== ============ ======== ========
LOG0000 01/31/94 12:08 PM 18
LOG0004 02/24/94 07:04 AM 1024
LOG0005 02/24/94 07:05 AM 1024
LOG0006* 02/24/94 07:06 AM 352

o From the time stamp, determine the log in which log you are
interested.

o Display the contents of the log and redirect the output to a
UNIX file using the following command:

LOGTOOL> list log=xxxx;outfile=

where xxxx is the integer of the log file name and is
a standard HPUX file name. You can drop the leading zeroes from
the integer number. The outfile file should be limited to 8
alpha/numeric characters only.

An example of displaying the contents of LOG0004 is as follows:

LOGTOOL> list log=4;outfile=Log4

In the above example, the contents of LOG0004 will be
redirected to a file called "Log4". It will be automatically
placed under the /usr/diag/bin directory.

o Now, to view this log, exit out of LOGTOOL and DUI and cd to
the /usr/diag/bin directory. Then use MORE or VI to view the file.

A sample of the system error log report follows:

SYSTEM ERROR LOG REPORT
=======================

===============================================================
WED, FEB 03, 1993 11:30 PM /usr/adm/diag/LOG0000
SYSTEM
(PIN 0
I/O ERROR
PRODUCT NAME: PDEV: 52.0.0
LDEV: DEVICE CLASS: 15
I/O EVENT CLASS: Hardware LLIO STATUS: $E31F0414
RETRY SCHEME: Log Each Retry WILL RETRY: NO
I/O RESULT: I/O Failed RUN AUTODIAG: NO
RETRY COUNT: 0 MGR PORT NUM.: $7
TRANS. NUM.: $2B70B812 # HDWR BYTES: 22
HARDWARE STATUS:

1 2 3 4 5 6 7 8 9 10 11 12
== == == == == == == == == == == ==
1: 00 00 00 02 70 00 02 00 00 00 00 0B
13: 00 00 00 00 3A 00 00 00 00 00

You may see that LOGTOOL has further decoded the HARDWARE STATUS

WK