Hello.
I'm facing heavy ldap locking again, even after upgrading bdb 4.6 to latest patch level (4.6.21.3). When the problem occurs, any ldap query fails with this result:
[root@etoile main]# ldapsearch -x ldapsearch: error.c:272: ldap_parse_result: Assertion `r != ((void *)0)' failed. Abandon
gdb shows 18 active thread, apparently waiting a lock release (see bt and bt full output attached). I'm also joing output of db_stat -m and -c output.
The only suspect trace I found in the log was some strange queries from an apparently wrongly host, such as: Apr 14 06:57:09 etoile slapd[24528]: conn=61313 op=2 SRCH base="dc=msr-inria,dc=inria,dc=fr" scope=2 deref=0 filter="(&(objectClass=posixAccount)(objectClass=posixAccount)(uid=<!--))" But I suffered from this kind of lockup before it was installed. I wonder however of the potential impact of such kind of queries, using exotic characters.
I'm using openldap 2.4.15 on linux 32 bits.
Beyond the problematic lockup, why does the client abort, instead of trying the slave server when the first one fails ? Here is my ldap.conf configuration file.
BASE dc=msr-inria,dc=inria,dc=fr URI ldap://ldap1.msr-inria.inria.fr ldap://ldap2.msr-inria.inria.fr TLS_CACERTDIR /etc/pki/tls/certs TLS_REQCERT demand NETWORK_TIMEOUT 2 TIMEOUT 2 TIMELIMIT 2