Re: (ITS#5160) syncrepl of glued and syncrepl'd databases causes unwanted deletes on the end consumer

[hyc@symas.com]

jclarke@linagora.com wrote:
> I have tested this on both 2.3.38 and HEAD (same version on all 3 servers), and
> behaviour is quite different, though the end result is the same.

Due to multiple limitations, this is not expected to work in 2.3 at all.

> On HEAD, things are quite different:
> request done: ld 0x82c2228 msgid 2
> do_syncrep2: rid=7 LDAP_RES_SEARCH_RESULT
> nonpresent_callback: rid=7 got UUID b5797e8c-0486-102c-83e0-79137da6179f, dn
> dc=ossa,dc=linagora,dc=org
> nonpresent_callback: rid=7 got UUID b5a2f834-0486-102c-83e1-79137da6179f, dn
> uid=root,dc=ossa,dc=linagora,dc=org
> nonpresent_callback: rid=7 got UUID b5a31526-0486-102c-83e2-79137da6179f, dn
> uid=replicator,dc=ossa,dc=linagora,dc=org
> adresse de be_modify : 80c8840
> null_callback : error code 0x32
> syncrepl_updateCookie: rid=7 be_modify failed (50)

This is Insufficient Access. You have not configured the glue databases with 
identical rootDN's, which is clearly documented as a requirement for glued databases.
-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/