Sun Java System Calendar Server 6 2005Q4 Administration Guide

Monitoring Calendar Server

You will want to monitor system activity as part of your daily tasks. There are several utility tools available to you for monitoring Calendar Server activity: csmonitor, csstats, cstool. In addition, you can set up many log files to help monitor system usage.

This section covers the following topics:

About csmonitor

This Calendar Server utility is a shell script that requires bash. When invoked, this utility performs the following functions:

For debugging purposes, you can configure the monitor to run in a continuous loop with very short intervals, but this requires more system resources, so you don’t want to keep it in that mode during normal production.

To use csmonitor under normal circumstances, set it to run with an interval that you choose.

For more information about the csmonitor utility, see Appendix D, Calendar Server Command-Line Utilities Reference.

ProcedureTo Configure csmonitor

  1. Log in as an administrator with permission to change the configuration.

  2. Change to the /etc/opt/SUNWics5/cal/config directory.

  3. Save your old ics.conf file by copying and renaming it.

  4. Edit one or more of the ics.conf parameters shown in the following table:


    Description and Default Value  


    Specifies whether csmonitor should loop continuously:"0" – Do not loop continuously (the default)."1" – Loop continuously.

    Set this parameter to “1” to enable csmonitor to run automatically.


    Specifies the delay in seconds between two monitoring loops. The default is “60” seconds. 

    For debugging purposes, make the interval shorter and for production, make the interval much longer. 


    Specifies the email address csmonitor sends messages from. No default given.

    Specifies the email address csmonitor should send messages to. No default given.


    Monitors the calendar database (csdb). Specifies a threshold value, as a percent of the total disk space, for maximum disk occupation. If the disk occupation for the csdb directory exceeds this value, it sends a warning email message. The default is “90”.


    Specifies the csmonitor log file name. The default is “csmonitor.log”.


    Specifies the maximum log file size. If the log file exceeds this size, csmonitor saves the log as csmonitor.log.timestamp and resets the current log. The default is “2097152”


    Specifies the debug level. With a range of 0-5, the higher this value, the more precise and verbose messages sent by csmonitor. The default is “0”, which specifies no logging. A value of “5” would indicate debug logging.

  5. Save the file as ics.conf.

  6. Restart Calendar Server.


Listing Counter Statistics

The csstats utility displays statistical information from counter objects defined in the calendar configuration (counter.conf) files. Counter objects such as httpstat, authstat, wcapstat, or dbstat show information about Calendar Server including:

For information about Calendar Server counter statistics, see Appendix E, Calendar Server Configuration Parameters.

Using cstool for Monitoring

You can ping the following services as well as the machine where Calendar Server is installed:

For information about using cstool, see Appendix D, Calendar Server Command-Line Utilities Reference.

Using Calendar Server Log Files

Each Calendar Server service writes status information to its own log file. Each log file is named after its associated service name, as shown in the following table:

Service Name 

Log File Name 

Administration Service (csadmind) 


Distributed Database Service (csdwpd) 


HTTP Service (cshttpd) 


Notification Service (csnotifyd) 


Single Sign-on log 


Log of start commands 


Log of stop commands 


Log of store commands 


Calendar Server log files are stored in the following default directory:


Each log file is rolled-over to a new log file identified by a unique number. For example:

admin.log.8.1083013284 http.log.8.1083013284

Calendar Server provides six levels of severity for events reported to the log files as described in the following table. You can specify the level of severity of the events that Calendar Server reports to the log files by modifying the ics.conf parameter logfile.loglevel.

Severity Level 



Critical condition. 


Error condition. 


Warning condition. 


Normal, but signification condition. This is the default reporting level for each calendar service. 




Debug-level message. 

A log event is represented by a single line that shows the associated timestamp, server host name, severity level, process name (process ID), type of event, priority, and description.

For information regarding the ics.conf log settings, see Appendix E, Calendar Server Configuration Parameters.