Event Monitoring Service Version A.03.20.01 Release Notes for HP-UX 11i

14 Chapter1

Known Problems and Workarounds

registrar stream tcp nowait root \

/etc/opt/resmon/lbin/registrar \

/etc/opt/resmon/lbin/registrar

Be sure the following line is in the /etc/services ﬁle:

registrar 1712/tcp # resource monitor service

Then enter inetd -c to reconﬁgure inetd.

2. Retry running the client that failed.

JAGab77759: ServiceGuard package service status is

reported incorrectly

What is the problem? /cluster/package/service_status/

<package_name>/<service_name> may be incorrectly reported. When

monitoring the service status of a package running locally and the

ServiceGuard coordinator node is not the same node, service status may

be incorrectly reportedas UNKNOWN or DOWN when it is reallyUP. cmviewcl

shows the service is UP.

What is the workaround? Conﬁgure package and service status

monitoring on each node in the cluster. Then correlate the data reported

on each node. The coordinator node will report status of UNKNOWN for the

remote service. UNKNOWN state means that the service is up and running

somewhere in the cluster.

JAGad03512: Events could be lost when EMS and HA

Monitors are upgraded

What is the problem? When updating the Event Monitoring Services,

notiﬁcations for monitors with active persistent requests can be lost.

This can happen for up to two minutes from the update. This cannot

happen with a new install, only an update.

What is the workaround? Before updating, ﬁnd out which monitors are

active. Enter the ps -ef |grep resmon command. In the table below,

check any of the monitors listed in the output.

Now, update the software.

Immediately after the update, activate the monitor to re-register all of its

active persistent requests. Use the commands in the table below.