127
127
A configuration directive may take arguments. If so, the arguments are
128
separated by white space. If an argument contains white space,
128
separated by whitespace. If an argument contains whitespace,
129
129
the argument should be enclosed in double quotes {{EX:"like this"}}.
130
130
In the descriptions that follow, arguments that should be replaced
131
131
by actual text are shown in brackets {{EX:<>}}.
171
171
enabled). Log levels may be specified as integers or by keyword.
172
172
Multiple log levels may be used and the levels are additive.
173
173
To display what levels
174
correspond to what kind of debugging, invoke slapd with {{EX:-?}}
174
correspond to what kind of debugging, invoke slapd with {{EX:-d?}}
175
175
or consult the table below. The possible values for <level> are:
177
177
!block table; colaligns="RL"; align=Center; \
178
178
title="Table 5.1: Debugging Levels"
179
Level Keyword Description
180
-1 Any enable all debugging
182
1 Trace trace function calls
183
2 Packets debug packet handling
184
4 Args heavy trace debugging
185
8 Conns connection management
186
16 BER print out packets sent and received
187
32 Filter search filter processing
188
64 Config configuration processing
189
128 ACL access control list processing
190
256 Stats stats log connections/operations/results
191
512 Stats2 stats log entries sent
192
1024 Shell print communication with shell backends
193
2048 Parse print entry parsing debugging
194
4096 Cache database cache processing
195
8192 Index database indexing
196
16384 Sync syncrepl consumer processing
179
Level Keyword Description
180
-1 any enable all debugging
182
1 (0x1 trace) trace function callss
183
2 (0x2 packets) debug packet handling
184
4 (0x4 args) heavy trace debugging
185
8 (0x8 conns) connection management
186
16 (0x10 BER) print out packets sent and received
187
32 (0x20 filter) search filter processing
188
64 (0x40 config) configuration processing
189
128 (0x80 ACL) access control list processing
190
256 (0x100 stats) stats log connections/operations/results
191
512 (0x200 stats2) stats log entries sent
192
1024 (0x400 shell) print communication with shell backends
193
2048 (0x800 parse) print entry parsing debugging
194
16384 (0x4000 sync) syncrepl consumer processing
195
32768 (0x8000 none) only messages that get logged whatever log level is set
198
The desired log level can be input as a single integer that
199
combines the (ORed) desired levels, both in decimal or in hexadecimal
200
notation, as a list of integers (that are ORed internally), or as a list of the names that are shown between brackets, such that
205
> olcLogLevel 0x80 0x1
206
> olcLogLevel acl trace
203
214
This will cause lots and lots of debugging information to be
206
E: olcLogLevel: Conns Filter
217
E: olcLogLevel conns filter
208
219
Just log the connection and search filter processing.
223
Log those messages that are logged regardless of the configured loglevel. This
224
differs from setting the log level to 0, when no logging occurs. At least the
225
{{EX:None}} level is required to have high priority messages logged.
212
E: olcLogLevel: Stats
231
Basic stats logging is configured by default. However, if no olcLogLevel is
232
defined, no logging occurs (equivalent to a 0 level).
215
235
H4: olcReferral <URI>