Access Log Content
Slot Number
The slot number, in this case
, is a legacy part of the access log which
slot=608
has the same meaning as file descriptor. Ignore this part of the access log.
Operation Number
To process a given LDAP request, Directory Server will perform the required
series of operations. For a given connection, all operation request and operation
result pairs are given incremental operation numbers beginning with
to
op=0
identify the distinct operations being performed. In Code Example 5-1 on page 199
we have
for the bind operation request and result pair, then
for the
op=0
op=1
LDAP search request and result pair, and so on. Should you see
in the access
op=-1
log it generally means that the LDAP request for this connection was not issued by
an external LDAP client, but instead initiated internally.
Method Type
The method number, in this case
, indicates which LDAPv3 bind
method=128
method was used by the client. There are three possible bind method values:
= no authentication
0
= simple bind with user password
128
= SASL bind using external authentication mechanism
sasl
Version Number
The version number, in this case,
, indicates the LDAP version
version=3
number (either LDAPv2 or LDAPv3) that the LDAP client used to communicate
with the LDAP server.
Error Number
The error number, in this case
, provides the LDAP result code returned
err=0
from the LDAP operation performed. The LDAP error number
means that the
0
operation was successful. For a more comprehensive list of LDAP result codes
see "LDAP Result Codes," on page 210.
Tag Number
The tag number, in this case
, indicates the type of result returned, which
tag=97
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:
for a result from a client bind operation
tag=97
Chapter 5
Access Log and Connection Code Reference
201
Need help?
Do you have a question about the NETSCAPE DIRECTORY SERVER 6.2 and is the answer not in the manual?
Questions and answers