A1
|
The client has closed the connection without performing an UNBIND.
|
B1
|
This connection code can have one of the following causes:
-
The client has closed the connection without performing
an UNBIND.
-
The BER element was corrupt. If BER elements, 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 elements
can be corrupted by physical layer network problems or bad LDAP client
operations, such as an LDAP client aborting before receiving all request
results.
|
B2
|
The BER element is longer than the nsslapd-maxbersize attribute
value.
|
B3
|
A corrupt BER tag was encountered.
|
B4
|
The server failed to flush data response back to client. This
code can occur when the client closes the connection to the server,
before the server finished sending data to the client.
|
P1
|
The client connection was closed by a custom plug-in. None of
the plug-ins provided by Directory Server close a connection.
|
P2
|
A closed connection or corrupt connection has been detected.
|
T1
|
The server closed the client connection because it was idle
for longer than the idle-timeout server property.
|
T2
|
The server closed the client connection because it was stalled
for longer than the nsslapd-ioblocktimeout attribute
value. This code can occur for the following reasons:
-
There is a network problem.
-
The server sends a lot of data to the client but the
client does not read the data. As a result, the server’s transmit
buffer becomes full.
|
U1
|
The server closed the client connection because client sent
an UNBIND request.
|