httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gregg Smith <>
Subject Re: A push for 2.4.2
Date Sun, 01 Apr 2012 00:04:19 GMT
On 3/31/2012 12:44 PM, Graham Leggett wrote:
> On 31 Mar 2012, at 7:25 PM, Gregg Smith wrote:
>> It was nss and I was pulling away nss dll files to see just what was needed and what
wasn't. Interesting was that the error was different for most but that error came up for some.
The other was
>> [Fri Mar 30 18:12:05.018600 2012] [session_crypto:error] [pid 3404:tid 700] (OS 126)The
specified module could not be found.  : AH01845: The specified module could not be found.
>> This does give better info
>> [Sat Mar 31 10:15:59.017600 2012] [session_crypto:error] [pid 4932:tid 700] (100005)Error
string not specified yet: AH01845: The crypto library 'nss' could not be loaded: (null) (Error
during 'nss' initialisation)
>> Maybe however, "Error string not specified by the driver yet" or something to that
effect? It cannot be incorrectly read as "we're not sure what to say here yet," as I embarrassingly
> The string "Error string not specified yet" belongs to APR, and is returned if an error
code (in this case
> 100005) isn't recognised by apr_error_string().
> If it's nss, then the following code is generating the error:
>      if (s != SECSuccess) {
>          if (result) {
>              apu_err_t *err = apr_pcalloc(pool, sizeof(apu_err_t));
>              err->rc = PR_GetError();
>              err->msg = PR_ErrorToName(s);
>              err->reason = "Error during 'nss' initialisation";
>              *result = err;
>          }
>          return APR_ECRYPT;
>      }
> In turn, it means that PR_ErrorToName(s) is returning the string "(null)".
> It may be worth logging the value err->rc as well to see the value of the NSS error.
When I developed this stuff way back when I discovered a number of places where NSS errors
were either missing or were duplicated (ie multiple failures mapped to the same error code).
When the errors were pointed out, the NSS guys were very quick to fix the problems. Are you
using a recent version of NSS?

3.13.3, Feb. 22, 2012


View raw message