Hello openldap community,
I have openldap 2.4.6 running on 2 machines.
one master server with a BDB database acting as the syncrepl provider (the syncrep[l overlay has been added to the database configuration directive).
I now have set up a second machine also running openldap 2.4.6 and I've been playing around with it trying to get it to act as a syncrepl consumer.
I remember reading somewhere in the openldap documentation that it should be fairly straight forward with a simple 10-12 line LDIF file to get the synrepl consumer synched up with the provider.
Can someone please post an example of such a simple kickstart file?
Thanks ^6,
Scott
On Monday 19 November 2007 20:38:45 Scott Classen wrote:
Hello openldap community,
I have openldap 2.4.6 running on 2 machines.
one master server with a BDB database acting as the syncrepl provider (the syncrep[l overlay has been added to the database configuration directive).
I now have set up a second machine also running openldap 2.4.6 and I've been playing around with it trying to get it to act as a syncrepl consumer.
I remember reading somewhere in the openldap documentation that it should be fairly straight forward with a simple 10-12 line LDIF file to get the synrepl consumer synched up with the provider.
Uh, if you are using a configuration file (and not back-config, and implying that you want to bootstrap the configuration via sync-repl too), then assuming that your configuration is correct, starting the consumer should result in it doing an initial sync.
Maybe you could provide more details on your configuration if you don't come right.
Regards, Buchan
Scott Classen wrote:
Hello openldap community,
I have openldap 2.4.6 running on 2 machines.
one master server with a BDB database acting as the syncrepl provider (the
syncrep[l overlay has been added to the database configuration directive).
I now have set up a second machine also running openldap 2.4.6 and I've been
playing around with it trying to get it to act as a syncrepl consumer.
I remember reading somewhere in the openldap documentation that it should be
fairly straight forward with a simple 10-12 line LDIF file to get the synrepl consumer synched up with the provider.
Can someone please post an example of such a simple kickstart file? Thanks ^6,
Sounds vaguely like you want this (from http://www.openldap.org/pub/hyc/LDAPcon2007s.pdf page 20)
### dn: cn=config objectclass: olcglobal cn: config
dn: olcdatabase={0}config,cn=config objectclass: olcdatabaseconfig olcdatabase: {0}config olcsyncrepl: rid=001 provider=$URI binddn="cn=config" bindmethod=simple credentials=$CONFIGPW searchbase="cn=config" type=refreshOnly interval=00:00:00:10 ###
Slapadding this will fully initialize a new server if you point it at an existing provider, but of course you need to have the syncprov overlay configured on the config database of the provider.
See test049 in the test suite for a more detailed example.
Howard Chu wrote:
olcsyncrepl: rid=001 provider=$URI binddn="cn=config" bindmethod=simple credentials=$CONFIGPW searchbase="cn=config" type=refreshOnly
Just to make it very clear avoiding confusion. Is this LDIF snippet directly usable? I guess $URI and $CONFIGPW have to be replaced by valid values.
Ciao, Michael.
Michael Ströder wrote:
Howard Chu wrote:
olcsyncrepl: rid=001 provider=$URI binddn="cn=config" bindmethod=simple credentials=$CONFIGPW searchbase="cn=config" type=refreshOnly
Just to make it very clear avoiding confusion. Is this LDIF snippet directly usable? I guess $URI and $CONFIGPW have to be replaced by valid values.
Correct. It's just an example, you have to fill in the proper values yourself. That's why I said to look at test049, which has an actual working config.
openldap-software@openldap.org
-
Buchan Milne -
Howard Chu -
Michael Ströder -
Scott Classen