Troubleshooting

Several strategies exist to help diagnose and solve problems in a container deployment.

Tracing

Configuration

Two configuration entries can be used to enable tracing when the container first starts.
Table 1. Configuration Entries
Entry Description
debug.startup This configuration entry is used to enable tracing of the bootstrapping and configuration process.
debug.runtime This configuration entry is used to set the debug level of the runtime process. The debug level value is a bit mask that controls which output is generated, with values in the range 1 - 65535. For information about debug levels, see Debugging levels.For information about debug levels, see the Debugging levels topic in the Command Reference Guide.
Note: The runtime trace is sent to the file: /var/isvd/logs/ibmslapd.trace.log
Dynamically Enabling Trace

It is possible to dynamically enable trace after the container is started by running the idsldaptrace command from within the running container. For more information about how to dynamically enable trace, see Collecting trace information.For more information about how to dynamically enable trace, see the Other diagnostic tools > Collecting trace information topic in the Troubleshooting and Support Guide.