On 25.04.2019 23:44, mauzi wrote:
>
> I wrote a simple test program that does ldap_search() calls in endless
> loop with 1 second delay in between. This should run practically forever
> with no timeout.
>
> The program runs as expected, but then it exits suddenly. NDSTRACE
> output shows an unbind on server side:
>
> 2644252416 LDAP: DEBUG: DoSearch on connection 0xfbd1110
> 2644252416 LDAP: DEBUG: Search request:
> base: "o=SomeContext"
> scope:2 dereference:0 sizelimit:0 timelimit:0 attrsonly:0
> filter: "(cn=username)"
> attribute: "mailQuotaStorage"
> 2644252416 LDAP: DEBUG: Sending search result entry
> "cn=username,o=SomeContext" to connection 0xfbd1110
> 2644252416 LDAP: INFO: Sending operation result 0:"":"" to connection
> 0xfbd1110
> 2630670080 LDAP: DEBUG: DoUnbind on connection 0xfbd1110
> 2630670080 LDAP: INFO: Connection 0xfbd1110 closed
>
> Notice that this always occurs at the same second, eg. 11:39:24,
> 11:40:24, 11:41:24, etc.
> What the hell triggers the unbind call and why?
>
>

May sound odd, but a cron job every minute doing NLDAP -U / NLDAP -L? ;)

--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de