Ben Beuchler writes:
Apr 11 15:06:43 cliff slapd: conn=1 op=36051 BIND anonymous
Apr 11 15:06:43 cliff slapd: conn=1 op=36051 BIND dn="" method=128
Apr 11 15:06:43 cliff slapd: connection_input: conn=1 deferring
operation: pending operations
Apr 11 15:06:43 cliff slapd: conn=1 op=36051 RESULT tag=97 err=0 text=
I can't find a reference to '97' anywhere in the above mentioned RFC.
Is there somewhere else I should look?
97 is BindResponse. But it's easier to take the conn=1 op=36051 in the
RESULT, and find the matching conn=1 op=36051 request. Each request on
a connection gets its own op number. Don't be confused by the several
BINDs with the same conn+op - that means several things are happening
with that request or slapd wanted to log more than one line's worth of
data. In this case, the mech=implicit Bind is because any Bind first
reverts the connection to anonymous if it is not already anonymous.
BTW, I notice the requests/responses you've posted were less than 2 or
often 1 seconds apart - is that how long clients hang, or are there some
really long hangs?
On another note, maybe you can dispatch the Binds to e.g. 4 processes
and thus 4 connections, thus reducing much of the sequencing.