We are also in the process of migrating from OpenLDAP 2.0.x to 2.2.x.
So far we haven't been able to replicate properly from a 2.0.x master to
a 2.2.x slave. we had problem especially when creating new entries. We
had to build a whole new 2.2.x platform and test it before migrating
from the old platform to the new one.
Sam
On Fri, 2005-01-07 at 14:33, John Morris wrote:
> Hi,
>
> I've just upgraded one of my slave ldap servers to 2.2.13. When copying
> the database over in LDIF format using slapcat/slapadd, the 2.2 slapadd
> complained about syntax errors. The problem was that the syntax of the
> DN of the ModifiersName changed: the old format for GSSAPI DNs was
> "uid=kerb/princ + realm=REALM.COM", and the new format is
> "uid=kerb/princ,cn=realm.com,cn=gssapi,cn=auth". Simply changing the
> format in the LDIF file stopped slapadd's complaints, and the slave
> server is now working, except:
>
> It now appears that the same problem is occurring with slurpd updates.
> The master server, running 2.0.27, is sending the ModifiersName with the
> old syntax. The new slave server of course complains in the .rej file,
> "ERROR: invalid syntax".
>
> How can I fix this without having to upgrade the master server and the
> other slave servers on the network? Is it possible to get slurpd to
> stop sending the ModifiersName? Or is it possible to change the syntax
> of the ModifiersName to accept the old format?
>
> Thank you for any feedback.
>
> John
>
>
> >From the .rej file:
>
> ERROR: Invalid syntax
> replica: ldap-3.foo.com:389
> time: 1105124212.0
> dn: dc=ns,dc=foo.com,ou=pdns,o=foo
> changetype: modify
> replace: tXTRecord
> tXTRecord: test
> -
> replace: modifiersName
> modifiersName: uid=bar/admin + realm=FOO.COM
> -
> replace: modifyTimestamp
> modifyTimestamp: 20050107185652Z
> -