I am pretty sure the issue is actually some configs needed on your non-CA
master in its /etc/puppetlabs/puppetserver/conf.d/webserver.conf.
See https://docs.puppet.com/puppetserver/2.2/external_ca_configuration.html
for documentation on this. The added lines you likely need are these:
ssl-c
http://docs.puppetlabs.com/puppetserver/2.1/external_ca_configuration.html
On Monday, September 21, 2015 at 5:56:10 AM UTC+3, rhpupp...@gmail.com
wrote:
>
> We currently have a handful number of puppet masters and using
> apache-passenger stack to run puppet master service. We use set of
> dedi
On 17 July 2013 14:18, Nick Lewis wrote:
> On Tuesday, July 16, 2013 1:25:22 PM UTC-7, replicant wrote:
>>
>> So,
>>
>> We are working on migrating a global deployment of Puppet over to a
>> single PuppetDB instance away from a single MySQL storeconfigs
>> instance and are running into an issue. I
On Tuesday, July 16, 2013 1:25:22 PM UTC-7, replicant wrote:
> So,
>
> We are working on migrating a global deployment of Puppet over to a
> single PuppetDB instance away from a single MySQL storeconfigs
> instance and are running into an issue. It seems is that PuppetDB will
> only allow node
I was wondering if on the 2nd puppet master I have installed, whether or
not I need the SSLEngine on for my virtual host configuration file? I have
tried this, but with no luck...
LoadModule passenger_module
/usr/lib/ruby/gems/1.8/gems/passenger-3.0.18/ext/apache2/mod_passenger.so
PassengerRoot
