[389-users] How to unlock a busy replica

DANIEL CRISTIAN CRUZ daniel.cruz at sc.senai.br
Wed May 20 13:21:42 UTC 2009


When in multi-master, I guess it's normal when one master is updating and
another is trying to do the same.

I my case, even when requested from console in a single master
configuration, it doesn't work. Stay with status "Busy Replica".

Regards,

"Tim Hartmann" <hartmann at fas.harvard.edu> escreveu:
> 
> I've also run into this a bit, we monitor our replication with Nagios,
> and I've gotten a couple of alerts like this:
> 
> Replication error: 1 Cant acquire busy replica
> 
> Which is cleared by having the the effected master send another update,
> so far i've always done it through the console, but I DID find this
> script to do it through the CLI:
> 
>
http://www.redhat.com/docs/manuals/dir-server/8.1/admin/Managing_Replication-Forcing_Replication_Updates.html
> 
> I'd be interested in hearing if anyone else has come across this, and if
> there are any configuration tweaks that people might suggest to keep us
> from seeing this error, or maybe even clearing it automatically?

--
<span style="color: #000080">Daniel Cristian Cruz
</span>Administrador de Banco de Dados
Direção Regional - Núcleo de Tecnologia da Informação
SENAI - SC
Telefone: 48-3239-1422 (ramal 1422)







More information about the Fedora-directory-users mailing list