[389-devel] 300s delay when query cn=monitor
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