|Sun ONE Directory Server 5.2 Reference Manual|
Chapter 8 Access Logs and Connection Codes
Sun ONE Directory Server 5.2 provides you with logs to help you monitor directory activity. Monitoring allows you to detect and remedy failures and, when done proactively, to anticipate and resolve potential problems before they result in failure or poor performance. To monitor your directory effectively, you need to understand the structure and content of the logs.
This chapter includes the following sections:
For information on the error codes returned in log files, see Appendix A "Error Codes."
If you require further assistance in the investigation of your access log reports, please contact Sun ONE Technical Support:
Access Log Content
The Sun ONE Directory Server 5.2 access log contains detailed information about client connections to the directory. A connection is a sequence of requests from the same client with the following structure:
- Connection record that gives the connection index and the IP address of the client
- Bind record
- Bind result record
- Sequence of operation request / operation result pairs of records (or individual records in the case of connection, closed, and abandon records)
- Unbind record
- Closed record
The access log files are located in the directory ServerRoot/slapd-serverID/logs. Each line of a log file begins with a timestamp [20/Aug/2002:11:39:51 -0700], where -0700 indicates the time difference in relation to GMT. The format of the timestamp may vary depending on the platform you are using. Apart from the connection, closed, and abandon records that appear individually, all records appear in pairs, consisting of a request for service record followed by a result record. These two records frequently appear on adjacent lines but this is not always the case.
This section presents the different levels of access logging available with Sun ONE Directory Server 5.2, then describes the default access logging content and ends with a description of the additional access logging level content. This section is divided into the following parts:
- "Access Logging Levels"
- "Default Access Logging Content"
- "Access Log Content for Additional Access Logging Levels"
Access Logging Levels
Different levels of access logging exist. By changing the value of the nsslapd-accesslog-level configuration attribute, you can select the exact type of logging you require. The default level of logging is level 256 which logs access to an entry but you can choose from the following logging levels, combining more than one level to suit your needs:
0=No access logging
4=Logging for internal access operations
256=Logging for access to an entry
512=Logging for access to an entry and referrals
131072=Precise timing of operation duration. This gives microsecond resolution for the Elapsed Time item in the access log.
For example, if you want to log internal access operations, entry access, and referrals, you would set a value of 516 (512+4) in the nsslapd-accesslog-level configuration attribute. For further information on other access log configuration attributes, see Chapter 4 "Core Server Configuration Attributes."
Default Access Logging Content
This section describes the access log content in detail, based on the default access logging level extract in Code Example 8-1.
Code Example 8-1    Access Log Extract with Default Access Logging Level (Level 256)
[22/Oct/2002:12:05:04 +0200] conn=25 op=0 msgId=1 - BIND dn="cn=Directory Manager" method=128 version=3
[22/Oct/2002:12:05:04 +0200] conn=25 op=0 msgId=1 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
[22/Oct/2002:12:07:19 +0200] conn=25 op=1 msgId=2 - ADD dn="cn=Simon Campbell,ou=People,dc=Example,dc=COM"
[22/Oct/2002:12:07:20 +0200] conn=25 op=1 msgId=2 - RESULT err=0 tag=105 nentries=0 etime=1
[22/Oct/2002:12:07:26 +0200] conn=25 op=2 msgId=3 - UNBIND
[22/Oct/2002:12:07:26 +0200] conn=25 op=2 msgId=-1 - closing (3 ops still in progress) - U1
[22/Oct/2002:12:07:27 +0200] conn=25 op=-1 msgId=-1 - closed.
[22/Oct/2002:12:09:43 +0200] conn=26 op=-1 msgId=-1 - fd=32 slot=32 HTTP connection from 126.96.36.199 to 188.8.131.52
[22/Oct/2002:12:09:45 +0200] conn=26 op=0 msgId=0 - DSML Batch Request requestID=""
[22/Oct/2002:12:09:45 +0200] conn=26 op=2 msgId=1 - DSML Modify requestID="" (parent msgId="0")
[22/Oct/2002:12:09:45 +0200] conn=26 op=2 msgId=1 - MOD dn="cn=Simon Campbell,ou=People,dc=Example,dc=COM"
[22/Oct/2002:12:09:45 +0200] conn=26 op=2 msgId=1 - RESULT err=0 tag=103 nentries=0 etime=0
[22/Oct/2002:12:09:45 +0200] conn=26 op=0 msgId=-1 - protocol=HTTP host="Foo" remlog="-" uname="-" date="[Tue, 22 Oct 2002 10:09:46 GMT]" request="POST /dsml HTTP/1.1" status="200 OK" length=565
[22/Oct/2002:12:09:45 +0200] conn=26 op=0 msgId=-1 - closing (3 ops still in progress) - (HTTP closure.)
[22/Oct/2002:12:09:46 +0200] conn=26 op=-1 msgId=-1 - closed.
[22/Oct/2002:12:11:01 +0200] conn=27 op=-1 msgId=-1 - fd=32 slot=32 LDAP connection from 127.0.0.1 to 127.0.0.1
[22/Oct/2002:12:11:01 +0200] conn=27 op=0 msgId=1 - BIND dn="cn=Directory Manager" method=128 version=3
[22/Oct/2002:12:11:01 +0200] conn=27 op=0 msgId=1 - RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=directory manager"
[22/Oct/2002:12:11:01 +0200] conn=27 op=1 msgId=2 - SRCH base="dc=Example,dc=COM" scope=2 filter="(uid=scampbell)" attrs=ALL
[22/Oct/2002:12:11:01 +0200] conn=27 op=1 msgId=2 - RESULT err=0 tag=101 nentries=1 etime=0
[22/Oct/2002:12:11:01 +0200] conn=27 op=2 msgId=3 - UNBIND
[22/Oct/2002:12:11:01 +0200] conn=27 op=2 msgId=-1 - closing (3 ops still in progress) - U1
[22/Oct/2002:12:11:02 +0200] conn=27 op=-1 msgId=-1 - closed.
Every external request is listed with an incremental connection number (conn=25, conn=26, and conn=27 in the preceding example), starting at conn=0 immediately after server startup. In this example, conn=25 represents an LDAP add operation, conn=26 is a DSML add operation and conn=27 is an LDAP search operation.
Internal LDAP requests are not recorded in the access log by default. To activate the logging of internal access operations, specify an access logging level of 4 in the nsslapd-accesslog-level configuration attribute.
Every connection from an external LDAP client to Directory Server requires a file descriptor, or socket descriptor, from the operating system (fd=32 in the preceding example). fd=32 indicates that file descriptor number 32 was used from the total pool of available file descriptors.
The slot number (slot=32 in the preceding example), has the same meaning as file descriptor. It is a legacy section of the access log and can be ignored.
In processing an external request, Directory Server performs the required series of operations. For a specific connection, all operation request and operation result pairs are given incremental operation numbers beginning with op=0 to identify the distinct operations being performed. In Code Example 8-1, op=0 is given for the bind operation request and result pair, then op=1 for the LDAP search request and result pair, and so on. Should you see op=-1 in the access log, it generally means that the LDAP request for this connection was not issued by an external LDAP client, but instead initiated internally.
The method number, in this case method=128, indicates which LDAPv3 bind method was used by the client. There are three possible bind method values:
0 = no authentication
128 = simple bind with user password
sasl= SASL bind using external authentication mechanism
The version number, in this case version=3, indicates the LDAP version number (either LDAPv2 or LDAPv3) that the LDAP client used to communicate with the LDAP server.
The error number, in this case err=0, provides the LDAP result code returned from the LDAP operation performed. The LDAP error number 0 means that the operation was successful. For a more comprehensive list of LDAP result codes see "LDAP Result Codes".
The tag number, in this case tag=97, indicates the type of result returned, which is almost always a reflection of the type of operation performed. The tags used are the BER tags from the LDAP protocol. Commonly used tags include:
tag=97 for a result from a client bind operation
tag=100 indicates the actual entry for which you were searching
tag=101 for a result from a search operation
tag=103 for a result from a modify operation
tag=105 for a result from an add operation
tag=107 for a result from a delete operation
tag=109 for a result from a moddn operation
tag=111 for a result from a compare operation
tag=115 indicates a search reference when the entry you perform your search on holds a referral to the entry you require. Search references are expressed in terms of a referral.
tag=120 for a result from an extended operation
tag=100 and tag=115 are not result tags as such. It is unlikely that you will see them in your access log.
Number of Entries
The number of entries, in this case nentries=0, indicates the number of entries that were found matching the LDAP client's request.
Elapsed time, in this case etime=1000, indicates the amount of time (in seconds) that it took Directory Server to perform the LDAP operation. An etime value of 0 means that the operation actually took milliseconds to perform. If you want to have microsecond resolution for this item in the access log, enter a value of 131328 (256+131072) in the nsslapd-accesslog-level configuration attribute.
LDAP Request Type
The LDAP request type indicates the type of LDAP request being issued by the LDAP client. Possible values are:
LDAP Response Type
The LDAP response type indicates the LDAP response being issued by the LDAP client. Possible values are:
REFERRAL=referral or search reference
Unindexed Search Indicator
The unindexed search indicator, notes=U, indicates that the search performed was unindexed, which means that the database itself had to be directly searched instead of the index file. Unindexed searches occur either when the All IDs Threshold was reached within the index file used for the search, when no index file existed, or when the index file was not configured in the way required by the search.
An unindexed search indicator is often accompanied by a large etime value, as unindexed searches are generally more time consuming.
Extended Operation OID
An extended operation OID, in this case either EXT oid="2.16.840.1.1137184.108.40.206" or EXT oid="2.16.840.1.1137220.127.116.11", provides the OID of the extended operation being performed. Table 8-1 provides the list of the LDAPv3 extended operations that are supported by Sun ONE Directory Server 5.2, and their OIDs.
Table 8-1    LDAPv3 Extended Operations Supported by Sun ONE Directory Server 5.2
Extended Operation Name
Sun ONE Directory Server 5.x Start Replication Request
Sent by a replication initiator to indicate that a replication session is requested.
Sun ONE Directory Server 5.x Replication Response
Sent by a replication responder in response to a Start Replication Request Extended Operation or an End Replication Request Extended Operation.
Sun ONE Directory Server 5.x End Replication Request
Sent to indicate that a replication session is to be terminated.
Sun ONE Directory Server 5.x Replication Entry Request
Carries an entry, along with its state information (csn and UniqueIdentifier), and is used to perform a replica initialization.
Sun ONE Directory Server 5.x Bulk Import Start
Sent by the client to request a bulk import together with the suffix being imported to and sent by the server to indicate that the bulk import may begin.
Sun ONE Directory Server 5.x Bulk Import Finished
Sent by the client to signal the end of a bulk import and sent by the server to acknowledge it.
Change Sequence Number
The change sequence number, in this case csn=3b4c8cfb000000030000, is the replication change sequence number, indicating that replication is enabled on this particular naming context.
The abandon message, in this case, [06/Aug/2002:11:39:52 -0700] conn=12 op=2 ABANDON targetop=1 msgid=2 nentries=0 etime=0, indicates that an operation has been aborted, where nentries=0 indicates the number of entries sent before the operation was aborted, etime=0 indicates how much time (in seconds) had elapsed, and targetop=1 corresponds to an operation value from a previously initiated operation (that appears earlier in the access log).
There are two possible log ABANDON messages depending on whether the message ID succeeds in locating which operation was to be aborted or not. If the message ID succeeds in locating the operation (the targetop) then the log will read as above. However, if the message ID does not succeed in locating the operation or if the operation had already finished prior to the ABANDON request being sent, then the log will read as follows:
[06/Aug/2002:11:39:52 -0700] conn=12 op=2 ABANDON targetop=NOTFOUND msgid=2
where targetop=NOTFOUND indicates that the operation to be aborted was either an unknown operation or already complete.
The message ID, in this case msgid=2, is the LDAP operation identifier, as generated by the LDAP SDK client. The message ID may have a different value to the Sun ONE Directory Server Operation Number, but identifies the same operation. The message ID is used in the context of an ABANDON operation and tells the user which client operation is being abandoned.
The Sun ONE Directory Server operation number starts counting at 0. In the majority of LDAP SDK/client implementations the message ID number starts counting at 1. This explains why the message ID is frequently equal to the Sun ONE Directory Server operation number plus 1.
SASL Multi-Stage Bind Logging
Sun ONE Directory Server 5.2 logging for multi-stage binds is now more explicit. Each stage in the bind process is logged and, where appropriate, the progress statement SASL bind in progress is included.
The authenticated DN (the DN used for access control decisions) is logged in the BIND result line and not in the bind request line:[06/Aug/2002:11:39:55 -0700] conn=14 op=1 RESULT err=0 tag=97 nentries=0 etime=0 dn="uid=coulbeck,dc=example,dc=com"
For SASL binds, the DN value displayed in the BIND request line is not used by the server and is, therefore, not relevant. However, given that the authenticated DN is the DN which, for SASL binds, must be used for audit purposes, it is essential that this be clearly logged. Having this authenticated DN logged in the BIND result line avoids any confusion as to which DN is which.
Access Log Content for Additional Access Logging Levels
This section presents the additional access logging levels available in the Sun ONE Directory Server 5.2 access log.
In Code Example 8-2, access logging level 512, which logs access to entries and referrals, is enabled. In this extract, 6 entries and 1 referral are returned in response to the search request in bold.
Code Example 8-2    Access Log Extract with Entry Access and Referral Logging Level (Level 512)
[06/Aug/2002:16:43:02 +0200] conn=306 op=0 ENTRY dn="ou=Special Users,dc=example,dc=com"
[06/Aug/2002:16:43:02 +0200] conn=306 op=0 ENTRY dn="cn=Accounting Managers,ou=groups,dc=example,dc=com"
[06/Aug/2002:16:43:02 +0200] conn=306 op=0 ENTRY dn="cn=HR Managers,ou=groups,dc=example,dc=com"
[06/Aug/2002:16:43:02 +0200] conn=306 op=0 ENTRY dn="cn=QA Managers,ou=groups,dc=example,dc=com"
In Code Example 8-3, access logging level 4, which logs internal operations, is enabled.
Code Example 8-3    Access Log Extract with Internal Access Operations Level (Level 4)
[06/Aug/2002:16:45:46 +0200] conn=Internal op=-1 SRCH base="cn=\22dc=example,dc=com\22,cn=mapping tree,cn=config"scope=0 filter="objectclass=nsMappingTree"attrs="nsslapd-referral" options=persistent
06/Aug/2002:16:45:46 +0200] conn=Internal op=-1 RESULT err=0 tag=48 nentries=1etime=0
[06/Aug/2002:16:45:46 +0200] conn=Internal op=-1 SRCH base="cn=\22dc=example,dc=com\22,cn=mapping tree,cn=config"
scope=0 filter="objectclass=nsMappingTree" attrs="nsslapd-state"
[06/Aug/2002:16:45:46 +0200] conn=Internal op=-1 RESULT err=0 tag=48 nentries=1etime=0
Access log level 4 enables logging for internal operations which log the details of the search being performed, and the search base, scope, filter, and requested search attributes.
The connection description, in this case conn=Internal, indicates that the connection is an internal connection. The operation number op=-1 indicates that the operation was initiated internally.
The options description, in this case options=persistent, indicates that a persistent search is being performed. Persistent searches can be used as a form of monitoring. They can be configured to return changes to given configurations when changes occur.
The Sun ONE Directory Server 5.2 access log distinguishes between persistent and regular searches. Some earlier Directory Server releases did not make this distinction.
In Code Example 8-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 8-4    Access Log Extract with Internal Access Operation, Entry Access and Referral Logging Levels (Levels 4+512)
[06/Aug/2002:16:45:46 +0200] conn=Internal op=-1 ENTRY dn="cn=\22dc=example,dc=com\22, cn=mapping tree, cn=config"
[06/Aug/2002: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 closed log message to provide additional information related to the connection closure. Common connection codes include:
A1=Client aborts the connection.
B1=Corrupt BER tag encountered or BER tag is longer than the nsslapd-maxbersize attribute value. For further information about this configuration attribute, see "nsslapd-maxbersize (Maximum Message Size)".
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 "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.
T2=Server closed connection after ioblocktimeout period was exceeded.
U1= Connection closed by server after client sends an UNBIND request. The server will always close the connection when it sees an UNBIND request.
LDAP Result Codes
LDAP has a set of operation result codes with which you should be familiar. The following result codes may be generated by the LDAP server:
Table 8-2    LDAP Server Result Codes
Authentication method not supported
Strong authentication required
Partial results and referral received
Administrative limit exceeded
Unavailable critical extension
SASL bind in progress
No such attribute
Undefined attribute type
Type or value exists
No such object
Invalid DN syntax
Object is a leaf
Alias dereferencing problem
Server is busy
Server is unavailable
Server is unwilling to perform
Object class violation
Operation not permitted on a non-leaf entry
Operation not permitted on a RDN
Entry already exists
Cannot modify object class
Results too large
Affects multiple servers
Virtual list view error
The following result codes may be generated by LDAP clients:
Table 8-3    LDAP Client Result Codes
Cannot contact LDAP server
Unknown authentication method
Bad search filter
User cancelled operation
Bad parameter to an LDAP routine
Out of memory
Cannot connect to the LDAP server
Not supported by this version of LDAP
Requested LDAP control not found
No results returned
Additional results to return
Client detected loop
Referral hop limit exceeded