This content has been marked as final. Show 3 replies
the first command (insync) will inquire the replication protocol to see all the suffixes for which XX02:389 is a 'supplier' (or, in other words, a Master)
The second command (dsconf) instead inquires the status of the replication from XXXXds01:389 to XXXXds02:389 for suffix "dc=example,dc=cl"
From the outputs that you pasted, it seems that the replication is disabled from XXXXds02:389 --> XXXXds01:389, while it is enabled from XXXXds01:389 --> XXXXds02:389 and the last update has been sent on Mar 1, 2013 12:33:59 PM ...
Is that the case?
Is curious that the insync command shows "error" and the command "dsconf show-repl-agmt-status" shows "status : enabled" because reason?
which is the exit status of the insync command? [#echo $? just after the insync]
forgive me, but I cannot see the 'error'... The fact that the Replication between one server (ds2) and another one (ds1) is not enabled, "may be" perfectly licit condition (if you just enabled a one-way replication, or for example in the past for some reason you simply 'stopped' the replication agreement and then you didn't started it again)
The other thing is that with 'insync' you're enquiring to the local host (guess ds1) the 'replication protocol' to check which is the status of the suffixes for which ds2 is a supplier. From the topology/replication point of view, even if the replication agreement between ds2 and ds1 is not enabled (DS2 DISABLED-> DS1), it still exists... and STILL ds2 is a supplier of ds1 for that suffix... and since the updates are sent in the other way around (DS1 ---ENABLED---> DS2) from ds1 to ds2 there is no delay between the replicas.