On Jul 16, 2024, at 20:15, Alex Nazarenko <alexander.b.nazare...@gmail.com>
wrote:
>
> Hello, colleagues,
>
> After moving to RHEL9.2 and 389-ds-base-2.4.5-8.el9_4.x86_64 the following
> behavior is observed:
>
> The system is Supplier-consumer.
> 1. Patch RHEL9.2 supplier server
> 2. Reboot the supplier server to enable patches
> 3. Observe the following error in the replication agreement:
> {"state": "red", "ldap_rc": "0", "ldap_rc_text": "Success", "repl_rc": "19",
> "repl_rc_text": "RUV error", "date": "2024-07-16T19:16:48Z", "message":
> "Error (19) Replication error acquiring replica: Replica has different
> database generation ID, remote replica may need to be initialized (RUV
> error)"}
>
> Is there a way to avoid such behavior, or what is the best way to fix the
> replication agreement short of removing and re-initializing the consumer?
I suggest switching to Fedora, since this is a Fedora mailing list, then at
least it’s on topic. 389-ds-base is part of RHEL, it’s not in EPEL.
Since you’re using RHEL, perhaps you can open a case with Red Hat to get help?
There is also a 389-users list, although I don’t know if it’s limited to Fedora
versions.
https://lists.fedoraproject.org/archives/list/389-us...@lists.fedoraproject.org/
--
Jonathan Billings
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
