How do I do this manually on server A?
 
The other question is, what kind of impact does it have when I re-iitialize server B? To be more precise, my replication environment is more complex than just server A and server B. In fact, I have a setup like the following:
 
srv C <--> srv A <--> srv B <--> srv D <--> srv C
                 /\             /\
                 |               |
                \/              \/
              srv E          srv F
 
I don't want to end up to re-initialize all boxes in my environment.
 
Thanks,
-Reinhard

From: Marc Sauton [mailto:msauton@redhat.com]
Sent: Tuesday, October 11, 2011 4:36 PM
To: General discussion list for the 389 Directory server project.
Cc: Reinhard Nappert
Subject: Re: [389-users] Replication issue

On 10/11/2011 01:22 PM, Reinhard Nappert wrote:
Hi,
 
I encountered the following logs in the errors:
[06/Oct/2011:10:11:57 +0000] NSMMReplicationPlugin - changelog program - agmt="cn=srvAtosrvB" (srvB:389): CSN 4e8d804a0000000c0000 not found, we aren't as up to date, or we purged
[06/Oct/2011:10:11:57 +0000] NSMMReplicationPlugin - agmt="cn=srvAtosrvB" (srvB:389): Data required to update replica has been purged. The replica must be reinitialized.

[06/Oct/2011:10:11:57 +0000] NSMMReplicationPlugin - agmt="cn=srvAtosrvB" (srvB:389): Incremental update failed and requires administrator action
 
Does anyone have an idea, what could have caused this and more importantly, how to fix this?
 
Thanks
-Reinhard

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
On server A, read a changelog to manually run the changes on server B.
May be tune up nsds5ReplicaPurgeDelay if such errors somehow appears regularly.
Otherwise, like the errors log says, the change was purged/removed, and replica need a re-init.
M.