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

Re: (ITS#4809) Replication of operational attributes when performing modrdn operation

Thomas.Fritz@bam.de wrote:
> Full_Name: Thomas Fritz
> Version: 2.3.33
> OS: Debian Gnu/Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (
> We are using OpenLDAP 2.3.33 in a master/slave setup with slurpd and hdb
> backend.
> When performing the modrdn operation against the master, no update directives
> for the attributes 'modifiersName', 'modifyTimestamp', and 'entryCSN' are
> written to the replog file. Hence, the databases of master and slave differ by
> the values of these attributes after replication.
> This bug can be reproduced using e.g. the ldapmodrdn tool. OpenLDAP versions
> back to (at least) 2.3.24 are affected.

This is not a bug, it is a consequence of the design of slurpd. slurpd uses 
LDIF (RFC2849) for its replog format, and simply propagates LDAP operations 
as recorded there. In LDIF a modrdn record can only specify newrdn, 
deleteoldrdn, and newsuperior parameters. Likewise, these are the only 
parameters that can be specified in an LDAP modrdn operation. This design 
limitation is one of many reasons why slurpd has been deprecated.

If you want to perform replication and preserve these attributes, you can use 
syncrepl instead.
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc
   OpenLDAP Core Team            http://www.openldap.org/project/