topic vmunix: DIAGNOSTIC SYSTEM WARNING: in Operating System - HP-UX

vmunix: DIAGNOSTIC SYSTEM WARNING:

dictum9 — Tue, 18 May 2010 13:23:01 GMT

This is 11.23 on 4640, getting these in syslog, any idea what this means?
ioscan doesn't show any bad disks.

May 16 01:57:37 vmunix: DIAGNOSTIC SYSTEM WARNING:
May 16 01:57:37 vmunix: The diagnostic logging facility is no longer receiving excessive
May 16 01:57:37 vmunix: errors from the I/O subsystem. 2 I/O error entries were lost.
May 16 01:57:38 vmunix: The diagnostic logging facility has started receiving excessive
May 16 01:57:38 vmunix: errors from the I/O subsystem. I/O error entries will be lost
May 16 01:57:38 vmunix: until the cause of the excessive I/O logging is corrected.
May 16 01:57:38 vmunix: DIAGNOSTIC SYSTEM WARNING:
May 16 01:57:38 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
May 16 01:57:38 vmunix: in stm to start it.
May 16 01:57:38 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
May 16 01:57:38 vmunix: to determine which I/O subsystem is logging excessive errors.
May 16 02:02:57 vmunix: DIAGNOSTIC SYSTEM WARNING:
May 16 02:02:57 vmunix: The diagnostic logging facility is no longer receiving excessive
May 16 02:02:57 vmunix: errors from the I/O subsystem. 2 I/O error entries were lost.
May 16 02:02:57 vmunix: The diagnostic logging facility has started receiving excessive
May 16 02:02:57 vmunix: errors from the I/O subsystem. I/O error entries will be lost
May 16 02:02:57 vmunix: until the cause of the excessive I/O logging is corrected.
May 16 02:02:57 vmunix: DIAGNOSTIC SYSTEM WARNING:
May 16 02:02:57 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
May 16 02:02:57 vmunix: in stm to start it.
May 16 02:02:57 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
May 16 02:02:57 vmunix: to determine which I/O subsystem is logging excessive errors.
May 16 02:04:25 vmunix: DIAGNOSTIC SYSTEM WARNING:
May 16 02:04:25 vmunix: The diagnostic logging facility is no longer receiving excessive
May 16 02:04:25 vmunix: errors from the I/O subsystem. 2 I/O error entries were lost.
May 16 02:04:25 vmunix: The diagnostic logging facility has started receiving excessive
May 16 02:04:25 vmunix: errors from the I/O subsystem. I/O error entries will be lost
May 16 02:04:25 vmunix: until the cause of the excessive I/O logging is corrected.
May 16 02:04:25 vmunix: DIAGNOSTIC SYSTEM WARNING:
May 16 02:04:25 vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
May 16 02:04:25 vmunix: in stm to start it.
May 16 02:04:25 vmunix: If the diaglogd daemon is active, use the logtool utility in stm
May 16 02:04:25 vmunix: to determine which I/O subsystem is logging excessive errors.

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

R.O. — Tue, 18 May 2010 13:34:15 GMT

Hi,

Try to do this:

"If the diaglogd daemon is active, use the logtool utility in stm to determine which I/O subsystem is logging excessive errors"

# stm>tools>utility>run>logtool

Regards,

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

dictum9 — Tue, 18 May 2010 13:41:17 GMT

stm / tools / utility / activity log or Failure log do not reveal any further logs.

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

Torsten. — Tue, 18 May 2010 13:45:48 GMT

You should also see related mails in root's mailbox.

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

dictum9 — Tue, 18 May 2010 14:17:48 GMT

Nothing in mailbox but the same errors in dmesg.

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

dictum9 — Tue, 18 May 2010 14:18:10 GMT

I cannot zoom in to the disks via stm.

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

Torsten. — Tue, 18 May 2010 14:22:00 GMT

>> # stm>tools>utility>run>logtool

stm / tools / utility / activity log or Failure log do not reveal any further logs.

This is NOT the same! Run the logtool.

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

stephen peng — Tue, 18 May 2010 15:06:04 GMT

i recall that function on logtool could disable this mass logs

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

singh sanjeev — Tue, 18 May 2010 17:32:18 GMT

check eventlog ,for any hardware related issue:
/var/opt/resmon/log/event.log

there you could find anything...

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

Steven E. Protter — Tue, 18 May 2010 19:23:56 GMT

Shalom,

I disagree with disabling logging.

Somewhere on the I/O subsystem there is either an unterminated SCSI connection or some kind of problem that has gone undiagnosed.

You should use mstm, cstm or xstm to diagnose the problem and then correct it.

SEP

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

knight_runner — Fri, 16 Jul 2010 09:25:11 GMT

I get the same errors "The diagnostic logging facility has started receiving excessive errors..." in all my servers when I start the diagnostics.

I suppose that I can't have problems on all my servers so I'm thinking that the reason of that message could be previous logged errors?

What do you think?

Thanks & regards