-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I tried to setup replication on two ldap servers : a master and a slave.
The master is configured like this (slapd.conf) :
database hdb
suffix "dc=test,dc=fr" rootdn "cn=root,dc=test,dc=fr"
[...]
overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100
The slave is configured like this (slapd.conf). I tried to make a very simple setup :
syncrepl rid=001 provider=ldap://my-master:389/ searchbase="dc=test,dc=fr" bindmethod=simple binddn="cn=root,dc=test,dc=fr" credentials=password type=refreshAndPersist retry="5 +"
When I restart my slave I got this error in logfiles :
Sep 24 11:08:37 kyo slapd[2296]: syncrepl_message_to_entry: rid=001 mods check (postalAddress: value #0 provided more than once)
And replication stops.
Master and slaves are installed from debian squeeze packages :
root@kyo:/var/lib/ldap# slapd -V @(#) $OpenLDAP: slapd 2.4.23 (Sep 13 2010 07:04:08) $ @borges:/home/devel/openldap/trunk/debian/build/servers/slapd
libbdb version is 4.8.30.
Replication works well with a 2.3.20 slave, so i think i missed something on 2.4.23 slave configuration.
Thanks for your help,
- -- Nicolas Greneche - RSSI et Sysadmin Centre de Ressources Informatiques (CRI) Doctorant au sein du projet SDS - www.sds-project.fr Mail : nicolas.greneche_(at)_univ-orleans.fr GPG : http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5FEBD0EF
Universite d'Orleans Web : http://blog.garnett.fr Batiment 3IA - 2e etage Tel : 02 38 49 25 26 6 rue Leonard de Vinci BP 6102 45061 ORLEANS Cedex 2
--On Friday, September 24, 2010 11:33 AM +0200 Nicolas Greneche nicolas.greneche@univ-orleans.fr wrote:
Sep 24 11:08:37 kyo slapd[2296]: syncrepl_message_to_entry: rid=001 mods check (postalAddress: value #0 provided more than once)
Sounds like you have bad data in your database that 2.4 catches and 2.3 doesn't.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Le 24/09/2010 18:23, Quanah Gibson-Mount a écrit :
--On Friday, September 24, 2010 11:33 AM +0200 Nicolas Greneche nicolas.greneche@univ-orleans.fr wrote:
Sep 24 11:08:37 kyo slapd[2296]: syncrepl_message_to_entry: rid=001 mods check (postalAddress: value #0 provided more than once)
Sounds like you have bad data in your database that 2.4 catches and 2.3 doesn't.
I got it, I've looked for the record that freeze replication. I've got something like this :
postalAddress: xxxXXXxxx postalAddress: XXxxxxxxX
The same postalAddress value with different case. I added 'schemachecking off' on the replica without any success :
syncrepl rid=001 provider=ldap://my-master:389/ searchbase="dc=test,dc=fr" bindmethod=simple binddn="cn=root,dc=test,dc=fr" credentials=password schemachecking=off type=refreshAndPersist retry="5 +"
Replication process blocks on the same entry.
I've done a slapcat of the master, removed one postalAddress, slapadd and restart replica : the entry is relicated with success (then it locks to another one and I can't modify LDAP directory feeding process).
Why slapadd succeds whereas replication with schema checking disabled fails ?
Do you have any suggestions to make replication works without removing duplicate postalAddress entries ?
Thanks,
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
- -- Nicolas Greneche - RSSI et Sysadmin Centre de Ressources Informatiques (CRI) Doctorant au sein du projet SDS - www.sds-project.fr Mail : nicolas.greneche_(at)_univ-orleans.fr GPG : http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5FEBD0EF
Universite d'Orleans Web : http://blog.garnett.fr Batiment 3IA - 2e etage Tel : 02 38 49 25 26 6 rue Leonard de Vinci BP 6102 45061 ORLEANS Cedex 2
--On Tuesday, September 28, 2010 10:15 AM +0200 Nicolas Greneche nicolas.greneche@univ-orleans.fr wrote:
I've done a slapcat of the master, removed one postalAddress, slapadd and restart replica : the entry is relicated with success (then it locks to another one and I can't modify LDAP directory feeding process).
Why slapadd succeds whereas replication with schema checking disabled fails ?
As documented, slapadd is not as rigorous in its data checking as ldapadd or replication.
Do you have any suggestions to make replication works without removing duplicate postalAddress entries ?
No. You need to fix your broken data.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
Nicolas Greneche -
Quanah Gibson-Mount