Mine was similar... In my case, the second (slave) puppetmaster
had built its own ca certificates when it was first started.
Obviously
these were different to the primary CA's certificates.
Copying across the CA certificates onto the slave puppetmaster
solved my remaining issues - even though the
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
configurat
OK... I have finally cleaned up most of the mess this has created...
One of the issues I guess was that I was also trying to move the
puppetca from one puppetmaster to another...
I now have a situation where I have 2 puppetmasters, one "master"
and one "slave-master"... The master holds the pupp
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: SS
comment out the SSLCARevocationFile option in apache.
cheers,
Ohad
On Thu, May 21, 2009 at 11:25 AM, jeff wrote:
>
> Hey Greg,
>
> What a timely email. Just this afternoon I was working on bringing a new
> .24.8 puppetmaster online in effort to test migrating to using
> apache/passenger as a fr
Hey Greg,
What a timely email. Just this afternoon I was working on bringing a new
.24.8 puppetmaster online in effort to test migrating to using
apache/passenger as a frontend.
While troubleshooting, I tried running the tried and true puppetmasterd
in lieu of the apache/passenger frontend in
