T able 5.3. Common Connection CodesConnection Code DescriptionA1 Client aborts the connection.B1 Corrupt BER tag encountered. If BER tags, whichencapsulate data being sent over the wire, arecorrupt when they are received, a B1 connectioncode is logged to the access log. BER tags canbe corrupted due to physical layer networkproblems or bad LDAP client operations, such asan LDAP client aborting before receiving allrequest results.B2 BER tag is longer than the nsslapd-maxbersizeattribute value. For further information about thisconfiguration 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 toclient.P2 Closed or corrupt connection has been detected.T 1 Client does not receive a result within thespecified idletimeout period. For furtherinformation about this configuration attribute, seeSection 2.3.1.60, “nsslapd-idletimeout (Default IdleT imeout)”.T 2 Server closed connection after ioblocktimeoutperiod was exceeded. For further informationabout this configuration attribute, seeSection 2.3.1.62, “nsslapd-ioblocktimeout (IOBlock T ime Out)”.U1 Connection closed by server after client sends anunbind request. T he server will always close theconnection when it sees an unbind request.5.2. Error Log ReferenceT he Directory Server error log records messages for Directory Server transactions and operations.T hese may be error messages for failed operations, but it also contains general information about theprocesses of Directory Server and LDAP tasks, such as server startup messages, logins and searchesof the directory, and connection information.5.2.1. Error Log Logging LevelsT he error log can record different amounts of detail for operations, as well as different kinds ofinformation depending on the type of error logging enabled.T he logging level is set in the nsslapd-errorlog-level configuration attribute. T he default log level is16384 , which included critical error messages and standard logged messages, like LDAP results codesand startup messages. As with access logging, error logging levels are additive. T o enable bothreplication logging (8192) and plug-in logging (65536), set the log level to 73728 (8192 + 65536).NOTEEnabling high levels of debug logging can significantly erode server performance. Debug loglevels, such as replication (8192) should only be enabled for troubleshooting, not for dailyoperations.166 Chapter 5. Log File Reference