Logging and Tracing

EMS Logging

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, or any other client, 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 plus (+) means that request has been added. A minus (-) indicates a removal. A minus (-) followed by a plus (+) indicates a modification. Events sent to targets are marked with period (.). Errors are marked with Log Level: Error or with Log Level: Warning.

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

Some monitors have their own logs, refer to the man page for individual monitors.

Log File Size

EMS log files are normally under /etc/opt/resmon/log. Although their size is limited, the EMS log files can grow to 13 MBytes. In addition, some monitors put their own log files in the EMS log directory. EMS does not control the size of monitor log files. If disk space is limited in the file system that contains /etc/opt/resmon/log, relocate the EMS log directory and make /etc/opt/resmon/log a symbolic link to the new location. To relocate the directory:

mkdir /newpath/resmon mv /etc/opt/resmon/log /newpath/resmon # create /newpath/resmon/log # remove /etc/opt/resmon/logln -s /newpath/resmon/log /etc/opt/resmon/log

	NOTE: EMS requires that /etc/opt/resmon, the parent directory, reside on the root file system. Do not move all of /etc/opt/resmon to another file system.

High Availability Monitors

High availability monitors provide additional logging support.

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

Entries in /var/adm/syslog/syslog.log are marked with the monitor daemon name, for example pkgmond 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 there.

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

Some monitors provide tracing which can be used for debugging monitor code.

Use the -d option to turn on tracing for EMS. Tracing should only be used at the request of your HP support personnel when trying to determine if there may be a problem with EMS. 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/mibmond -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 /system.

Tracing is customarily logged to /etc/opt/resmon/log/monitor_name.log. The monitor_name usually matches the name used for the monitor in the dictionary file. For example, the MIBmonitor uses mibmond.dict and mibmond.log.