Bind Logs for Directory Proxy Server

Bind logs contain information about the successful bind operations received from the clients. This is the same information placed in the access log, but the information is replicated to avoid loosing it when old access logs are deleted.

Format of a Bind Log Message

A bind log message has this format:

timestamp - category - severity -
 connectionNumber operationNumber messageID operationType messageText

The category is always BIND and severity is always INFO.

Example 23-3 Extract of a Bind Log

[07/Sep/2010:14:32:38 +0200] - BIND - INFO - conn=11 op=1 msgid=2 BIND 
    dn="cn=proxy manager" method="NONE" version=3 controls=""

[07/Sep/2010:14:32:43 +0200] - BIND - INFO - conn=12 op=0 msgid=396 BIND 
    dn="uid=jvedder,ou=people,dc=example,dc=com" method="SIMPLE" version=3 controls=""

Message Part in a Bind Log

Bind messages are similar to the bind messages in the access log. See Content of Access, Error, and Audit Logs.

Bind Log Buffer

Bind log messages are stored in a buffer. The buffer is flushed to the bind log at the following times:

• When the buffer is full

• When the bind log is rotated

• When the Directory Proxy Server is stopped

• Every 2.5 seconds

By default, the size of the bind log buffer is 1M. However, the size of the buffer can be configured to control the frequency with which it is flushed. Setting the buffer size to 0 will disable buffering (and make Directory Proxy Server slower).

You can configure the size of the bind log buffer by setting the log-buffer-size property. For information about how to configure bind log properties, see Configuring Directory Proxy Server Logs in Oracle Directory Server Enterprise Edition Administration Guide.