Re: Replication issue? Data is different between master and consumer with same entryCSNs

[Dave Steiner <steiner@rutgers.edu>]

On 9/6/2018 2:48 PM, Quanah Gibson-Mount wrote:
> --On Wednesday, September 05, 2018 5:49 PM -0400 Dave Steiner 
> <steiner@rutgers.edu> wrote:
>
> Hi Dave,
>
>
> > $ ldapsearch ... -H ldap://ldapmaster.rutgers.edu uid=XXXX postalAddress
> > createTimestamp modifyTimestamp entryCSN
> >  dn: uid=XXXX,ou=People,dc=rutgers,dc=edu
> >  createTimestamp: 20121220100700Z
> >  postalAddress: Business And Science Bldg$227 Penn Street$Camden, NJ
> > 081021656
> >  entryCSN: 20180505002024.083133Z#000000#001#000000
> >  modifyTimestamp: 20180505002024Z
> >
> > $ ldapsearch ... -H ldap://ldapconsumer3.rutgers.edu uid=XXXX
> > postalAddress createTimestamp modifyTimestamp entryCSN
> >  dn: uid=XXXX,ou=People,dc=rutgers,dc=edu
> >  createTimestamp: 20121220100700Z
> >  postalAddress: BUSINESS AND SCIENCE BLDG$227 PENN STREET$CAMDEN, NJ
> > 081021656
> >  entryCSN: 20180505002024.083133Z#000000#001#000000
> >  modifyTimestamp: 20180505002024Z
>
> Those entries appear identical to me. I assume you believe they are not 
> identical because the case doesn't match.  However, postalAddress uses 
> caseIgnore normalization rules, so they are in fact identical as far as LDAP 
> is concerned.
>
> Also, given the entry was created in 2012 and there's no indication of when 
> the postalAddress attribute was modified, it's impossible to determine 
> when/how the divergence in capitalization occurred.  You also don't provide 
> any information about the underlying database in use, which could be very 
> relevant, history wise.

Ok, bad example... Here's another example that's rather different:

$ searchn -H ldap://ldapmaster.rutgers.edu uid=XXXX mail createTimestamp 
modifyTimestamp entryCSN
dn: uid=XXXX,ou=People,dc=rutgers,dc=edu
createTimestamp: 20180504140010Z
mail: xxxxxxxxx.xxxx@rutgers.edu
entryCSN: 20180831205041.549496Z#000000#001#000000
modifyTimestamp: 20180831205041Z

$ searchn -H ldap://ldapconsumer1.rutgers.edu uid=XXXX mail createTimestamp 
modifyTimestamp entryCSN
dn: uid=XXXX,ou=People,dc=rutgers,dc=edu
createTimestamp: 20180504140010Z
mail: yyyyy@rutgers.edu
entryCSN: 20180831205041.549496Z#000000#001#000000
modifyTimestamp: 20180831205041Z


> > So I'm trying to figure out why this happens (config issue, bug, ???) and
> > second, if I can't use the contextCSN to report that everything is fine,
> > what else can I do besides trying to compare ldif dumps.
>
> So far, everything appears fine from a technical standpoint (the values match 
> per LDAP SYNTAX rules).
>
> I would suggest the following if you would like the case to match:
>
> dn: ...
> changetype: modify
> replace: postalAddress
> postalAddress: ...
>
> That should correct the value on the providers and consumers to match case.
>
> Warm regards,
> Quanah
>
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.symas.com&amp;data=02%7C01%7Csteiner%40oit.rutgers.edu%7Ca13f8a75c55b4fdbdb6308d614294c60%7Cb92d2b234d35447093ff69aca6632ffe%7C1%7C0%7C636718564940835797&amp;sdata=pVe%2FLnPDf4Civ13qlr1pXPCb0icy%2BzTZUEAcnViaTCo%3D&amp;reserved=0>