Hi Tim,
Perhaps I am missing something in your output. There may be some
actions implied that you took but where not shown. So excuse me if I
am misunderstanding something.
Did you take any actions on the server side while you were running
'puppetd -t --waitforcert 15 --server puppet.example.ne
pet it
> should also act as a client.
>
> Cheers,
> Den
>
> On 08/04/2011, at 8:22, Saurval wrote:
>
>
>
> > At the time of the last run I did not have a nodes.pp included in my
> > configuration. I had added one with a node definition, but it has
> > made no d
FQDN comes up
as the default value for 'certname'. When I look at the certificate
my 'CN= my FQDN' comes up as the Issuer and the Subject, so that seems
to match just fine.
I do not have a [client] section to my configuration, and I do not see
one in my --genconfig output eithe
I am on CentOS 5.4 running
puppet-0.22.4-1.el5.rf
puppet-server-0.22.4-1.el5.rf
I am a little stumped on this one.I imagine it is something simple
I am missing. but basically the puppetmasterd cannot talk to a
puppetd instance running as a client on the same host.
The error I am getting is