NSS .pki/nssdb issue with google content_shell for version 47

[Jacques Levy (jacqlevy)]

Hi,

 

I am trying to compile content_shell  on a STB with following options :

use_nss_certs=1

use_open_ssl=1

use_openssl_certs=0

 

I use version 47 of chromium.

 

For that I have previously cross compiled NSS/NSPR .

 

Now, when, I try to run content_shell on the STB, I can see following error, and a crash :

 

1723:1726:1216/165136:4454458773:WARNING:dns_config_service_posix.cc(302)] Failed to read DnsConfig.
[1723:1735:1216/165137:4454853351:ERROR:nss_util.cc(740)] Error initializing NSS with a persistent database (s
ql:/.pki/nssdb): File not found
[1723:1735:1216/165137:4454854330:ERROR:nss_util.cc(209)] Error initializing NSS without a persistent database
: NSS error code: -5925
[1723:1735:1216/165137:4454854587:FATAL:nss_util.cc(211)] nss_error=-5925, os_error=0

 

 

On linux, on the build directory, I can see that src/chrome/test/data/diagnostis/user/.pki/nssdb contains :  cert9.db, key4.db, pkcs11.txt

 

 

So  I tried to put it on the STB in different areas:

 

/home/.pki/nssdb

/.pki/nssdb

sql:/.pki/nssdb

 

I have the same issue.

 

·         Did you ever meet this issue ?

·         Do you know where to put those files ? or how not to use them ?

 

I can see a similar issue here : https://code.google.com/p/chromium/issues/detail?id=100857

 

Error initializing NSS with  

a persistent database: NSS error code: -8187
http://code.google.com/p/chromium/issues/detail?id=100857

benjamin.pabst85: thank you for the strace log.  It shows the preparation
for initializing NSS (checking that the directory /home/xxx/.pki/nssdb  
exists),
but does not show some operations that NSS does during initialization, such
as reading 1024 bytes from /dev/urandom or opening /var/tmp and /usr/tmp.
This means NSS_InitReadWrite must have failed very early.

To track this down will require running Chrome in a debugger and  
single-stepping
after Chrome enters NSS_InitReadWrite.  You can also set a conditional  
breakpoint
in the PR_SetError function, with the condition code=-8187.

I don't know if you have the setup or time to do this kind of debugging.

 

 

How as it been solved ?

 

Thanks

 

Regards

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.