[389-devel] Re: 300s delay when query cn=monitor

2021-07-15 Thread Erwin Weitlaner
After further log file analysis I found the blocking ldap query ... it is a BIND request (which is successfull) and a missing CLOSE afterwards. After 5 minutes the LDAP Server closes the connection with closetype="T2" (server side timeout). So far so good (client problem I will fix). I am not

[389-devel] Re: 300s delay when query cn=monitor

2021-07-12 Thread Erwin Weitlaner
Thank you Thierry for your support. So I will try to get the thread dump .. If the problem comes with a connection timeout from a (not listening) client, shoudn´t I see an error log entry somewhere? I searched for that for hours but no hints .. Maybe not the right idea but the problem came

[389-devel] 300s delay when query cn=monitor

2021-07-09 Thread Erwin Weitlaner
We are using 389-Directory/1.3.10.2 B2021.127.856 (we will update next month) .. a monitor script queries with basedn cn=monitor and filter (objectClass=*) every minute. This query returned in <10ms for years. Since two weeks under unknown circumstances this query lasts up to 300s (one or two