what does the syslog.log mean?

[thebeatlesguru]

i found a lot of logs in syslog.log :Mar 10 09:24:23 dm-px vmunix: DIAGNOSTIC SYSTEM WARNING:
Mar 10 09:24:23 dm-px vmunix: in stm to start it.
Mar 10 09:24:23 dm-px vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Mar 10 09:24:23 dm-px vmunix: to determine which I/O subsystem is logging excessive errors.
Mar 10 09:24:25 dm-px vmunix: DIAGNOSTIC SYSTEM WARNING:
Mar 10 09:24:25 dm-px vmunix: The diagnostic logging facility is no longer receiving excessive
Mar 10 09:24:25 dm-px vmunix: errors from the I/O subsystem. 1 I/O error entries were lost.
Mar 10 09:24:28 dm-px vmunix: The diagnostic logging facility has started receiving excessive
Mar 10 09:24:28 dm-px vmunix: errors from the I/O subsystem. I/O error entries will be lost
Mar 10 09:24:28 dm-px vmunix: until the cause of the excessive I/O logging is corrected.
Mar 10 09:24:28 dm-px vmunix: DIAGNOSTIC SYSTEM WARNING:
Mar 10 09:24:28 dm-px vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Mar 10 09:24:28 dm-px vmunix: in stm to start it.
Mar 10 09:24:28 dm-px vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Mar 10 09:24:28 dm-px vmunix: to determine which I/O subsystem is logging excessive errors.
Mar 10 09:24:30 dm-px vmunix: DIAGNOSTIC SYSTEM WARNING:
Mar 10 09:24:30 dm-px vmunix: The diagnostic logging facility is no longer receiving excessive
Mar 10 09:24:30 dm-px vmunix: errors from the I/O subsystem. 1 I/O error entries were lost.
Mar 10 09:24:35 dm-px vmunix: The diagnostic logging facility has started receiving excessive
Mar 10 09:24:35 dm-px vmunix: errors from the I/O subsystem. I/O error entries will be lost
Mar 10 09:24:35 dm-px vmunix: until the cause of the excessive I/O logging is corrected.
Mar 10 09:24:35 dm-px vmunix: If the diaglogd daemon is not active, use the Daemon Startup command

the same thing repeat again and agin, but i dont know what does these things mean

[Michael Tully]

Hi,

These messages are generated from the system diagnotic daemon (diagmond). The message about excessive I/O's could be a few things. SCSI problems, problems with the diagnostic software itself or the start of some other hardware problem.
Suggest you restart the daemon and monitor it's output. Also load the latest diagnostic tools from either your latest patch bundle CD or from here:
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B6191AAE

Restart the diagnostic daemon
# /sbin/init.d/diagnostic start

HTH
Michael

[Michael Steele_2 · Accepted solution]

"...DIAGNOSTIC SYSTEM WARNING..."

More than likely you've got a HW I/O error and the diagnostic system is overloaded.

"...vmunix: errors from the I/O subsystem. 1 I/O error entries were lost..."

Any vmunix error message is not good.

"...if the diaglogd daemon is not active, use the Daemon Startup command..."

ps -ef | grep -i diaglogd
if not found then:
/sbin/init.d/diagnostic start

Something's probably failing. Sometimes this happens intermittently with tape drive units during backups so check the media and the drive. Also use LOGTOOL:

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > Raw Summary

Note the first and last dates and calculate the time difference, 5 days 3 hours for example.

Now note the integer numbers in parenthesis appearing next to hardware addresses as you scroll down the report. Look for anything in the hundreds. Here is an example:

Last date - First date = 4 hours and (454) 1/2/0/0/2.5 appears.

Cross reference the HW address in STM or ioscan to determine the product and product number and model and call HP. Open up a HW call with this information.

Also make a visual inspection checking for faults lights and review the other logs like /var/adm/messages (* dmesg *)and /etc/opt/resmon/log/api.log and the GSP log. Here is how you check for the GSP log:

control b
return, return
GSP>sl
(* Use a filter and check the error log *)

[thebeatlesguru]

hi, i have tried to restart the diagnostic ,but there is something wrong :

#/sbin/init.d/diagnostic start

/usr/sbin/stm/uut/bin/sys/diagmond failed during
execution.




what should i do ?

[S.K. Chan]

Can you check if "diaglogd" and "memlogd" is running. What I'm afraid is "diagmond" died and left behind these 2 processes. If that's the case you would need to kill both "diaglogd" and "memlogd" and then restart diagnostics with ..
#/sbin/init.d/diagnostic start
If the abovr does not apply and you still cannot startup diagnostic then there may be something wrong with your STM installation.

[Steven E. Protter]

Back up your data, take this system out of production if possible and consult HP hardware even if you pay time and materials.

You could have a bad disk.
You could have a bad scsi controller.
You could have a bad terminator on a scsi device.
You could have a bad cable
You could have a bad drive cage(if applicable).

If your OS and data is not mirrored you could be in big trouble.

try the command dmesg which, and you should get the same thing.

SEP

[thebeatlesguru]

i found one of harddisk is unavailable ,but it is one of mirror disk, i will replace it ,thanks for everyone