On 02/04/13 12:10, Nathan Scott wrote:
>
>
> ----- Original Message -----
>> Apologies ... I did not check the script and misread the output.
>>
>> The issue really appears to be the "Peer's Certificate issuer is not
>> recognized" error ... which is also seen in QA/712.
>>
>
> These tests generate a self-signed certificate for use to validate
> the SSL connections (so the certificate issuer is the qa host).
> The qa/common.secure nss_setup_certificates function does this bit
> fwiw.
>
>> What am I doing wrong here?
>
> Not clear, as the above certainly appears to be accepted on my setup
> (nss-3.13.6-2). Check the results of the nss_subject_name function
> in common.secure might be a starting point, as this drives $certdomain
> used later on (712.full should have greater detail).
Well it appears this test for me is always either not run (no certutils, PCP
build w/out secure sockets support) or fails.
I tried moving closer to your environment with CentOS 5.9 and nss-3.13.6-3 but
the problem got worse!
I installed the nss-devel and nspr-devel rpms, rebuilt PCP, and installed the
new PCP rpms.
But now I _cannot_ start pmcd ... each time I run /etc/init.d/pcp start I end
up with an empty ~kenj/.pki/nssdb directory being created (if it does not
already exist) and then
kenj@vm04:~/src/pcp/qa$ pcp
pcp: [Wed Apr 3 10:03:46] pminfo(2728) Warning: __pmConnectPMCD: certificate
database exists, but failed initialization
Cannot connect to PMCD on host "vm04.localdomain": Connection refused
Arrgghh ....
|