> On 5 Feb 2019, at 09:00, Zarko D <zarko@xxxxxxxxxxxx> wrote: > > Correct, I've run the command: > > ipa-replica-manage -v re-initialize --from=<another-master> > > ... it completed successfully. The remaining problem is that this 'fixed' server doesn't get updates from another master, the error is : > "Error (16) : Incremental update connection error. Backing off, will retry update later." > As per this doc: > https://directory.fedoraproject.org/docs/389ds/FAQ/replication-update-status.html > .. this is considered temporary, I am afraid it's permanent in my case. > > For now my work around is having cronjob that repeats "ipa-replica-manage -v re-initialize --from=<another-master> " and this gets updates. > This doesn’t exactly sound like a sustainable situation … I believe you can enable verbose rreplication logging by setting the nsslapd-errorlog-level to 8192 which could give us more insight. — Sincerely, William Brown Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
