Using the Event Monitoring Service (June 2003)

Troubleshooting
Logging and Tracing
Appendix B 89
The persistence file names are normally having the format m.<number>,
where <number> is created by using a hash algorithm on the EMS
monitor start-up string stored in its dictionary file in
/etc/opt/resmon/dictionary. If the invocation command changes (e.g.
by adding command line options), the persistence file name also changes.
Structure of the Persistence File
The first 8 bytes give the length of monitor request: 0000014a, always
followed by entries of the form "IIII,LLLL,DDDD;" where
• I represents the ID of the field.
• L represents the length of the data field.
• D represents the data.
Example:
2019,4,1002;
2019: ID is RMObjectType
4: Length is 4 byte
1002: Data is RM_MONITOR_REQUEST_OBJECT
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 themonitor cannot access a resource are
also logged there.