CSN XXX not found, we aren't as up to date, or we purged

[Sergei Gerasenko <gerases@xxxxxxxxx>]

Hi,

I see these messages in the errors log of on a couple of suppliers.:

08/Nov/2017:22:44:13.612346436 +0000] NSMMReplicationPlugin - changelog program - agmt="cn=meToXXXXt": CSN 5a02f2c30002007c0000 not found, we aren't as up to date, or we purged

[08/Nov/2017:22:44:13.629490783 +0000] NSMMReplicationPlugin - agmt="cn=meToXXXX": Data required to update replica has been purged from the changelog. The replica must be reinitialized.

The documentation from RedHat says:

agmt=%s(%s:%d): Can't locate CSN %s in the changelog (DB rc=%d). The consumer may need to be reinitialized.

Most likely the changelog was recreated because of the disk is full or the server ungracefully shutdown.

The local server will not be able to send any more change to that consumer until the consumer is reinitialized or gets the CSN from other suppliers.

If this is a single-master replication, reinitialize the consumers. Otherwise, see if the consumer can get the CSN from other suppliers. If not, reinitialize the consumer.

I’ve used cl-dump to look at the change log but none of the machines have a reference to it. So where is the knowledge of that CSN is coming from and what can I do besides reinitializing? I’ve tried multiple reinitializations but the error just moves to another machine.

The replication doesn’t seem to be affected however. The symptom is error 18 in the output of `ipa-replica manage $HOSTNAME list`.

Mark Reynolds did suggest it was possibly a bug in 389-ds-base-1.3.5.10-21.el7_3.x86_64, but it’s not feasible to upgrade at the moment. Any way to manually maneuver out of this without upgrading?

Thanks,

  Sergei

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx