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

Hello,

that is excellent news. The server was trying to read an operation for
5min then timeout (ioblock_timeout), I am a bit surprised it detected
incoming event but nothing to read. Anyway in such situation the
connection is locked and this  explains why cn=monitor was hanging.

best regards
thierry

On 7/15/21 2:49 PM, Erwin Weitlaner wrote:
> 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 sure if this situation blocked the cn=monitor query in earlier versions, I guess not?!
>
> Once again thank you for your help.
>
> Finally the log of the blocking connection
>
> 2021-07-15 10:22:42 +02:00
> pldaXXX [15/Jul/2021:10:22:42.916319196 +0200] conn=1228488 CLOSE type=close fd=4751 slot=4751 from=10.XXX.YYY.ZZZ to=10.AA.BB.CCC ssl=true binddn="gvgid=at:lX:yyyyy,ou=service,dc=ttttt+gvouid=at:l7:lvn:000001,dc=gv,dc=at" method=128 version=3 op=0 totalop=-1 closestate=normal closetype="T2"
> 2021-07-15 10:17:41 +02:00
> pldaXXX [15/Jul/2021:10:17:41.893466169 +0200] conn=1228488 BIND type=bind op=0 binddn="gvgid=at:lX:yyyyy,ou=service,dc=ttttt+gvouid=at:l7:lvn:000001,dc=gv,dc=at" method=128 version=3 RESULT op=0 err=0 errname=success tag=97 nentries=0 optime=0.000512268 wtime=0.041730272 etime=0.042240973 resultdn="gvgid=at:lX:yyyyy,ou=service,dc=ttttt+gvouid=at:l7:lvn:000001,dc=gv,dc=at" CONNECTION fd=4751 slot=4751 from=10.XXX.YYY.ZZZ to=10.AA.BB.CCC ssl=true binddn="gvgid=at:lX:yyyyy,ou=service,dc=ttttt+gvouid=at:l7:lvn:000001,dc=gv,dc=at" method=128 version=3 op=0
> 2021-07-15 10:17:41 +02:00
> pldaXXX [15/Jul/2021:10:17:41.850130533 +0200] conn=1228488 OPEN type=open fd=4751 slot=4751 from=10.XXX.YYY.ZZZ to=10.AA.BB.CCC ssl=true
> _______________________________________________
> 389-devel mailing list -- 389-devel@lists.fedoraproject.org
> To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure