Using the Event Monitoring Service (June 2003)

Troubleshooting
Logging and Tracing
Appendix B 85
Apart from 6 MB monitor disk space, you can reserve additional disk
space for EMS monitors logging. To relocate the directory, enter the
following commands:
mkdir /newpath/resmon
mv /etc/opt/resmon/log/newpath/resmon
# create /newpath/resmon/log
# remove /etc/opt/resmon/log
ln -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.
EMS Log Files
EMS log files are stored in the following locations:
• /etc/opt/resmon/log
• /var/opt/resmon/log
The following log files are stored in the /etc/opt/resmon/log path:
• api.log
This file contains logs of the processes that make use of the EMS API
to interact with EMS. All EMS Monitors such as EMS HA Monitors
(diskmond, mibmond etc.), EMS Hardware Monitors (disk_em,
ha_disk_array, dm_stape etc.), EMS Kernel Resource Monitor
(krmond) and the Peripheral Status Monitor (psmmon) log to this file.
Once the file reaches 500KB in size, it is automatically copied to
api.log.old and the previous api.log.old file is lost.
• client.log
This file contains the logs of all EMS Clients. There is a number of
possible client processes such as the Persistence Client (p_client),
the EMS GUI (invoked by SAM), the Peripheral Status Monitor
Client/Target daemon (psmctd), monconfig, resls and other.
Once the file reaches 500KB in size, it is automatically copied to
client.log.old and the previous client.log.old file is lost.
• registrar.log