[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: deferring operation: pending operations
The examples I could find all look like this:
Apr 11 15:06:43 cliff slapd[15355]: conn=1 op=36051 BIND anonymous
mech=implicit ssf=0
Apr 11 15:06:43 cliff slapd[15355]: conn=1 op=36051 BIND dn="" method=128
Apr 11 15:06:43 cliff slapd[15355]: connection_input: conn=1 deferring
operation: pending operations
Apr 11 15:06:43 cliff slapd[15355]: 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?
My apologies; I neglected to include an example of the "deferring
operation: binding" log entries:
Apr 11 15:14:49 cliff slapd[15355]: conn=1 op=36640 BIND anonymous
mech=implicit ssf=0
Apr 11 15:14:49 cliff slapd[15355]: conn=1 op=36640 BIND
dn="uid=bbrogan,dc=users,dc=accounts,dc=ldap,dc=mcad,dc=edu"
method=128
Apr 11 15:14:49 cliff slapd[15355]: conn=1 op=36640 BIND
dn="uid=bbrogan,dc=users,dc=accounts,dc=ldap,dc=mcad,dc=edu"
mech=SIMPLE ssf=0
Apr 11 15:14:49 cliff slapd[15355]: conn=1 op=36640 RESULT tag=97 err=0 text=
Apr 11 15:14:50 cliff slapd[15355]: connection_input: conn=1 deferring
operation: binding
Apr 11 15:14:50 cliff slapd[15355]: conn=1 op=36641 BIND anonymous
mech=implicit ssf=0
Apr 11 15:14:50 cliff slapd[15355]: conn=1 op=36641 BIND dn="" method=128
Apr 11 15:14:50 cliff slapd[15355]: conn=1 op=36641 RESULT tag=97 err=0 text=
It appears to my untrained eye that the operation both before and
after the deferral completed successfully. Any idea what type of
client behavior could trigger messages like this?
-Ben