thanks for answer
Am 15.06.2018 um 22:15 schrieb David Boreham:
On 6/15/2018 2:04 PM, Jan Kowalsky wrote:
> What I can see are a log of unindexec component queries, most of them
> [15/Jun/2018:21:51:14 +0200] conn=462 op=31251 SRCH
> base="ou=Domains,dc=example,dc=org" scope=2
> attrs="associatedDomain inetDomainBaseDN"
> [15/Jun/2018:21:51:14 +0200] conn=462 op=31251 RESULT err=0 tag=101
> nentries=1 etime=0 notes=U
The "etime=0" implies that this is not the operation you are looking for.
The maximum I ever had was etime=4
[15/Jun/2018:20:22:43 +0200] conn=95644 op=17 SRCH
et))" attrs="entryuuid nsUniqueId objectguid guid ipauniqueid
distinguishedName uid samaccountname memberOf dknOwncloudQuota mail
mail jpegPhoto thu
[15/Jun/2018:20:22:47 +0200] conn=95644 op=17 RESULT err=0 tag=101
And they result from nexcloud query with a lot of base dns configured...
Looking back at your original question, I am wondering : when you
that some searches are very slow do you mean "searches with certain
properties in terms of filter and so on" or do you mean " for the exact
same kind of search, submitted over and over, some responses are very
slow but most are very fast"?
The latter. The same queries are sometimes fast and hang some times.