Never mind-- the issue was that my client is a virtual server (linux
vserver) and the host's puppet agent had the default bind address of
0.0.0.0, so it was grabbing all the addresses and the agent couldn't
start on the vserver. I changed the bind address for the host, started
the agent on the clie
On Fri, 24 Feb 2012 12:39:20 -0500
Adam Heinz wrote:
> I upgraded from puppet 0.25.5 to 2.6.12 recently and ended up doing
> puppetca --clean then --sign again for each of my hosts. Seemed a bit
> brute force, but it got me out of the bind.
I tried cleaning out and regenerating the cert for my
I upgraded from puppet 0.25.5 to 2.6.12 recently and ended up doing
puppetca --clean then --sign again for each of my hosts. Seemed a bit
brute force, but it got me out of the bind.
On Fri, Feb 24, 2012 at 12:30 PM, Dan Urist wrote:
> puppet kick ceased working for me when I upgraded to 2.6.3; I
puppet kick ceased working for me when I upgraded to 2.6.3; I've also
tried it with 2.7.10 and get the same result:
> r...@npuppet.ucar.edu $ puppet kick vanilla.cms.ucar.edu
> Triggering vanilla.cms.ucar.edu
> Host vanilla.cms.ucar.edu failed: Server hostname 'vanilla.cms.ucar.edu' did
> not mat
