Enabling and Gathering Sametime Community Server Logs

The Sametime® Community Server includes a utility that automatically collects configuration and log files for problem determination. You can then provide this information to HCL Support to investigate Sametime Community Server issues.

About this task

The recommended trace level for gathering general diagnostic information is VP_TRACE_ALL=1. However, this trace level is very verbose and should be used only on servers that have available disk space and CPU utilization to spare. If you need to enable trace on a production server that is running near capacity, contact HCL Support to get specific diagnostic settings that have a lower impact on system resources.

Tracing not included in VP_TRACE_ALL

VP_TRACE_ALL enables most of the general diagnostic information on a Sametime Community server. There are services not included in this trace setting which can be set individually.

For Sametime Chat history tracing, add to the [stchathistory] section of the sametime.ini:
For Sametime Buisness Card tracing, add to the [Debug] section of the sametime.ini:
For Sametime Policy tracing, add to the [Debug] section of the sametime.ini:

For more information on component level tracing, see Common debug parameters for Sametime Community Server.

Follow these instructions to set the trace level on the community server. Once these steps are completed, reproduce the problem so the information will be gathered in the logs. Always maintain a backup copy of any configuration files before making changes.

<Program directory> example: Programs/hcl/domino

<Data directory> example: Programs/hcl/domino/data


  1. Stop both the Domino® server. This will stop the Sametime Community Server.
  2. Remove old log files from the Sametime trace directory. This is usually located in the <Program Directory>/trace folder. Do not delete the trace folder.
  3. Edit the sametime.ini file (as administrator), which is in the <Program directory>. Locate the [Debug]section of this file
  4. Add or modify the following line to the [Debug] section:


  5. Optional: In addition to setting the trace level, you can set the maximum file size of each trace file, and the maximum number of trace files used until the files are recycled.
    Table 1. Trace Settings
    Trace Settings Description
    ST_TRACEFILE_SIZE To set the maximum file size of each trace file. The default value is 20.
    ST_TRACEFILE_CNT To set the number of trace files generated per Sametime service application. The default value is 25.
    ST_TRACEFILE_SIZE ST_TRACEFILE_SIZE multiplied by ST_TRACEFILE_CNT equals the maximum size of the trace files on the operating system hard disk per Sametime service application.

    For example, if the sametime.ini file contains the following settings:

    ST_TRACEFILE_SIZE=20ST_TRACEFILE_CNT=25Then 10 X 25 equals 250, so 250 MB is the maximum disk space each Sametime service application consumes for the trace files.

  6. Save and close the sametime.ini.
  7. Stop and start the Domino server. Sametime will stop/start automatically with Domino.
  8. Reproduce the problem that you want to troubleshoot, and diagnostic information will be gathered in the logs.
  9. Run the stdiagzip collector utility, as shown in the following sample paths:


    C:\Program Files\hcl\domino\stdiagzip.bat


    /local/notesdata> sh stdiagzip.sh

  10. The output file is a compressed file in the <Program directory>/Trace directory in the following format: stdiags_hostname_MM_DD@hh_mm.zip

    To inspect this file, use a tool such as WinZip or 7Zip to extract the file content instead of using the Windows Explorer unzip tool.

  11. Collect the following data:
    • Details of user IDs that were used to reproduce the problem.
    • The exact time and date of the reproduced failure.
    • Client Application type and version that was used to reproduce the problem.
    • If you are troubleshooting a server crash, send all of the core dump (NSD log) files that were created at the time of the crash.
    • Any additional details about the deployment, configuration, abnormal behavior, or any other general details that might help the HCL Support Team investigate the problem.
    • For newly installed servers, include the <Data directory>_HCL_Sametime_Server_version directory

What to do next

After collecting the diagnostic information, any trace which was enabled on the Community Server should be disabled or reverted to the default level. Stop and start the Domino Server again once the sametime.ini has been updated to remove trace details.

If you need assist troubleshooting the Sametime Community Server, please open a product case with HCL Support and upload the collected data to your case.