This document covers the following versions of Sun Java System Calendar Server on the SolarisTM Operating System, HP-UX, Linux, and Microsoft Windows platforms:
Sun Java System Calendar Server 6.3 (Communications Suite 5)
Sun Java System Calendar Server 6.2 2005Q4
Sun Java System Calendar Server 6.2 2005Q1
Sun Java System Calendar Server 6.1 2004Q2
Sun Java System Calendar Server 6.0 2003Q4
You can use this document in all types of environments, including test, pre-production, and production. Verbose debugging is not used (to reduce performance impact), except when it is deemed necessary. At the same time, it is possible that the problem could disappear when you configure logging for debug mode. However, this is the minimum to understand the problem. In the majority of cases, the debug data described in this document is sufficient to analyze the problem.
This document does not provide workarounds nor techniques or tools to analyze debug data. It provides some troubleshooting, but you should not use this guide as an approach to troubleshooting Calendar Server problems.
If your problem does not conveniently fit into any of the specific categories, supply the general information described in 1.5 What Calendar Server Debug Data Should You Collect? and clearly explain your problem.
If the information you initially provide is not sufficient to find the root cause of the problem, Sun will ask for more details, as needed.
The prerequisites for collecting debug data for Calendar Server are as follows:
Make sure you have superuser privileges.
For the Solaris OS platform, obtain the dbhang, pkg_app, and cscapture scripts from the following location:
For information about running the pkg_app script, see To Run the pkg_app Script.
For information about running the cscapture script, see Using Calendar Server Capture (cscapture) to Collect Debug Data for Sun Java System Calendar Server.
On the Windows platform, download the free Debugging Tools for Windows to help in analyzing process hang problems. The debugger Dr. Watson is not useful for process hang problems because it cannot generate a crash dump on a running process. Download the free Debugging Tools from the following location:
Install the last version of Debugging Tools and the OS Symbols for your version of Windows. Also, you must add the environment variable NT_SYMBOL_PATH.
Use the command drwtsn32 -i to select Dr. Watson as the default debugger. Use the command drwtsn32, check all options, and choose the path for crash dumps.
The following describes the variables used in the procedures in this document. Gather the values of the variables if you don't already know them before you try to do the procedures.
calendar-service-port: Port number used by the Calendar Server.
calendar-pid: Process ID of a Calendar Server daemon.
calendar-process-name: Process name of a Calendar Server process such as csadmind or csnotifyd.
identifier: The Directory Server instance name used during installation. The installation program automatically adds the prefix slapd- to the name you specify. For example, if you name the identifier tango, the installation program creates the name slapd-tango.
cal-svr-base: The directory on the Calendar Server machine dedicated to holding the Calendar Server program, configuration, maintenance, and information files. The default location for the Solaris OS version of Sun Java System Calendar Server 6 is /opt/SUNWics5/cal/. See To Obtain the cal-svr-base Variable for more information on determining the value of cal-svr-base.
server-root: The placeholder for the directory where the Directory Server instances and data reside.
windbg-root: The directory on the Windows Calendar Server machine dedicated to holding the Win Debugger program, and configuration, maintenance, and information files.
The cal-svr-base variable refers to the directory on the machine that holds the Calendar Server's programs, configuration, maintenance, and information files. This is the directory in which you install the server software.