Table
Setting | Console name | Description |
8 | Connection management | Logs the current connection status, including the connection |
|
| methods used for a SASL bind. |
|
|
|
16 | Packets sent/received | Print out the numbers of packets sent and received by the |
|
| server. |
|
|
|
32 | Search filter processing | Logs all the functions called by a search operation. |
|
|
|
64 | Config file processing | Prints any .conf configuration files used with the server, |
|
| line by line, when the server is started. By default, only |
|
| |
|
|
|
128 | Access control list processing |
|
|
|
|
2048 | Log entry parsing. | Logs schema parsing debugging information. |
|
|
|
4096 | Housekeeping | Housekeeping thread debugging. |
|
|
|
8192 | Replication | Logs detailed information about every |
|
| operation, including updates and errors, which is important |
|
| for debugging replication problems. |
|
|
|
16384 | Default | Default level of logging used for critical errors and other |
|
| messages that are always written to the error log, such as |
|
| server startup messages. Messages at this level are always |
|
| included in the error log, regardless of the log level setting. |
|
|
|
32768 | Entry cache | Database entry cache debugging. |
|
|
|
65536 | Writes an entry to the log file when a server | |
|
| |
|
| , so this is used for server |
|
|
|
131072 |
| Microsecond resolution for timestamps instead of the default |
|
| seconds. This cannot be enabled in the Directory Server |
|
| Console. |
|
|
|
262144 | Access control summary | Summarizes information about access to the server, much |
|
| less verbose than level 128. This value is recommended for |
|
| use when a summary of access control processing is needed. |
|
| Use 128 for very detailed processing messages. |
|
|
|
The error log format is simpler than the access log entries. It is also more flexible because the kind of information returned depends on the service or operation which is writing the log entry. Generally, error log entries contain the following elements:
•A timestamp, such as [05/Aug/2009:02:27:22
•The
•Functions called by the
•Messages returned by the
Frequently, the messages for an operation appear on multiple lines of the log, but these are not identified with a connection number or operation number.
Example
182 Log file reference