OK; opened: https://bugzilla.redhat.com/show_bug.cgi?id=571677
2010/3/9 Rich Megginson
> Juan Asensio Sánchez wrote:
> > One note, we have servers with version 1.1.3 and servers that have
> > been upgraded to version 1.2.5. Only the servers that have been
> > upgraded to 1.2.5 are showing the bu
One note, we have servers with version 1.1.3 and servers that have been
upgraded to version 1.2.5. Only the servers that have been upgraded to 1.2.5
are showing the busy replica error, not those with version 1.1.3. Hope this
could help.
Regards.
El 8 de marzo de 2010 16:50, Juan Asensio Sánchez
These are the messages when enabling replication logs:
[08/Mar/2010:16:02:51 +0100] NSMMReplicationPlugin - conn=221525 op=11
repl="o=X,dc=X,dc=X": Replica in use locking_purl=conn=207283
id=3
[08/Mar/2010:16:02:51 +0100] NSMMReplicationPlugin - conn=221525 op=11
replica="o=X,dc=XX
At first sight, there are no messages neither in access or error logs, in
supplier or consumers. Last modification operation in the busy
replica/database is:
[08/Mar/2010:08:16:01 +0100] conn=207283 op=4 DEL
dn="nsuniqueid=f851c101-1dd111b2-a64db547-e406+uid=cabudenhos029p$,ou=computers,o=
Juan Asensio Sánchez wrote:
> Hi all
>
> I have posted this on the chat, but i am not sure if it is wirking
> fine in my computer. I am using 389ds 1.2.5, and i have found some
> replication conflicts (nsds5replicaconflict=*). I have deleted them
> manually, and now the databases in the other se
