Slot Number; Operation Number; Method Type; Version Number - Red Hat DIRECTORY SERVER 7.1 Configuration

Slot Number

The slot number, in this case
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
distinct operations being performed. In Code Example 5-1, on page 211, we have
for the bind operation request and result pair, then
op=0
request and result pair, and so on. Should you see
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
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
(either LDAPv2 or LDAPv3) that the LDAP client used to communicate with the
LDAP server.

Error Number

The error number, in this case
the LDAP operation performed. The LDAP error number
operation was successful. For a more comprehensive list of LDAP result codes, see
"LDAP Result Codes," on page 221.

Tag Number

The tag number, in this case
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
, is a legacy part of the access log which has
slot=608
, indicates which LDAPv3 bind
method=128
, indicates the LDAP version number
version=3
, provides the LDAP result code returned from
err=0
, indicates the type of result returned, which is
tag=97
Chapter 5
Access Log Content
to identify the
op=0
for the LDAP search
op=1
in the access log, it
op=-1
means that the
0
Access Log and Connection Code Reference 213