I had this problem. So I ran this on the puppetmaster:
puppet cert --list --all
came back with nothing for the puppetmaster itself. I added my.domain to
search domains in /etc/resolv.conf
I rebooted the puppetmaster and when I ran
puppet cert --list --all
I saw two certs, the one for my
@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of glm
Sent: Monday, March 19, 2012 6:39 PM
To: puppet-users@googlegroups.com
Subject: [Puppet Users] Re: SSLv3 read server certificate B:
certificate verify failed. -- Not time related
Hi
Hi,
On 02/22/2012 08:58 PM, Jon Davis wrote:
How can I track down where the issue for this is?
it's always troublesome, but the only clean approach I'm aware of is
openssl s_client and openssl x509 to carefully compare what the
master is presenting when the agent connects to whatever the agent
How can I track down where the issue for this is? I've found some bugs
and blog posts that seem to be related [1][2] and I've followed all of the
instructions and checked ALL of the versions related. I'm running Ruby
1.8.7 and Puppet 2.7.9 on both sides of the equation, which appear to be
OK
On Wed, Feb 22, 2012 at 11:58 AM, Jon Davis j...@snowulf.com wrote:
How can I track down where the issue for this is? I've found some bugs
and blog posts that seem to be related [1][2] and I've followed all of the
instructions and checked ALL of the versions related. I'm running Ruby
1.8.7
I was cleaning the clients yes.
After I cleaned the puppet server and the client AND still had issues. I
decided to blow away everything in /var/lib/puppet/ssl on the master and
rebuild it. Fortunately I only have a few dozen puppetized machines
because... I have to go through and re-cert them
