Re: syncRepl fails to replicate new trees (ITS#2948)

[jongchoi@OpenLDAP.org]

Quanah,

> I understand about being on vacation -- It is a wonderful thing to do.

Oh, I'm not on vacation, but attending a conference.
 
> Here is the path that I took:
> 
> 1) strip DB of entryUUID & entryCSN
> 
> 2) Load DB on provider (with -p -w -l)
> 
> 3) slapcat -m -l DB
> 
> 4) Copy provider generated DB to replica
> 
> 5) slapadd -r -l DB
> 
> So all entryUUID, entryCSN pieces should match.
> 
> I note:
> 
> diff -u db_syncrepl_m db_syncrepl_r
> 
> returns:
> 
> ldap-dev2:/# diff -u db_syncrepl_m db_syncrepl_r
> --- db_syncrepl_m       2004-03-04 10:46:09.000000000 -0800
> +++ db_syncrepl_r       2004-03-04 10:44:39.000000000 -0800
> @@ -15676214,12 +15676214,12 @@
>  entryUUID: 2b3126fc-01c5-1028-8bd9-8075041b1e70
>  entryCSN: 20040304011528Z#0000b4#00#000000
> 
> -dn: cn=ldapsync,dc=stanford,dc=edu
> +dn: cn=syncrepl0,dc=stanford,dc=edu
>  objectClass: top
>  objectClass: subentry
> -objectClass: syncProviderSubentry
> +objectClass: syncConsumerSubentry
>  structuralObjectClass: subentry
> -cn: ldapsync
> -contextCSN: 20040304011528Z#0000b4#00#000000
> +cn: syncrepl0
> +syncreplCookie: 20040304011528Z#0000b4#00#000000
>  subtreeSpecification: {}
> 
> 
> Where db_syncrepl_m is a slapcat -m -l on the provider, and db_syncrepl_r 
> is a slapcat -k -l on the replica.  So in my 481MB database dump, the only 
> things that differ are the syncrepl0/ldapsync entries.

You took the right path.
 
> It has gone from a point of where it partially worked in 2.2.5 to a point 
> where I get no updates propagating in 2.2.6.  I don't see anything 
> spectacular about my configuration, I know that the syncrepl connection is 
> being made between the provider and replica, and that the replica has full 
> read on the master.  That tends to indicate to me that it isn't functional.
> 
> --Quanah

I'm looking at the difference between the two. Will be back asap.

- Jong-Hyuk