Event Monitoring Service Version A.03.10 Release Notes

Chapter 1 15
Event Monitoring Service Version A.03.10 Release Notes
Known Problems and Workarounds
Known Problems and Workarounds
The following are known problems and suggested workarounds with the
EMS:
JAGab77628: ServiceGuard package package_status is
not being reported on nodes in a failed state
What is the problem? An EMS “error” event occurs when monitoring the
resource instance /cluster/package/package_status/
<package_name>. cmviewcl shows the local node STATE to be failed.
The api.log contains:
-------------------Start Event--------------------
User event occurred at <timestamp information>
Process ID: nnnn (/etc/opt/resmon/lbin/pkgmond) Log Level: Error
SNMPGet of /cluster/package/package_status/pkg1 fails: Invalid Target
Object Used
-------------------End Event----------------------
What is the workaround? If you get an error event, run the cmviewcl
command to check the status of packages. If ITO is installed, configure
an EMS trap template to intercept the error event, and then launch the
cmviewcl command as an automatic action.
JAGab77527: EMS client may fail to connect to the
registrar
What is the problem? An EMS client may fail to connect the EMS
registrar. If this occurs, you may see a message in
/etc/opt/resmon/log/client.log like this one:
-------------------Start Event--------------------
Event 11 occurred at Tue Oct 19 15:53:24.025936 1999
Process ID: 1062 (/etc/opt/resmon/lbin/startmon_client)
Log Level: Error
rm_client_connect: Failed to connect to hprdstts.rose.hp.com,
IP address 15.8.135.200, Port 1712: Invalid argument
-------------------End Event----------------------
-------------------Start Event--------------------
User event occurred at Tue Oct 19 15:53:24.036390 1999
Process ID: 1062 (/etc/opt/resmon/lbin/startmon_client)
Log Level: Error