Cause: nss internal call stan_GetCERTCertificate did nor properly ensure sure that objects do not go away until it it's finished with the operation
Consequence: A crash in 389-ds-base server was reported in in nss's stan_GetCERTCertificate (pki3hack.c) under the replication replay failure condition.
Fix: The certificate code was fix to properly manage objects references.
Result: The crashes reported by the 389 directory server no longer occur
Hi Elio,
The crash occurred for me, too. I'm attaching the stacktraces, which looks different from the one Sankar attached (attachment 939356[details]), though.
Here's the component list used in my test.
nss-devel-3.16.2-4.el7_0.x86_64
nss-util-devel-3.16.2-1.el7_0.x86_64
nss-debuginfo-3.16.2-4.el7_0.x86_64
nss-softokn-freebl-3.16.2-1.el7_0.x86_64
nss-softokn-freebl-devel-3.16.2-1.el7_0.x86_64
nss-sysinit-3.16.2-4.el7_0.x86_64
nss-tools-3.16.2-4.el7_0.x86_64
nss-util-3.16.2-1.el7_0.x86_64
nss-pkcs11-devel-3.16.2-4.el7_0.x86_64
nss-softokn-devel-3.16.2-1.el7_0.x86_64
nss-softokn-3.16.2-1.el7_0.x86_64
nss-3.16.2-4.el7_0.x86_64
nspr-4.10.6-1.el7_0.x86_64
nspr-debuginfo-4.10.6-1.el7_0.x86_64
nspr-devel-4.10.6-1.el7_0.x86_64
389-ds-base-1.3.1.6-26.el7_0.x86_64
389-ds-base-libs-1.3.1.6-26.el7_0.x86_64
389-ds-base-debuginfo-1.3.1.6-26.el7_0.x86_64
389-ds-base-devel-1.3.1.6-26.el7_0.x86_64
Created attachment 940216[details]
stacktraces from the 389-ds-base core.
The core file was generated. Please let me know if you are interested in examining it.
Comment 17Sankar Ramalingam
2014-12-08 09:48:02 UTC
Any updates from nss team for this crash issue? This is not fixed in RHEL7.1 as well.