Common Connection Codes - Netscape DIRECTORY SERVER 6.02 Configuration Manual

Common Connection Codes

NOTE
In Code Example 5-4 both access logging level 512 and 4 are enabled, which results
in both internal access operations, as well as entry access and referrals being
logged.
Code Example 5-4
[12/Jul/2001:16:45:46 +0200] conn=Internal op=-1 ENTRY
dn="cn=\22dc=example,dc=com\22, cn=mapping tree, cn=config"
[12/Jul/2001: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 which is added to the
additional information related to the connection closure. Common connection
codes include:
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
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
information about this configuration attribute see "nsslapd-maxbersize (Maximum
Message Size)," on page 60.
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
190 Netscape Directory Server Configuration, Command, and File Reference • May 2002
Directory Server access log now distinguishes between persistent
and regular searches, which was not the case for previous Directory
Server releases.
Access Log Extract with Internal Access Operation, Entry Access
and Referral Logging Levels (Levels 4+512)
connection code is logged to the access log. BER tags can be
B1
nsslapd-maxbersize
log message to provide
closed
attribute value. For further