1826123 Members
4487 Online
109690 Solutions
New Discussion

a problem about EMS

 
lin.chen
Frequent Advisor

a problem about EMS

IN syslog.log
> Oct 13 15:18:27 wznms EMS [1714]: ------ EMS Event Notification ------ Value:"SERIOUS
> (4)" for Resource: "/system/events/core_hw/core_hw" (Threshold: >= " 3") Execute
> the following command to obtain event details: /opt/resmon/bin/resdata -R 112328706 -r
> /system/events/core_hw/core_hw -n 112328915 -a

when I run the command as followings,
/opt/resmon/bin/resdata -R 112328706 -r /system/events/core_hw/core_hw -n 112328915 -a
but I can not retrieve any data.Actually,there is no output!

EMS-core A03.20
EMS-KRMonitor A11.00.03
EMS-Config A03.20

os:11.00

customer did no want to see information in event.log,so could you do me a favor,thanks!
9 REPLIES 9
Yang Qin_1
Honored Contributor

Re: a problem about EMS

If you can find /etc/opt/resmon/log/reslog.html on the server, then try to use a web browser to view the log.
rariasn
Honored Contributor

Re: a problem about EMS

Hi,

view logs files:

# cd /var/opt/resmon/log

# more event.log client.log

rgs,

ran
lin.chen
Frequent Advisor

Re: a problem about EMS

thanks!but customer want to know the root reason,because they can it normally in another system,which is the same version about OS and EMS.so could you give me some idea to resolve this issue.
rariasn
Honored Contributor

Re: a problem about EMS

Andrew Merritt_2
Honored Contributor

Re: a problem about EMS

Hi,
Not sure exactly what you're asking.

The 'resdata' command line given will only be valid for the lifetime of the monitor which reports it, so if dm_core_hw has been restarted since Oct 13, then the 'resdata' command will fail to show the event details.

The event.log file is where the full event details will be found; what does this show?

I don't understand what you mean by "customer did no want to see information in event.log". Can you explain?

You probably also need to update to the A.44.00 version of OnlineDiags, and apply the latest patch, which is currently PHSS_34834.

Andrew
lin.chen
Frequent Advisor

Re: a problem about EMS

yes,customer know how to read the monitor information in event.log.
But customer want to know why he issue the command logging in syslog has no output.
he said he can run it normally in another system.unfortunately,I can not find any difference between the two system.so customer need the root reason.
OldSchool
Honored Contributor

Re: a problem about EMS

examine the monitor configuration in both the "working" and "non-working" servers. See /etc/opt/resmon/lbin/monconfig
jerry1
Super Advisor

Re: a problem about EMS

The event log has probably been cleared
out depending on the model of the system.
Without more information. It's hard to
say what the reason is that it is not
displaying. I have had problems with EMS
and firmware that needs to be updated
according to hp relating to reporting
harware problems with EMS.

Andrew Merritt_2
Honored Contributor

Re: a problem about EMS

Lin Chen,
Have you checked to see if dm_core_hw was restarted since Oct 13? Also, is there actually an event in the event.log file at this time?

If it wasn't, and the customer is running an up-to-date version of OnlineDiags, I would recommend opening a support call with HP to investigate further

It would be useful to know if this is a persistent problem or has only happened once.

Andrew