Re: [Puppet Users] SSL issues arising from cloning environment

2014-11-18 Thread Roger Sherman
Er ah, to be more specific, I had to list the correct .pem files in the puppetmaster vhost, and change the server IP. On Tuesday, November 18, 2014 10:51:40 AM UTC-5, Roger Sherman wrote: > > Turns out this was the problem - thanks for the help, guys, as always, > talking it out helped point me

Re: [Puppet Users] SSL issues arising from cloning environment

2014-11-18 Thread Roger Sherman
Turns out this was the problem - thanks for the help, guys, as always, talking it out helped point me down the right path. Thanks, Rog On Tuesday, November 18, 2014 9:56:05 AM UTC-5, Roger Sherman wrote: > > Right - and on that note, I think I've made a little bit of progress, but > I'm still

Re: [Puppet Users] SSL issues arising from cloning environment

2014-11-18 Thread Roger Sherman
Right - and on that note, I think I've made a little bit of progress, but I'm still not there yet. I looked at the apache vhost file for the puppetmaster, and found the following: # you probably want to tune these settings PassengerHighPerformance on PassengerMaxPoolSize 12 PassengerPoolIdle

Re: [Puppet Users] SSL issues arising from cloning environment

2014-11-18 Thread jcbollinger
On Tuesday, November 18, 2014 7:57:44 AM UTC-6, Roger Sherman wrote: > > For some reason, (I think) the PM is unable to sign them. At least, that's > what seems to be the case. > Well yes, sort of. It appears that the PM is unable to sign the requests because the client is unable to establis

Re: [Puppet Users] SSL issues arising from cloning environment

2014-11-18 Thread Roger Sherman
Hi Neil, thank you for the response. Certificate requests are sent out during a noop run, which are then signed on the PM and then a subsequent noop run puts the cert in place. For some reason, (I think) the PM is unable to sign them. At least, that's what seems to be the case. Thank you, Rog

Re: [Puppet Users] SSL issues arising from cloning environment

2014-11-18 Thread Neil
Hello 2.7 is pretty old. IIRC noop stops the agent writing anything including the certificate stuff. You can either Drop the noop Upgrade puppet on client Do the certificate work manually Specify the certname in the config and use the old cert assuming your cloned master still has that Neil On 18

[Puppet Users] SSL issues arising from cloning environment

2014-11-17 Thread Roger Sherman
I'm in the process of setting up a staging environment for the company I work for. To do this, we've cloned our production environment (vmware), changed the hostnames of the nodes, re-IP'd the nodes, and since that point, I've been trying to get the environment to the point where I can do puppe