It looks like that client is trying a SASL bind, then issuing a simple
bind prior to receiving the SASL bind response. I don't think that's
permitted per RFC; hence, slapd defers the simple bind?
On Wed, 11 Apr 2007, Ben Beuchler wrote:
> Include 256 in your loglevel, if you haven't already, and
look for the
> '<date> swizzle slapd[<pid>]: conn=<num> ...' lines it
> In particular, look for 'conn=<num> op=<num> RESULT' lines
> the 'deferring operation' line, where the matched received operation
> (same conn and op) was _before_ that line. Notice what the operation
> was, and what the result code was (RESULT ... err=). You'll find the
> result code descriptions in RFC 4511.
The examples I could find all look like this:
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?