Question:
Is it ok for me to turn off the diaglogd?
I've stopped both daemons diagmond and diaglogd since they are sending large amounts of info to the syslog.
I restarted both diagmond and diaglogd but when I restarted diaglogd the log messages continued.
Here are the messages in syslog.log:
Jul 29 05:34:10 vmunix: DIAGNOSTIC SYSTEM WARNING:
Jul 29 05:34:10 vmunix: If the diaglogd daemon is not active, use th
e Daemon Startup command
Jul 29 05:34:10 vmunix: in stm to start it.
Jul 29 05:34:10 vmunix: If the diaglogd daemon is active, use the lo
gtool utility in stm
Jul 29 05:34:10 vmunix: to determine which I/O subsystem is logging
excessive errors.
NOTE:
In an earlier email I said I'd report what caused this apparently the entire incident happened earlier in the month and was fixed then but the dialogd was left in a bad state:
Here is the report from July 7 when they set up the temporary array:
------------------------------------------
/var/opt/resmon/log/event.log
Notification Time: Sat Jul 7 14:34:29 2007
pkdh0085 sent Event Monitor notification information:
/adapters/events/TL_adapter/0_0_10_1_0 is >= 1.
Its current value is INFORMATION(1).
Event data from monitor:
Event Time..........: Sat Jul 7 14:34:29 2007
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 19
System..............: pkdh0085
Summary:
Adapter at hardware path 0/0/10/1/0 : Received an interrupt indicating
that a primitive was received
Description of Error:
lbolt value: 4228
The Fibre Channel Driver received an interrupt indicating
that a primitive was received
Frame Manager Status Register = 0xa002c4b0
Probable Cause / Recommended Action:
The Tachyon TL adapter received a primitive sequence.
No action needed. Informative message.
Additional Event Data:
System IP Address...: 10.206.148.28
Event Id............: 0x468fa47500000002
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x468fa14500000001
Additional System Data:
System Model Number.............: 9000/800/rp7420
OS Version......................: B.11.11
EMS Version.....................: A.04.20
STM Version.....................: A.49.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#19v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
Component Data:
Physical Device Path....: 0/0/10/1/0
Vendor Id...............: 0x0000103C
Serial Number(WWN)......: 50060B0000BD6A96
I/O Log Event Data:
Driver Status Code..................: 0x00000013
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000006 00001084 00000001 00000001 A002C4B0 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E 63
