-----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. Things I learned: * Try running the puppetmasterd by hand with the --no-daemonize --debug --verbose options to see what is going on. * Run puppetd on the client with the same options. * Deleting the ssl directories in $HOME/.puppet and /var/lib/puppet is sometimes needed. Another subtle point is that I was doing the initial certificate signing using a regular user and sudo. The problem with this is that the certs go into $HOME/.puppet/ssl rather than the system /var/lib/puppet that would be used if you start things using the init.d scripts that come with the system. This is a bit confusing and means that the recommended way of running puppetd by hand in non-daemon mode to sign the certs doesn't work properly on Ubuntu. Cheers, Brian These are some good tips, I'm adding this to my notes, something to check on my puppet hosts -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
