try to review the access log for connection events related to those from the errors log file mentioned earlier, and also verify on the remote replica, the errors and access log events corresponding to this connection, as well as file descriptors and LDAP thread use, run some netstat and dsconf monitor commands:
dsconf SOME-INSTANCE-NAME-HERE config get nsslapd-conntablesize nsslapd-threadnumber nsslapd-maxdescriptors dsconf SOME-INSTANCE-NAME-HERE monitor server sysctl net.core.somaxconn net.ipv4.tcp_max_syn_backlog On Thu, Apr 18, 2024 at 10:53 AM <tda...@arizona.edu> wrote: > Just to add: > > - I can manually make a connection from the old to new using the > replication account and password, so connectivity is fine. > - The old server is in 2-way replication with another server of the same > version and that is all working perfectly. > -- > _______________________________________________ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-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/389-users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-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/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
