Sorry I didn't reply to this message sooner I've been up to my neck in other
things.
I'm not sure if you saw this, but Charles Johnson said
"Gabriel, I use puppet to maintain files and services across a linux cluster
with some 850 boxes. From time to time a box goes down and has to be re-imaged
-Original Message-
From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On
Behalf Of Brian Granger
Sent: Monday, May 03, 2010 6:38 PM
To: Trevor Vaughan
Cc: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] Re: SSL issues when testing - This is how to fix
Just in case others run into this problem...
The issue in my case was that I ran puppet and *then* changed
somethings in /etc/hosts. But, the first time I ran puppetd on the
client, it created a $HOME/.puppet/ssl directory that had the old
host/domain info. Simply deleting it solved the issue.
On the client, what do you get when you run
puppetd --test --debug
~Charles~
On Sat, May 1, 2010 at 8:18 PM, Brian Granger wrote:
> Gabriel,
>
> I am running into similar problems in configuring a single client,
> single server puppet setup.
>
> > I’ve been suffering all week to fix all manner
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you set up autosign by chance?
Try puppetca --list --all
Trevor
On 05/01/2010 09:18 PM, Brian Granger wrote:
> Gabriel,
>
> I am running into similar problems in configuring a single client,
> single server puppet setup.
>
>> I’ve been sufferi
