FWIW - I currently see this error on around 30% of our EC2 nodes since moving to 0.25. We also use the rpm's provided for both client and master. The fix is for us to log on to the EC2 node, remove the cert, run a puppetca --clean on the master for the hostname, and then start puppet again on the client.
I haven't had time to figure out was going on yet, but it feels like the first poll is somehow generating a bad key. 2009/10/14 Todd Zullinger <t...@pobox.com>: > James Turnbull wrote: >> Also the puppet.conf bundled with the RPM is written by the >> downstream package maintainers (Todd?) - perhaps there is an issue >> there also? Can you pastie that also? > > We ship the puppet.conf file from conf/redhat in the puppet tarball in > the Fedora/EPEL packages, as well as the packages I've put up on my > fedorapeople.org space. So the package should function as well (or as > unwell) as if it was installed from source. :) > > It still couldn't hurt to see the puppet.conf to be sure it's alright. > > I thought one of the issues reported with 0.25.x involved ssl certs > and setting up puppetmaster and clients from scratch with 0.25. But > that's just based on a hazy memory, so I could easily be way off. > > -- > Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > An idea is not responsible for the people who believe in it. > -- Anonymous > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
