this is the correct document for the full cleanup.
it may be possible to recover by just deleting the nsState on a master and
doing a reinit of all the replica, but there may be stale csn traces in the
ruv in each replication agreement.
M.


On Mon, Apr 9, 2018 at 5:49 AM, Paul Whitney <paul.whit...@mac.com> wrote:

> Hi guys,
>
> I have been reading up on a fix for this and only found one set of
> procedures to repair this issue. (http://directory.
> fedoraproject.org/docs/389ds/howto/howto-fix-and-reset-time-skew.html).
> Would removing/recreating the replication agreement resolve this issue
> instead of the steps in the above URL?
>
>
> Paul M. Whitney
> E-mail: paul.whit...@mac.com
> Sent from my browser.
>
>
>
> _______________________________________________
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>
>
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

Reply via email to