The master's replication log (openldap-data/replication.log) is "slurp"-ed by slurpd, which is why it appears to never grow. At one time, it had all the stuff that's in slurp/replica/slurpd.replog. Look at your .rej files to figure out why your entries are being rejected.
On 9/29/05, Moe <[EMAIL PROTECTED]> wrote: > 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? > > Thanks > > Moe > > matthew sporleder <[EMAIL PROTECTED]> wrote: > Are you getting .rej files? Check in your -t tmp directory and make > sure the replication log there is not overwriting the slapd > replication log. > > 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. > > > > Regards, > > > > Moe > > > > > > --------------------------------- > > 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. >
