On 11-09-22 10:09 PM, Daniel Qian wrote:
On 11-09-22 9:37 PM, Brett @Google wrote:
you need to add the syncrepl overlay to the backend containing your replication source data, to make it syncrepl aware.
On Fri, Sep 23, 2011 at 10:30 AM, Daniel Qian <daniel@up247solution.com mailto:daniel@up247solution.com> wrote:
On 11-09-22 7:37 PM, Howard Chu wrote: Daniel Qian wrote: The problem direction has the same syncrepl configuration as the working one except for the rid and provider name:I am not sure what you mean by "add the syncrepl to the backend". The two nodes have pretty much the same configuration for the backend containing the replicated data but the question is why one is working and the other one is not.
[root@localhost cn=config]# ldapsearch -LLL -b cn=config -D cn=admin,cn=config -W -ZZ -h ldaprov2.prod olcDatabase={1}bdb > /root/ldaprov2.ldif Enter LDAP Password:
[root@localhost cn=config]# ldapsearch -LLL -b cn=config -D cn=admin,cn=config -W -ZZ -h ldaprov1.prod olcDatabase={1}bdb > /root/ldaprov1.ldif Enter LDAP Password:
[root@localhost cn=config]# !diff diff /root/ldaprov1.ldif /root/ldaprov2.ldif 18c18
< olcRootPW: {SSHA}/2ht......................
olcRootPW: {SSHA}lfxH.....................
20c20 < olcSyncrepl: {0}rid=102 provider="ldap://ldaprov2.prod:389/" type=refreshAndP
olcSyncrepl: {0}rid=202 provider="ldap://ldaprov1.prod:389/"
type=refreshAndP
above lines are the only difference of the backend configurations in the two nodes.
Thanks, Daniel
Actually I was missing a component on the second node. This fixed the problem:
[root@localhost cn=config]# ldapadd -W -D cn=admin,cn=config <<EOF dn: olcOverlay={0}syncprov,olcDatabase={1}bdb,cn=config objectClass: olcOverlayConfig objectClass: olcConfig objectClass: top objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpCheckpoint: 100 10 EOF Enter LDAP Password: adding new entry "olcOverlay={0}syncprov,olcDatabase={1}bdb,cn=config"
Thanks for the help Daniel