HPE 9000 and HPE e3000 Servers
1753798 Members
7314 Online
108805 Solutions
New Discussion юеВ

LPMC Cache Parity Errors

 
Andrew Merritt_2
Honored Contributor

Re: LPMC Cache Parity Errors

Hi Ralph,
You'll need to check the /var/opt/resmon/log/event.log file for lpmc_em events. This is because the events which report individual cache errors are at the Informational level, and are not logged to syslog. (E.g. event 100601; see http://www.docs.hp.com/hpux/onlinedocs/diag/ems/lpmc_em.htm for the full list of events).

Andrew
Ralph Grothe
Honored Contributor

Re: LPMC Cache Parity Errors

Hi Andrew,

revisiting resmon config I noticed a malconfiguration in that no TEXTLOG was set for events to log to.
I realized because the /var/opt/resmon/log/event.log had an older mtime than the TL events that got logged to syslog.log.
Thus I reconfigured resmon for all monitors to log events >= INFO to event.log and made sure that indeed things get logged by issueing an lpmc_em test log entry through the utility /etc/opt/resmon/lbin/send_test_event
(huh, this path for resmon tools is pretty concealed)
Madness, thy name is system administration
Andrew Merritt_2
Honored Contributor

Re: LPMC Cache Parity Errors

That's odd, the default config should have events going to event.log.

What does /etc/opt/resmon/lbin/moncheck show?

Ralph Grothe
Honored Contributor

Re: LPMC Cache Parity Errors

moncheck shows the same as the interactive monconfig with [s],
anyway too much to be posted here.
But when I reconfigured resmon to include TEXTLOG on INFORMATION events I assured that from now on this will actually happen.
Besides, the stuff >= MAJORWARNING went to syslogd alreayd before.
Madness, thy name is system administration