Logging and tracing

EMS Logging

As mentioned in the previous section, log files in /etc/opt/resmon/log / contain information logged by the monitors.

Look at the client.log if you seem to be having a problem with the SAM interfaces to EMS or MC/ServiceGuard. With the default level of logging, only audit and error messages are logged. An example of an audit message is:

User event occurred at Thu Jul 31 16:13:31 1997 Process ID: 10404 (client) Log Level:Audit + /vg/vg00/lv/copies/* (8 instances) If (<1), OpC (m/n), 18000s, Thu Jul 31 16:13:31 1997

The "+" means that request has been added. A "-" indicates a removal. A "-" followed by a "+" indicates a modification. Events sent to targets are marked with ".". Errors are marked with Log Level: Error or Warning.

Look at the api.log if you seem to be having a problem with a specific monitor. Check for warnings or errors.

Logging to /var/adm/syslog/syslog.log is enabled with the -l option by default for the disk monitor only. Although it is not recommended, you can turn off logging modify the diskmond.dict file in /etc/opt/resmon/dictionary and remove -l from the monitor:

MONITOR: /etc/opt/resmon/lbin/diskmond

Logging to /var/adm/syslog/syslog.log is disabled by default for the other monitors. To enable logging, modify the mibmond.dict file in /etc/opt/resmon/dictionary and add -l from the monitor:

MONITOR: /etc/opt/resmon/lbin/diskmond -l

	NOTE: Logging will occur at every polling interval. This can create a very large syslog file, so you may only want to use logging when you are troubleshooting.

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