Hi
Thanks Rich for your answer. Just some questions:
The bug that caused this to happen was fixed, but unfortunately cannot
fix the bad nsState that already exists. The problem is that the CSN
generator attribute (nsState) in the cn=replica entry for the suffx is
not cleaned up properly when you re-init replication. In general, you
can't do this, because you could generate CSNs that you have generated
before.
I think the solution here is to first unconfigure replication,
then
shutdown the servers, then dump the database(s) to LDIF,
then remove the
nsState attribute.
You will have to do this on every server. Then,
start up, reconfigure replication, reload the data,
and re-init all of
the other replicas. Make sure all of your servers are in time sync
before you begin.
I know this is a pain but I don't know any other way to get rid of the
bad nsState.
>
> Regards and thanks in advance.
>