DANIEL CRISTIAN CRUZ wrote: > When in multi-master, I guess it's normal when one master is updating and > another is trying to do the same. > Yes. > I my case, even when requested from console in a single master > configuration, it doesn't work. Stay with status "Busy Replica". > What platform? What version of DS? > 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) > > > > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3258 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20090520/5a532a30/attachment.bin