Re: synrcrepl "be_modify failed (80)"

[Pierangelo Masarati <ando@sys-net.it>]

Emmanuel Dreyfus wrote:
> > From time to time, syncrepl breaks on the replica, with this in the
> logs:
>
> slapd[1737]: null_callback : error code 0x50 
> slapd[1737]: syncrepl_entry: rid=017 be_modify failed (80) 
> slapd[1737]: do_syncrepl: rid=017 retrying 
>
> code 80 is LDAP_OTHER, which is not very insightful. The only way to get
> syncrepl working again is to wipe out the database and restart slapd.
>
> Being out of sync is not very pleasant, but there is worse: when several
> replicas are harassing the master with syncrepl requests, it tends to
> die horribly, with stuff like this:
>
> 1) assertion "c->c_conn_state == SLAP_C_CLOSING" failed: file
> "connection.c", line  787, function "connection_close"
>
> 2) assertion "c->c_struct_state == SLAP_C_USED" failed: file
> "connection.c", line 680, function "connection_state_closing"
>
> 3) slapd: Error detected by libpthread: Invalid mutex. Detected by file
> "/home/builds/ab/netbsd-4/src/lib/libpthread/pthread_mutex.c",  line
> 295, function "pthread_mutex_trylock".
>
> I end up with a hung slapd, that I can only get rid of with a kill -9.
>
> All of this happens with 2.4.13. Are these known bugs?

Not sure about the reason of the LDAP_OTHER issue, but the connection 
issue is probably known, and fixed in re24.  Can you try with a fresh 
checkout?

p.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Fax:     +39 0382 476497
Email:   ando@sys-net.it
-----------------------------------