Sun Java System Calendar Server 6 2005Q4 Administration Guide

Turning on Debugging Information

While there is no one ics.conf parameter that puts the whole system in “debug mode”, this section describes some ways to get useful debug information:

Note –

Be sure to turn off excess logging and monitoring when not needed as it will negatively impact performance.

Increase Logging Level

Use the parameter shown in the following table to increase the verbosity of logging:

Parameter	Description and Default Value
`logfile.loglevel`	Set to `DEBUG` to get all levels logged, including `CRITICAL`, `ALERT`, `ERROR`, `WARNING`, `NOTICE`, and `INFORMATION`. This applies to all logs.

For more information about the different logs available, see Using Calendar Server Log Files.

Enable Logging Access to the LDAP Cache

To log all accesses of the LDAP data cache and print out the log (report) set the ics.conf parameters shown in the following table:

Parameter	Description and Default Value
`local.ldap.cache.stat.enable`	Specifies whether or not to log the access to the LDAP data cache and to print statistics in the log file. The default is `“no”` (no statistics logged). Set to `“yes”` to enable logging of statistics. For performance enhancement, use this only in debug mode.
`local.ldap.cache.stat.interval`	Specifies the interval in seconds when each statistics report is written to the log file. The default is `“1800”` seconds (30 minutes). This is only active if logging is enabled. Decreasing the interval can help you pinpoint problems. Increasing the interval helps decrease system load.

Parameter

Description and Default Value

local.ldap.cache.stat.enable

Specifies whether or not to log the access to the LDAP data cache and to print statistics in the log file. The default is “no” (no statistics logged). Set to “yes” to enable logging of statistics.

For performance enhancement, use this only in debug mode.

local.ldap.cache.stat.interval

Specifies the interval in seconds when each statistics report is written to the log file. The default is “1800” seconds (30 minutes).

This is only active if logging is enabled. Decreasing the interval can help you pinpoint problems. Increasing the interval helps decrease system load.

Clearing the LDAP Cache

There is currently no logic in Calendar Server to expire LDAP cache data. You must manually remove the contents of the ldap_cache directory and restart Calendar Server.

To Clear the LDAP Cache

Stop Calendar Server.

Remove all files in the /var/opt/SUNWics5/csdb/ldap_cache directory, but do not remove the ldap_cache directory itself.

Restart Calendar Server.

Monitor the System Using Calendar Server Utilities

Use the following Calendar Server utilities to monitor your system:

csmonitor – Specify the debug level you need. The higher the number, the more verbose the messages.
csstats – Use the list command to display statistical information from counter objects defined in the counter.conf file.
cstool – Use this utility to ping the following services: cshttpd, csadmind, and enpd.

For more information on the Calendar Server utilities, see Appendix D, Calendar Server Command-Line Utilities Reference.