Sametime Community Server diagnostic files

Log files

Log files are named Sametime_ YYYYMMDD.log, where YYYYMMDD represents a date. The log files are located in the trace folder. You can change the default trace file location by adding or editing the ST_TRACE_PATH setting in the [Config] section of the sametime.ini file to point to an alternative folder path.

When the Community Server starts, a script runs that purges old logs. By default the script purges sametime_YYYYMMDD.log files older than 30 days. You can change how long log files are kept adding or editing the ST_PURGE_LOGS_OLDER_THAN setting in the sametime.ini file.

Sametime.err file

The Sametime.err file includes detailed information about errors that occur when users attempt to log in to the Sametime Community Server. The name of the process always displays in the log file. Other information relevant to the login is also included, such as UserID, UserName, and UserCluster. Most errors are configuration-related problems that you can fix.

NSD log and core dump files

When a Community Server process crashes, an NSD log is created in the server's trace directory. The NSD log contains information about the tasks that were running when the process crashed, as well as general system information that may help determine the cause of the crash.

In addition, part of the Sametime Community Components, using Notes® API libraries, creates an NSD log in the IBM_TECHNICAL_SUPPORT directory.

Trace files

Trace files are created in the trace folder and use the following format for file names:

Process-name_Process-start-date_Process-start-time_Process-ID_Trace-file-counter

Once a process starts, most of the components in the name of the trace file remain unchanged until the process is restarted. Only the counter part changes. The process name is the only component that is required in the file name; other components are optional.