#258 replication error Data required to update replica has been purged. The replica must be reinitialized.
Closed: wontfix None Opened 12 years ago by rmeggins.

getting many errors like
Data required to update replica has been purged. The replica must be reinitialized.

customer says that no replicas have been deleted, so I don't think it is related to http://directory.fedoraproject.org/wiki/Howto:CLEANRUV


The sequence of messages is like this:
[12/Jan/2012:21:37:36 -0800] NSMMReplicationPlugin - changelog program - agmt="cn=meToconsumer" (consumer:389): CSN 4f0badd7003c00150000 not found, we aren't as up to date, or we purged
[12/Jan/2012:21:37:36 -0800] NSMMReplicationPlugin - agmt="cn=meToconsumer" (consumer:389): Data required to update replica has been purged. The replica must be reinitialized.
[12/Jan/2012:21:37:37 -0800] NSMMReplicationPlugin - agmt="cn=meToconsumer" (consumer:389): Incremental update failed and requires administrator action

so the consequence is that replication stops working

the 4f0badd7003c00150000 causes errors like this on other servers:
NSMMReplicationPlugin - ruv_compare_ruv: RUV [changelog max RUV] does not contain element [{replica 21 ldap://badserver:389} 4f08b674000000150000 4f0badd7003c00150000] which is present in RUV [database RUV]

looking at the access and errors logs from badserver - the CSN 4f0badd7003c00150000 is not found - also not in the changelog db

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: N/A

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/258

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

3 years ago

Login to comment on this ticket.

Metadata