[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4916) syncrpl consumer not listing contextcsn as operation attr

brian@zimbra.com wrote:
> Full_Name: Brian Peterson
> Version: 2.3.34
> OS: Linux
> URL: pro
> Submission from: (NULL) (
> When setup sync replication the contextCSN is available via ldapsearch on the
> provider but not the consumer as an operation attribute.  If we do a slapcat on
> the consumer the resulting ldif contains the contextCSN.

This is because your context entry has no DN, it's a glue entry. When 
you do a search on it you get the contents of the server rootDSE instead 
of your glue entry. The search works on the provider because the 
syncprov overlay intercepts searches to insert the current contextCSN 
value in the result. You can add a syncprov overlay to the consumer to 
get the same effect.

> Top entry from slapcat ldif on the consumer.
> dn:
> objectClass: glue
> structuralObjectClass: glue
> contextCSN: 20070405182202Z#000000#00#000000
> entryCSN: 20070405182202Z#000000#00#000000
> modifiersName: uid=zimbra,cn=admins,cn=zimbra
> modifyTimestamp: 20070405182202Z

   -- 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/