Operating System - HP-UX
1833777 Members
2064 Online
110063 Solutions
New Discussion

no active monitor request for the resource /system/events/memory/8

 
shuh
Occasional Contributor

no active monitor request for the resource /system/events/memory/8

In /var/adm/syslog/OLDsyslog.log, following messages displays repeatedly, and then, server is rebooting

===============>
Mar 5 08:21:42 tcs115 EMS [1848]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource:
"/system/events/memory/8" (Threshold: >= " 3") Execute the following command to obtain event details:
/opt/resmon/bin/resdata -R 121110530 -r /system/events/memory/8 -n 121110551 -a

=========================
In executing "/opt/resmon/bin/resdata -R 121110530 -r /system/events/memory/8 -n 121110551 -a" , following message is displayed
There is no active monitor request for the resource /system/events/memory/8
associated with the request id 121110530.


i want to khow why this messages happen
and solution about the problem. help me
2 REPLIES 2
Florian Heigl (new acc)
Honored Contributor

Re: no active monitor request for the resource /system/events/memory/8

The EMS notifications can only be queried until the next reboot -
I'm no hardware guru, but it appears You have a faulty memory module.

I'd ask You to go two tests, both in the mstm program.
First, run an execersize test against the memory module in question, second review the 'run->logtool' logs. this are the hardware logs of Your system, if EMS noticed a hardware problem, there should be a message related to that.

If You're unsure about the program, open a HP hardware call, I think You'll need one anyway to replace the module and to be able to use the (probably) locked and faulty memory pages again.
yesterday I stood at the edge. Today I'm one step ahead.
Andrew Merritt_2
Honored Contributor

Re: no active monitor request for the resource /system/events/memory/8

You should look in the file /var/opt/resmon/log/event.log, as there should be an event logged there. That should give you the full details of the problem.

As Florian says, the reference in the syslog file is only valid until a reboot (or in fact until the relevant monitor is restarted).

Andrew