Provisioning Reference Guide › Provisioning Maintenance › View and Maintain Log Files › Diagnostic Logging › SLAPD and C++ Connector Server Logs

SLAPD and C++ Connector Server Logs

On Windows, you can enable SLAPD logging for advanced debugging tasks such as LDAP protocol packet handling and search-filter processing. You can set the log level in the Windows registry by assigning a value to the DebugLevel key. There are two registry keys, each controlling the logging for one of the services:

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\slapd\im_ps\CurrentVersion\DebugLevel

The im_ps registry key controls logging for im_ps.exe, run by the Provisioning Server service.

HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\slapd\im_ccs\CurrentVersion\DebugLevel

The im_ccs registry key controls logging for im_ccs.exe, run by the Connector Server service.

Important! The preferred method for enabling SLAPD logging is by setting the loglevel parameter in im_ps.conf or im_ccs.conf, for both Windows and Solaris. Each file contains configuration instructions.

The DebugLevel registry key or loglevel configuration file parameter specifies the amount of information the server writes to its log file, which is one of the following, depending upon your type of slapd service:

• PSHOME\Logs\im_ps.log
• PSHOME\Logs\im_ccs.log

Note: A "TLS: can't accept" error message may appear in the im_ps.log file when running in FIPS mode due to a low-level initialization problem that clears up after the first connection from a client. Since clients retry connections, you can ignore this message.

You can select a debug level to match the type of debugging you want to perform. The debug levels are listed in the following table: