System Administration

vmunix: DIAGNOSTIC SYSTEM WARNING:

 
SOLVED
Go to solution
dictum9
Super Advisor

vmunix: DIAGNOSTIC SYSTEM WARNING:


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.

10 REPLIES 10
R.O.
Esteemed Contributor
Solution

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

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,
"When you look into an abyss, the abyss also looks into you"
dictum9
Super Advisor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

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

Torsten.
Acclaimed Contributor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

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

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
dictum9
Super Advisor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

Nothing in mailbox but the same errors in dmesg.

dictum9
Super Advisor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

I cannot zoom in to the disks via stm.
Torsten.
Acclaimed Contributor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

>> # 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.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
stephen peng
Valued Contributor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

i recall that function on logtool could disable this mass logs
singh sanjeev
Trusted Contributor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

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

there you could find anything...
Sanjeev Singh
Steven E. Protter
Exalted Contributor

Re: vmunix: DIAGNOSTIC SYSTEM WARNING:

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
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com