Red Hat 8.1 - Manual (Page 166)

Table 5.3. Common Connection Codes
Connection Code Description
A1 Client aborts the connection.
B1 Corrupt BER tag encountered. If BER tags, which
encapsulate data being sent over the wire, are
corrupt when they are received, a B1 connection
code is logged to the access log. BER tags can
be corrupted due to physical layer network
problems or bad LDAP client operations, such as
an LDAP client aborting before receiving all
request results.
B2 BER tag is longer than the nsslapd-maxbersize
attribute value. For further information about this
configuration attribute, see
Section 2.3.1.76,
“nsslapd-maxbersize (Maximum Message Size)” .
B3 Corrupt BER tag encountered.
B4 Server failed to flush data response back to
client.
P2 Closed or corrupt connection has been detected.
T1 Client does not receive a result within the
specified idletimeout period. For further
information about this configuration attribute, see
Section 2.3.1.60, “nsslapd-idletimeout (Default Idle
Timeout)”
.
T2 Server closed connection after ioblocktimeout
period was exceeded. For further information
about this configuration attribute, see
Section 2.3.1.62, “nsslapd-ioblocktimeout (IO
Block Time Out)”
.
U1 Connection closed by server after client sends an
unbind request. The server will always close the
connection when it sees an unbind request.
5.2. Error Log Reference
The Directory Server error log records messages for Directory Server transactions and operations.
These may be error messages for failed operations, but it also contains general information about the
processes of Directory Server and LDAP tasks, such as server startup messages, logins and searches
of the directory, and connection information.
5.2.1. Error Log Logging Levels
The error log can record different amounts of detail for operations, as well as different kinds of
information depending on the type of error logging enabled.
The logging level is set in the nsslapd-errorlog-level configuration attribute. The default log level is
16384 , which included critical error messages and standard logged messages, like LDAP results codes
and startup messages. As with access logging, error logging levels are additive. To enable both
replication logging (8192) and plug-in logging (65536), set the log level to 73728 (8192 + 65536).
NOTE
Enabling high levels of debug logging can significantly erode server performance. Debug log
levels, such as replication (8192) should only be enabled for troubleshooting, not for daily
operations.
166
Chapter 5. Log File Reference