What does these warning message mean?

[zhaogui]

Hi,
Can anybody tell me why I got these warning message when I run dmesg?

Thanks,

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

[Paula J Frazer-Campbell]

Hi

From your errors :-

If the diaglogd daemon is active, use the logtool utility in stm


Fire up stm and check out you systems.
Also have a look at /var/adm/syslog/syslog.log for information.


Paula

[Clemens van Everdingen]

Hi,

Can you show us the part of the syslog file where these messages occurr ?
I.E. during boot or backup or something like that.

C.

[S.K. Chan]

Check 2 things ..
# ps -ef|grep diagmon
==> if not running start it up by ..
# /sbin/init.d/diagnostic start

and

# cstm
cstm> ru logtool
Logtool utility>

..will bring you to STM logtool utility, look for any errors there.

[Steve Steel]

Hi


As already stated . It is clear.

Something is logging messages

that smells like a hardware failure of some sort.
As the message indicates you probably need to run stm to determine what is broken.
But because you need to get some parts replaced then anyways and need to pace a call to hp you might as well ask them to help you run the diagnostics.


Steve Steel

[Juan Manuel López]

I think that you have to stop and restart the diaglog. The message show you that the diaglog is not working properly because it log is full.
Also you can reboot the machine to repair this situation.
I hope this help you.
Juanma.

[melvyn burnard]

you have had a burst of hardware errors that were so numerous, in a short period of yoime, that the logger could not handle them all.
Investigate your hardware.

[zhaogui]

The time when all these messgage come out is when we were doing a testing on alternate link by intentionally disable one Broadcade switch. But I was wondering how come other nodes which also connects to this shared disk array VA7400 did not get these message.
By the way, how to check if the log is full and where is the log file?

[Phillip Renner]

Hi,
If you go to /var/opt/resmon/log/event.log you can see what is causing the diagnostic errors.