Using High Availability Monitors (June 2007)

Troubleshooting HA Monitors

Debug Logging of EMS HA Monitors

Appendix B 91

Debug Logging of EMS HA Monitors

The debug logging of the EMS HA Monitors (mibmond, lanmond, fsmond,

pkgmond, svcmond, clustermond, diskmond, rdbmsmond) can be enabled

by modifying the monitor’s dictionary file, by adding the options "-d -l" to

the monitor invocation string and restarting it. See also the manual

pages for the monitors.

As an example, enable the debug logging for the mibmond:

# cd /etc/opt/resmon/dictionary

# grep mibmond *

mibmond.dict:MONITOR: /etc/opt/resmon/lbin/mibmond

The mibmond start-up string is defined in the mibmond.dict file. Modify

all the lines in the dictionary file that start with MONITOR and contain

mibmond information.

MONITOR: /etc/opt/resmon/lbin/mibmond -d -l

Now kill the mibmond. It will be restarted automatically if needed. After

mibmond is automatically restarted, it will log debug data to

/var/opt/resmon/log/mibmond.log. The mibmond.log file grows

without bound.

NOTE Do not save the backup copy of a dictionary file in the

/etc/opt/resmon/dictionary directory or in any other subdirectory. If

you want to make a backup copy of a dictionary file , save it to /tmp (or

similar).

To obtain full debug logging from the EMS API library functions, you

should enable the EMS debugging by creating /etc/opt/resmon/debug

and restarting the monitor.

To force the monitor to restart, the easiest method is to kill the monitor

first, followed by issuing resls(1m) on a monitor resource. E.g. "resls

/system/numUsers" will start the mibmond.