Using the Event Monitoring Service (June 2007)

Troubleshooting
Logging and Tracing
Appendix B 87
• Stop EMS clients.
• Kill all registrar processes.
• Kill p_client.
The p_client process will be restarted immediately. EMS monitor will
be started if the persistent requests are present. The non persistent
requests will be lost.
Using resls to Check EMS Communication
resls is a client application that can verify that the communication
between client, registrar and a monitor works. If you are dealing with a
problem that seems to be related to some sort of communication issue
between EMS processes, use resls to verify whether all monitors are
affected or only some.
For example:
If you type the following command at the HP-UX prompt,
1)
# resls /system/numUsers
the above command fails to check if any request is available for a
required resource. The resources managed by the mibmond can be listed
with resls /system command. You should also verify if another
resource of the same monitor fails, for example, mibmond.
Another mibmond resource:
2)
# resls /system/jobQueue1Min
A diskmond resource:
3)
# resls /vg/vg00/pv_summary
• If 2) fails but 3) succeeds, it is likely that the problem is with
mibmond or with the SNMP setup, where the mibmond monitor gets
its data.
• If 2) and 3) fail, it is likely that the problem is with EMS framework,
e.g. the communication of the resls(1m) client with the registrar fails.