It means that your syncrep directives are not the good ones i think,
or .
For each DIT you yant to replicate, you need to have :
The syncprov module load:
dn: cn=module{0},cn=config
objectClass: olcModuleList
cn: module{0}
olcModulePath: /usr/lib/ldap
olcModuleLoad: {0}back_hdb
olcModuleLoad: {1}syncprov
One overlay for your DIT :
dn: olcOverlay={0}syncprov,olcDatabase={1}hdb,cn=config
objectClass: olcOverlayConfig
objectClass: olcSyncProvConfig
olcOverlay: {0}syncprov
olcSpCheckpoint: 100 10
olcSpSessionlog: 100
And for the DIT you want to replicate, the syncrepl directives with
the associate olcAccess:
dn: olcDatabase={1}hdb,cn=config
objectClass: olcDatabaseConfig
objectClass: olcHdbConfig
olcDatabase: {1}hdb
olcDbDirectory: /var/lib/ldap
olcSuffix: dc=exemple,dc=com
olcAccess: {0}to attrs=userPassword,shadowLastChange
by dn.exact="cn=ldap01,ou=hosts,dc=exemple,dc=com" read
by dn.exact="cn=ldap02,ou=hosts,dc=exemple,dc=com" read
by anonymous auth
by * none
olcAccess: {2}to
dn.subtree="dc=interne,dc=observatoiredesmarques,dc=fr"
by
dn.exact="cn=ldap1.vm,ou=hosts,dc=interne,dc=observatoiredesmarques,dc=fr"
read
by
dn.exact="cn=ldap2.vm,ou=hosts,dc=interne,dc=observatoiredesmarques,dc=fr"
read
olcSyncrepl: {0}rid=101
provider= "ldap://ldap01.exemple.com/" type=refreshAndPersist
retry="10 30 30 +" searchbase="dc=exemple,dc=com" bindmethod=sasl
saslmech=gssapi //or depending on
which mechanism you use to bind into your LDAP base.
olcSyncrepl: {0}rid=101
provider= "ldap://ldap02.exemple.com/" type=refreshAndPersist
retry="10 30 30 +" searchbase="dc=exemple,dc=com" bindmethod=sasl
saslmech=gssapi
olcSyncrepl: {0}rid=101
provider= "ldap://ldap03.exemple.com/" type=refreshAndPersist
retry="10 30 30 +" searchbase="dc=exemple,dc=com" bindmethod=sasl
saslmech=gssapi
Regards,
Quentin
Le 24/07/2013 20:25, Ludovic Brochard a écrit :
Hello,
I use the 2.4.35
version of openldap.
I have three master
ldap mulit-delta-sync:
ldap01, ldap02
and ldap03.
We import data ldap03 on two others by a copy of the
FileSystem.
Upon restart, the
three seem OK but we have in the logs files 3GB
of message like this:
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Jul 22 20:10:46 ldap02 slapd[31439]: do_syncrep2: rid=992 (4096)
Content Sync Refresh Required
Someone
had an idea of the
problem? Or significatuion of this message
?
Thank you.
--
If the automobile had followed the same development cycle as the
computer, a Rolls-Royce would today cost $100, get a million
miles per gallon, and explode once a year, killing everyone
inside.
Robert X. Cringely, InfoWorld magazine
|