Using EMS HA Monitors

Chapter 6 77
Troubleshooting
Logging and tracing
Entries in /var/adm/syslog/syslog.log are marked with the monitor
daemon name, e.g. diskmond or fsmond, followed by the resource name and logging
data. Additions, deletions, notifications, and changes in resource states are logged.
Errors explaining why a resource is not available for monitoring, or why the monitor
cannot access a resource are also logged in /var/adm/syslog/syslog.log.
Look at the registrar.log if you are having trouble finding resources that you
suspect exist on your system. This log contains any errors that were encountered
when trying to read the dictionary. If a dictionary was corrupted in any way, the
registrar would not be able to read it, and EMS would not be able to find the
resources associated with that dictionary.
EMS Tracing
Tracing is used when debugging monitor code.
Use the -d option to turn on tracing for EMS monitors. Tracing should only be used
at the request of your HP support personnel when trying to determine if there may
be a problem with the EMS HA monitors. To turn on tracing, modify the .dict
file in /etc/opt/resmon/dictionary and add -d to the monitor you would
like to trace:
MONITOR: /etc/opt/resmon/lbin/diskmond -l -d
Kill the monitor process. The monitor will automatically restart with tracing
enabled. To speed up monitor restart, use the resls command with the top level of
the resource class as an argument, for example, resls /vg.
Tracing is logged to /etc/opt/resmon/log/diskmond.log for the disk
monitor and /etc/opt/resmon/log/mibmond.log for all other monitors