Re: After few seconds slapd automatically closes connection. Why?

To: Saša-Stjepan Bakša <ssbaksa@gmail.com>, "openldap-technical@openldap.org" <openldap-technical@openldap.org>

Subject: Re: After few seconds slapd automatically closes connection. Why?

From: Frank Swasey <Frank.Swasey@uvm.edu>

Date: Fri, 17 Feb 2017 13:21:13 +0000

Accept-language: en-US

Content-language: en-US

In-reply-to: <CANk+c=0bWAS2z5U8VFEEon+BmrNqtbuwTdeVeYSsX5tyGXc8Ww@mail.gmail.com>

References: <CANk+c=0bWAS2z5U8VFEEon+BmrNqtbuwTdeVeYSsX5tyGXc8Ww@mail.gmail.com>

Thread-index: AQHSiR4z+aZEndDu/ke5DWQiD6dVbKFtLy+A

Thread-topic: After few seconds slapd automatically closes connection. Why?

Do you run the server as well as the client, or only the client? What version of OpenLDAP are you using? What is the value assigned to idletimeout in the OpenLDAP configuration?

On 2/17/17, 08:00, "openldap-technical on behalf of Saša-Stjepan Bakša" <openldap-technical-bounces@openldap.org on behalf of ssbaksa@gmail.com> wrote:

After successful bind and some search actions my client is still bind to server but as I can see from trace few seconds after successful operation slapd shuts down connection. Why is that happening? Can I prevent it? We have monitoring in our software which find that as server down and lots of logs are generated.

229 1786.027248821 172.17.103.226 -> 10.50.200.191 LDAP 294 searchResEntry(49) "cn=config"
230 1786.027396894 172.17.103.226 -> 10.50.200.191 LDAP 68 searchResDone(49) success
231 1786.028152406 10.50.200.191 -> 172.17.103.226 TCP 60 56375 > ldap [ACK] Seq=576 Ack=130237 Win=65280 Len=0
232 1798.039843259 172.17.103.226 -> 10.50.200.191 TCP 54 ldap > 56375 [FIN, ACK] Seq=130237 Ack=576 Win=30336 Len=0
233 1798.042231511 10.50.200.191 -> 172.17.103.226 TCP 60 56375 > ldap [ACK] Seq=576 Ack=130238 Win=65280 Len=0

Sasa