Hi, Pierre,
I appreciate your assertive approach to addressing this issue.
I reviewed the logs on node01, which was sending data for replication, and
noticed that at the exact moment the error was recorded on node02, node01
logged an LDAP error 51 ("Server is busy").
Given that node01 and node02 are virtual machines on the same network segment,
I do not believe this issue is related to the network interface.
This leads me to focus on the minimum resource requirements or internal
parameters of the 389 Directory Server as potential causes.
Currently, both nodes are configured with 4 vCPUs and 4 GB of RAM each.
I suspect that some internal parameter in the 389 DS configuration might be
contributing to this issue.
Looking forward to your insights.
--
_______________________________________________
389-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
