error on syslog

[sharif naser_1]

Hello experts,

i have some an error 62 in syslog what does this error mean.

my syslog file attached.

any help is highly appreciated.

TIA

[Bill Hassell]

The only error message with 62 is this one:

Mar 12 00:29:43 erpprod vmunix: DIAGNOSTIC SYSTEM WARNING:
Mar 12 00:29:43 erpprod vmunix: The diagnostic logging facility is no longer receiving excessive
Mar 12 00:29:43 erpprod vmunix: errors from the I/O subsystem. 62 I/O error entries were lost.

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

This message means that 62 error events were lost because you are having massive errors. From the bootup messages, it appears that either the online diagnostics were not properly installed or there are errors being logged all the time. You'll need HP to help you get the error messages under control and help with running the stm utility. My guess is that there are big problems with your disk array. I'm not sure why there aren't disk errors logged, but this depends on the revision of HP-UX you are running.

[Sanjiv Sharma_1]

Hi Sharif,

Please check these links:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=77495
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=456217

hth.

[Jaffar]

HI Tia
U check the /var/opt/resmon/log/event.log file for all the errors Logged by STM.

It seems Some device throwing the IO error which is logged on the STM.

If u check the above file then u wil cameto knw where is the problem
AJ