I set this effort down for another project. I have some good news. As of today after an auto update of OS and 389-DS the issue is fixed. I had another test system that I updated 389-ds to 2.6.1-8 and replication still failed the same way. I the did a dnf update to take it from rhel 9.5 to 9.6 plus kernel. After a reboot it also is fixed. Unsure if it was 389-ds, Rhel 9.6 or a combination but seems solid for a full init using port 636.
# cat /etc/redhat-release Red Hat Enterprise Linux release 9.6 (Plow) # rpm -qa|grep 389 389-ds-base-libs-2.6.1-8.el9_6.x86_64 389-ds-base-2.6.1-8.el9_6.x86_64 python3-lib389-2.6.1-8.el9_6.noarch -- _______________________________________________ 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
