[Date Prev][Date Next]
Re: LDAP replication using slurpd
- To: openldap-software@OpenLDAP.org
- Subject: Re: LDAP replication using slurpd
- From: Moe <email@example.com>
- Date: Thu, 29 Sep 2005 20:38:23 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=BaO4sxgbAQWm2i0w4Cfsy3pCiQF1mtZp8fJYi42LczbTJluPhuiS0Xjv4w68AbwY1lglzDNf0iLYA5MyEHXAAKsk+6ByUz91hEd3RCXZzC3wd6OiUpKwlUF3Fn1ujS4S5iFT0rPfGKIxEBvSbS1S6200zMjTe0JJARZtFjDT9hU= ;
- In-reply-to: <firstname.lastname@example.org>
yes im getting .rej files.
I have /usr/local/var/openldap-data/replicaion.log defined in my slapd.conf file. This file was always 0 bytes from the begining, never grew. Instead /usr/local/var/openldap-slurp/replica/slurpd.replog is the one that keeps growing. Not sure if this is normal.
which one is the master server's replication.log?
matthew sporleder <email@example.com> wrote:
Are you getting .rej files? Check in your -t tmp directory and make
sure the replication log there is not overwriting the slapd
If slurpd doesn't empty the master server's replication.log, it should
just continue to grow. If you have .rej files, you can try running
slurpd -o -r /path/to/replication.log
On 9/29/05, Moe wrote:
> Hi Everyone,
> Im doing replication between a master LDAP and a slave LDAP. It works fine when master and slave are both online.
> I noticed that when the slave is down for some reason and when it comes up again the changes that were done when the slave was down are not replicated to the slave when it comes up again. Is that how Open LDAP work?. Is there a way to replicate the changes that were made on the master when the slave is online again.
> Yahoo! for Good
> Click here to donate to the Hurricane Katrina relief effort.
Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort.