Bug 211139 - mod_nss reports NSS_Shutdown failed: -8038
Summary: mod_nss reports NSS_Shutdown failed: -8038
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: mod_nss (Show other bugs)
(Show other bugs)
Version: 5
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Rob Crittenden
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: bzcl34nup
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-17 16:31 UTC by Rob Crittenden
Modified: 2008-04-04 14:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-04 14:01:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Rob Crittenden 2006-10-17 16:31:03 UTC
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):

mod_nss-1.0.4

How reproducible:

Every time.

Steps to Reproduce:
1. Start Apache + mod_nss
2. Look in the error log

Comment 1 Rob Crittenden 2006-10-17 16:52:24 UTC
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
done
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
done
Running syncmail...
Mailing relnotes@fedoraproject.org...
...syncmail done.
Running syncmail...
Mailing cvsdirsec@fedora.redhat.com...
...syncmail done.

Tagged as mod_nss105

Comment 2 Bug Zapper 2008-04-04 04:00:54 UTC
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.
http://fedoraproject.org/wiki/LifeCycle/EOL

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
the change.

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:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

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


Note You need to log in before you can comment on or make changes to this bug.