Full_Name: Rein Tollevik
Version: CVS head
OS: Linux 2.6
Submission from: (NULL) (184.108.40.206)
Submitted by: rein
connection_client_setup() enables the connection for events twice, causing race
conditions that can create deadlock situations. Ref:
A fix that removes the unnecessary call to slapd_set_read() will be committed
--On Tuesday, September 23, 2008 2:32 PM +0000 sylvain.thomas(a)gmail.com
> I can provide a detailed log (loglevel -1) and any other information
> required. The environment and the configuration files are the same as for
> ITS 5661, but I do not use the mirror mode.
> Thanks for your help
(a) reproduce with the current RE24 source?
(b) Can you provide your slapd.conf files?
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration
Full_Name: Pavlos Parissis
OS: Linux 2.6 RH AE 4.6
Submission from: (NULL) (220.127.116.11)
During performance testing with SLAMD we noticed the dncache exceeds the limit.
As a result the system starts to swap a lot and the responses of slapd are very
Here are the facts:
# ldapsearch -x -D "cn=xxxx" -w xx -b 'cn=database 2,cn=databases,cn=monitor' -s
sub '(objectclass=*)' '*' '+' | grep -i Cache
olmBDBDNCache: 482001 <<==========
# slapd -V
@(#) $OpenLDAP: slapd 2.4.11 (Sep 11 2008 10:58:58) $
Berkeley DB 4.6.21: (September 27, 2007)
# uname -r
# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 4 (Nahant Update 6)
Full_Name: Quanah Gibson-Mount
Submission from: (NULL) (18.104.22.168)
The behavior of the dncachesize setting when it is not ideal (2x) is not
The DN cache is allowed to temporarily grow beyond the configured size. It does
this if many entries are locked when it tries to do a purge, because that means
they're legitimately in use. Also the dn cache never purges entries that have
cached children, so depending on the shape of the DIT, it could have lots over
the defined limit.
This would be useful to note in the slapd-bdb & slapd-hdb man pages.