Solved? Re: [Puppet Users] Re: Certificate issue for puppetd on same node as puppetmasterd

Jeff Adams
Thu, 21 May 2009 17:01:48 -0000

My WEBrick''s masterhttp.log file was telling a slightly different
story:

[2009-05-21 11:41:22] ERROR OpenSSL::SSL::SSLError: sslv3 alert bad
certificate
         /usr/lib/ruby/1.8/openssl/ssl.rb:122:in `accept''

As it turned out, in my /etc/puppet/manifest/site.pp file the filebucket
configuration was pointing to a different puppetmaster host.

Once that was fixed to reference the local puppetmaster, my cert errors
went away and the manifests applied properly.

Hope this helps someone.

- Jeff

On 05/20/2009 11:24 PM, Greg wrote:
> Not running Apache - I''m still using a WEBrick based setup, mostly
> because Apache ->  Mongrel
> isn''t playing ball... But that''s a different story...
>
> Further analysis has shown me that there is an error message in
> WEBrick''s masterhttp.log file:
>
> [2009-05-21 13:54:30] ERROR OpenSSL::SSL::SSLError: SSL_accept
> returned=1 errno> 0 state=SSLv3 read client certificate A: tlsv1 alert
unknown ca
>          /opt/csw/lib/ruby/1.8/openssl/ssl.rb:166:in `accept''
>
> At first I thought it had chopped off the alert, but it appears to be
> complaining about the lack of a
> CA... The files all appear to be in order - its signing certificates
> happily enough...