By Patrice Duc-Jacquet on Oct 10, 2008
Enable dxadm commands debug information
Traces can be enabled in administrative commands through environment variables :
DPS use :
possible values described in file <ws>/ldap/dps/dpx/ddx.h
possible values described in file <ws>/ldap/ds/slapx/slapx.h
Note : those traces are not documented !
e.g DDX_DEBUG_AREA=-1 (means DEBUG_AREA_ANY)
additional setting SPAWNER_DEBUG=1 will dump data input and result code of the spawner lib.
Enable DPS Debug traces
Enable DS Debug traces
- stop DS instance
- Edit <instance_path>/config/dse.ldif and add the following line
- start DS instance
Each component is identified as an area, whose value is a decimal translation of the hex values. The log area is additive. For example, to enable logging on search filter processing (32) and Config file processing (64), you would set this attribute to value=96 (32+64). The valid range includes the following values:
Default logging area, used for critical errors and other messages that are always written to the error log, for example server startup messages. Messages at this level are always included in the error log regardless of the nsslapd-infolog-level setting.
Trace function calls. Logs a message when the server enters and exits a function.
Search arguments processing.
Print out packets sent/received
Search filter processing
Config file processing
Access control list processing
Log LDIF entry parsing debugging
Housekeeping thread debugging
Database cache debugging.
Server plug-in debugging. An entry is written to the log file when a server plug-in calls slapi_log_info_ex().
Enable DSCC Debug traces
to be done