[Date Prev][Date Next]
Re: reprocessing rejected replica entries
Slurpd will consume the file as it goes through it.
If you end up with a .rej after processing the .rej, then your run
didn't work and you'll have to investigate further.
On 1/23/06, Angel L. Mateo <firstname.lastname@example.org> wrote:
> I am using openldap 2.2.23 and I have a master and a slave server with
> the same configuration. I have the same two backends in both nodes. But
> I had a problem with the replication.
> For some reason (I have to investigate it) the master server had a
> problem adding some entries in the slave one. So it created a .rej file
> describing the problem. I thought this file was reprocessed
> automatically by slurpd so I didn't do anything when I found it, but it
> seems it doesn't, because after some days the updates weren't completed.
> So now, I have run slurpd in one-shot mode indicating with -r option
> the .rej file and the updates were completed.
> My question is: is there any way to reprocess slurpd without needing to
> run slurpd in one-shot mode?
> If I have to run slurpd with -o option, do I have to delete the .rej
> file? Can I delete it while slurpd is running?
> Angel L. Mateo Martínez
> Sección de Telemática
> Área de Tecnologías de la Información _o)
> y las Comunicaciones Aplicadas (ATICA) / \\
> http://www.um.es/atica _(___V
> Tfo: 968367590
> Fax: 968398337