Re: N-way replication "dn_callback : entries have identical CSN"

["Jonathan Clarke" <jclarke@linagora.com>]

Le Mer 18 février 2009 09:24, Adrien Futschik a écrit :
> I then switched to OpenLDAP 2.4.14 and did not have the problem anymore
> (same
> configuration). I guess this was a bug form 2.4.11.
>
> Still, I had a few of theses messages in the log :
> conn=9 op=1 => bdb_dn2id_add
> dn="cn=M2client2@laposte.net,ou=clients,o=edf,c=fr" ID=0xb: put failed:
> DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock -30995
>
> but I also got a few of theses :
> dn_callback : entries have identical CSN
> cn=M2client20@laposte.net,ou=clients,o=edf,c=fr
> 20090217155418.854085Z#000000#002#000000
> syncrepl_entry: rid=004 be_search (0)
> syncrepl_entry: rid=004 cn=M2client20@laposte.net,ou=clients,o=edf,c=fr
> syncrepl_entry: rid=004 entry unchanged, ignored
> (cn=M2client20@laposte.net,ou=clients,o=edf,c=fr)
> do_syncrep2: cookie=rid=004,sid=002
> syncrepl_entry: rid=004 LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_ADD)
>
> Can anyone explain to me why ? is this normal ?
> The dn_callback message comes from the master log-file where
> "cn=M2client20@laposte.net,ou=clients,o=edf,c=fr" was inserted.

I don't know about the DB_LOCK_DEADLOCK message, but "entries have
identical CSN" means that your syncrepl consumer received an entry that is
identical to one already present in your DB.

This may happen when resynching a database, or it could be that your
multi-master setup is causing each server to feed updates back to itself.
Make sure the URLs in your syncrepl declarations match the listener URLs
to slapd (-h option).

Jonathan