Nsslapd-state automatically switching from backend to referral on update

Question

Hello,
I recently separated 4 instances of DS5.2 which used to be on the same machine on 2 different servers (one master & one slave by server).
The first master is working well (including replication on all 3 other instance) but the second master always switch is state (nsslapd-state) from 'backend' to 'referral on update' and never replicate on other LDAP's instances.
I first think of a backend's data problem and try to copy backends from the first master to the second (with binary copy, ldif2db, bak2db, ...) but wihtout any result.
Then I delete my replication agreement and recreate them but without anymore result.
I don't understand why it isn't working (and the 2 servers are binding each other because the first master's replication works well);
Please help me !!!!!
Julien

Answer 1

There is one button which is available on the right pane after master is initialized, under:
"Data" -> "sufix dc=XYZ,dc=com" -> "Replication"
I don't remember the name on the button but it is someting like "start accepting updates".
Read the following two topics at
http://docs.sun.com/source/816-6698-10/replicat.html#14962
* Convergence After Multi-Master Initialization
* To Begin Accepting Updates Through the Console
To Begin Accepting Updates Through the Console
Follow these steps to explicitly allow update operations after the initialization of a multi-master replica:
On the top-level Configuration tab of the Directory Server console, expand both the Data node and the node for the replicated suffix, and select the Replication node below the suffix.
In the right panel, the console will display a message indicating that the replica has been initialized and is currently returning referrals for update operations. If this message indicates the automatic referral delay is enabled, you may still follow this procedure to override the delay.
Use the insync tool to ensure that the replica has converged with all other masters. Replicas are in sync if the delay between modifications on all servers is zero or if the replica has never had any changes to replicate (delay of -1). For more information, see "insync" in Chapter 1 of the Sun ONE Directory Server Reference Manual.
Click the button to the right of the message to start accepting update operations immediately.