The csmonitor utility is a script that performs these monitoring functions:
Checks LDAP connectivity according to specific ics.conf parameters.
Checks the transaction log files, and if more than one file exists, csmonitor sends a warning by email.
Checks the available disk space for the calendar database.
Checks if Calendar Server services are running.
csmonitor [ -k | -c | -help] |
The following table describes the commands for the csmonitor utility.
Table D–22 csmonitor Utility Command Options
Parameter |
Description |
---|---|
-k |
Stops csmonitor. |
-c |
Backs up the csmonitor log and purges it. |
-help |
Displays the csmonitor usage. |
The following table csmonitor.
Table D–23 csmonitor Configuration Parameters
Parameter |
Description |
---|---|
service.monitor.continuous |
Specifies whether csmonitor should loop continuously: "0" – Do not loop continuously. "1" – Loop continuously. Default is "0". |
service.monitor.loopsdelay |
Specifies the delay in seconds between two monitoring loops. Default is "60". |
service.monitor.emailaddress.from |
Specifies the email address csmonitor sends messages from. Default is none. |
service.monitor.emailaddress.to |
Specifies the email address csmonitor should send messages to. Default is none. |
service.monitor.csdb.logthreshold |
Specifies a threshold value in percent of the total disk space for the maximum disk occupation considered to be normal. If, on the disk where the calendar database (csdb directory) resides, occupation exceeds this value, csmonitor sends a warning email message. Default is "90". |
logfile.monitor.logname |
Specifies the csmonitor log file name. Default is "csmonitor.log". |
logfile.monitor.maxlogfilesize |
Specifies the maximum log file size. If the log file exceeds this size, csmonitor saves the log as csmonitor.log.timestamp and resets the log. Default is "2097152". |
service.monitor.dbglevel |
Specifies the debug level. The higher this value, csmonitor sends more precise and verbose messages. Default is "0". |