[389-users] Re: Rhel 9.4 389-DS 2.4.5 Provider fails to fully initialize Rhel 9.4 389-DS 2.4.5 Consumer database.

Mark,

 

I highly suspect that https://github.com/389ds/389-ds-base/issues/6551 is also resolved. That error is very close to what I saw and the reporter referenced my issue.
https://www.mail-archive.com/389-users@lists.fedoraproject.org/msg10204.html

 

I also want to point out that the rhel 9.6 release notes are lagging the release which should be included with release availability. I am very interested as to what fixed this failure.

So for nss, that was not updated and package remains the same version on 9.5 and 9.6
nss-3.101.0-10.el9_2.x86_64

 

 

From: Mark Reynolds <mareynol@redhat.com>
Date: Thursday, May 15, 2025 at 7:28 PM
To: General discussion list for the 389 Directory server project. <389-users@lists.fedoraproject.org>
Cc: Bouvet, Timothy A <tbouvet@illinois.edu>
Subject: Re: [389-users] Re: Rhel 9.4 389-DS 2.4.5 Provider fails to fully initialize Rhel 9.4 389-DS 2.4.5 Consumer database.

We've been seeing several replication online init failures that seem to
be related to agreements that use TLS.  What version of "nss" are you on
now?  Any chance you knew the previous nss version on rhel 9.5?

Thanks,
Mark

On 5/15/25 5:27 PM, tbouvetncsa via 389-users wrote:
> 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

--
Identity Management Development Team