Hi,
I would suspect the dump of the opened connections status to be the RC
of that delay. If the monitor thread can not acquire the connection
lock, it will delay the request. So I would suspect a connection timeout
(5min) to hang the monitoring thread, for example if a ldapclient is not
reading while the server tries to send it some data.
As it is hanging for 5min, when it occurs you may run a pstack showing
what the threads are doing.
regards
thierry
On 7/9/21 11:51 AM, Erwin Weitlaner wrote:
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 times per day). The other queries work fine (no delay). Any ideas what could block the answer?
SG erwin
The 'bad' log entry:
[09/Jul/2021:06:54:01.203812923 +0200] conn=962307 SRCH type=srch op=1 base="cn=monitor" scope=2 filter="(objectClass=*)" attrs="ALL" RESULT op=1 err=0 errname=success tag=101 nentries=3 optime=250.179697410 wtime=0.000062324 etime=250.179757740 CONNECTION fd=4201 slot=4201 from=127.0.0.1 to=127.0.0.1 ssl=false binddn="cn=directory manager" method=128 version=3 op=1
The 'normal' log entry:
[09/Jul/2021:06:52:01.797036360 +0200] conn=962222 SRCH type=srch op=1 base="cn=monitor" scope=2 filter="(objectClass=*)" attrs="ALL" RESULT op=1 err=0 errname=success tag=101 nentries=3 optime=0.002609889 wtime=0.000057307 etime=0.002665406 CONNECTION fd=4199 slot=4199 from=127.0.0.1 to=127.0.0.1 ssl=false binddn="cn=directory manager" method=128 version=3 op=1
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
