Description of problem:
mod_nss is returning an error when the engine is not enabled:
NSS_Shutdown failed: -8038
This error resolves to SEC_ERROR_NOT_INITIALIZED
So basically NSS_Shutdown() is being called when the NSS is not enabled.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start Apache + mod_nss
2. Look in the error log
Checked into mod_nss tip.
Checking in nss_engine_init.c;
/cvs/dirsec/mod_nss/nss_engine_init.c,v <-- nss_engine_init.c
new revision: 1.24; previous revision: 1.23
Checking in nss_engine_log.c;
/cvs/dirsec/mod_nss/nss_engine_log.c,v <-- nss_engine_log.c
new revision: 1.5; previous revision: 1.4
Tagged as mod_nss105
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers