The module does not UNBIND when closing connections

[awvinson]

An example connection string, notice the (connection lost) at the end. If the module performed an UNBIND operation, we would not receive this error.

Nov 3 12:07:37 y slapd[11164]: conn=1037 fd=25 ACCEPT from IP=x.x.x.x:35998 (IP=z.z.z.z:636)
Nov 3 12:07:37 y slapd[11164]: conn=1037 fd=25 TLS established tls_ssf=256 ssf=256
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=0 BIND dn="" method=128
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=0 RESULT tag=97 err=0 text=
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=1 SRCH base="" scope=0 deref=2 filter="(objectClass=)"
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=1 SRCH attr=namingcontexts
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text=
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=2 SRCH base="dc=x,dc=gov" scope=0 deref=2 filter="(objectClass=)"
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=2 SRCH attr=contextCSN
Nov 3 12:07:37 y slapd[11164]: conn=1037 op=2 SEARCH RESULT tag=101 err=0 nentries=1 text=

++++. UNBIND should happen here ++++++

Nov 3 12:07:37 y slapd[11164]: conn=1037 fd=25 closed (connection lost)

[coudot]

Hello,

could you tell us which script is concerned?

[awvinson]

Apologies, that was silly of me to leave out.

check_ldap_syncrepl_status.pl