Common Connection Codes; Ldap Result Codes - Red Hat DIRECTORY SERVER 7.1 Configuration

Code Example 5-4
[12/Jul/2005:16:45:46 +0200] conn=Internal op=-1 ENTRY
dn="cn=\22dc=example,dc=com\22, cn=mapping tree, cn=config"
[12/Jul/2005:16:45:46 +0200] conn=Internal op=-1 ENTRY
dn="cn=\22dc=example,dc=com\22, cn=mapping tree, cn=config"

Common Connection Codes

A connection code is a code that is added to the
additional information related to the connection closure. Common connection
codes include:
•
A1
•
B1
sent over the wire, are corrupt when they are received, a
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
further information about this configuration attribute, see
"nsslapd-maxbersize (Maximum Message Size)," on page 68.
•
B3
•
B4
•
P2
•
T1
•
T2
•
U1
server will always close the connection when it sees an UNBIND request.

LDAP Result Codes

LDAP has a set of result codes with which it is useful to be familiar.
Access Log Extract with Internal Access Operation, Entry Access
and Referral Logging Levels (Levels 4+512)
= Client aborts the connection.
= Corrupt BER tag encountered. If BER tags, which encapsulate data being
= BER tag is longer than the
= Corrupt BER tag encountered.
= Server failed to flush data response back to client.
= Closed or corrupt connection has been detected.
= Client does not receive a result within the specified
= Server closed connection after
= Connection closed by server after client sends an UNBIND request. The
log message to provide
closed
nsslapd-maxbersize
ioblocktimeout
Chapter 5 Access Log and Connection Code Reference
Common Connection Codes
connection code is
B1
attribute value. For
period.
idletimeout
period was exceeded.
221