Sun Gathering Debug Data for Sun Java System Calendar Server

ProcedureTo Collect Debug Data on a Calendar Server Crashed Process

Use this task to collect data when a Calendar Server process has stopped (crashed) unexpectedly.

On Solaris systems, you can easily gather the required data by running the cscapture command.


For more information about running cscapture, see Using Calendar Server Capture (cscapture) to Collect Debug Data for Sun Java System Calendar Server.

The cscapture command gathers ps, swap, gcore, pkg_app, and other data.

On all other platforms, manually run all the commands on the actual machine where the core file(s) were generated, as described in the following procedure.

  1. Collect the general system information as explained in To Collect Required Debug Data for Any Calendar Server Problem.

  2. Note whether you can you restart Calendar Server. If the problem is reproducible, provide a test case that can be reproduced in the Sun Support Center labs.

  3. Get the output of the following commands.


    ps -ef | grep cal-svr-basevmstat 5 5iostat -xtopsar


    ps -aux | grep cal-svr-basevmstat 5 5topuptimesar


    Obtain the CALENDAR process PID: C:\windbg-root>tlist.exe

    Obtain process details of the CALENDAR running process PID: C:\windbg-root>tlist.exe calendar-pid

    Note –

    To use the preceding commands on Windows systems, you need to install the debugging tools, available from the following url:

    Install the latest version of the debugging tools and OS symbols for your version of Windows.

    You also must add the environment variable "_NT_SYMBOL_PATH".

  4. Get the swap information.






    Already provided in C:\report.txt as described in To Collect Required Debug Data for Any Calendar Server Problem.

  5. Get the system logs.






    Event log files:Start-> Settings-> Control Panel —> Event Viewer-> Select LogThen click Action-> Save log file as

  6. Get core files (called “Crash Dumps” by Windows).

    Solaris OS

    See 1.6 Configuring Solaris OS to Generate Core Files if a core file was not generated.


    Core dumps are turned off by default in the /etc/profile file. You can make per user changes by editing your ~/.bash_profile file. Look for the following line:

    ulimit -S -c 0 > /dev/null 2>&1

    You can either comment out the entire line to set no limit on the size of the core files or set your own maximum size.


    Generate a crash dump during a crash of Calendar Server by using the following commands:

    Get the CALENDAR process PID : C:\windbg-root>tlist.exeGenerate a crash dump when the CALENDAR process crashes: C:\windbg-root>adplus.vbs -crash -FullOnFirst -p calendar-pid -o C:\crashdump_dir

    The adplus.vbs command watches calendar-pid until it crashes and will generate the dmp file. Provide the complete generated folder under C:\crashdump_dir.

    Note –

    If you didn't install the Debugging Tools for Windows, you can use the drwtsn32.exe -i command to select Dr. Watson as the default debugger. Use the drwtsn32.exe command, check all options, and choose the path for crash dumps. Then provide the dump and the drwtsn32.log files.