Luke Kanies wrote:
> Just so you know, part of the problem too is that Debian (I think)
> ships with waitforcert=0 in a release in which Puppet thinks that
> means "keep trying" rather than "exit", which means that your puppet
> client will just hit the server as fast and as hard as it can.
Just so you know, part of the problem too is that Debian (I think)
ships with waitforcert=0 in a release in which Puppet thinks that
means "keep trying" rather than "exit", which means that your puppet
client will just hit the server as fast and as hard as it can.
The easiest way to track d
So this turned out to be caused by the fact that I had changed the
name of one of our servers and I hadn't signed the cert for it yet.
The error message is not very helpful at all since it references
"localhost" instead of the server that's trying to authenticate so
I've filed a bug for this:
ht
