Collect information for IBM
® Support to investigate Sametime
® awareness problems and related issues.
About this task
The recommended trace level for gathering general diagnostic information, VP_TRACE_ALL=1
, is very verbose, and therefore should only be used in on servers which have available disk space and CPU utilization to spare. If you are enabling trace on a production server which is running near capacity, please contact IBM
Support to get more specific diagnostic settings which do not have as high of an impact on system resource.
Follow these instructions to set the trace level, and then reproduce the problem to gather information.
- Stop the Lotus® Domino® and Sametime Community Server.
- Remove old log files from the Sametime trace directory.
- Use a text editor to edit the sametime.ini file, which is located in the Sametime Community Server installation directory (for example: C:\Program Files\lotus\domino). Add the following line to the Debug section to set the trace level:
- Restart the Lotus Domino and Sametime Community Server.
- Reproduce the problem that you want to troubleshoot, so you can collect diagnostic information.
- Collect diagnostic information:
- Run the following collector utility: stdiagzip.bat located in the Sametime binary folder. For Windows®, this is C:\Lotus\Domino by default.
The output file is in the following format:
- Collect the following data:
- The sametime.log file - Preserve as much history as possible. Do not remove data from this log.
- The sametime.ini file
- The communityConfig.txt file
- The Stlog.nsf file - Keep this file small, not more then 1M.
- 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 the core dump files which 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 IBM Support with the problem investigation.
What to do next
After collecting the diagnostic information, any trace which was enabled on the Sametime
Community Server should be disabled or reverted back to the default level. Use the STRuntimeDebug tool to enable and disable traces without having to restart the server.
Parent topic: Troubleshooting general issues in the Sametime Community Server
Sametime Community Server trace files location
NSD Log and core dump file location
Controlling the size and content of diagnostic data
Gathering Sametime Community Server name change utility diagnostic data
Sametime Community Server log and trace file formats