Got a ticket for diagnostic system warning on a HPUX box.
below is the complete error log
below is the complete error log
Aug 3 16:33:47 sapsrvr vmunix: DIAGNOSTIC SYSTEM WARNING:
Aug 3 16:33:47 sapsrvr vmunix: The diagnostic logging facility has started receiving excessive
Aug 3 16:33:47 sapsrvr vmunix: errors from the I/O subsystem. I/O error entries will be lost
Aug 3 16:33:47 sapsrvr vmunix: until the cause of the excessive I/O logging is corrected.
Aug 3 16:33:47 sapsrvr vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Aug 3 16:33:47 sapsrvr vmunix: in stm to start it.
Aug 3 16:33:47 sapsrvr vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Aug 3 16:33:47 sapsrvr vmunix: to determine which I/O subsystem is logging excessive errors.
started digging in and found that the diaglogd deamon is not running on the server.
But above error message doesnt suggest any thing that says the log is cause of diaglogd deamon not running.
so first step was to start the diaglogd and diagmond deamons.
/usr/sbin/stm/uut/bin/sys is the location where both the deamons executables are located and the diagmond deamon was renamed to diagmond.old which was restricting the start of diaglogd deamon.
so i renamed it back to original name and could be able to start the diagmond and diaglogd deamons and could be able to map devices from cstm.
so first step was to start the diaglogd and diagmond deamons.
/usr/sbin/stm/uut/bin/sys is the location where both the deamons executables are located and the diagmond deamon was renamed to diagmond.old which was restricting the start of diaglogd deamon.
so i renamed it back to original name and could be able to start the diagmond and diaglogd deamons and could be able to map devices from cstm.
No comments:
Post a Comment