I would have thought that, instead of rsyncing the new machine, you'd have used Puppet to deploy it as a Puppet master. I'm curious as to why you went this route?
On Thu, Apr 22, 2010 at 12:22 AM, Nicolas Szalay <[email protected]>wrote: > ----- "Brian Lam" <[email protected]> a écrit : > > | I apologized ahead of time if this post shouldn't go here but I > | having > | been knocking my heading for the last two days trying to get over the > | following error while trying to "clone" my primary puppetmasterd > | because we have outgrown one puppetmasterd setup. > | > | I have basically set up a 2nd instance of our primary puppetmasterd > | and rsync'ed over /var/lib/puppet/ssl/ from the primary to the > | secondary puppetmasterd. The client ran to completion (and recorded > | the log in /var/lib/puppet/report/) but the file copying statement > | were failing: > | (see log below) > > Ohad has the right answer : using the certname directive is the solution. > If there are french readers around here you can get the latest "GNU/Linux > Magazine" with an article I wrote about this kind of setup (multi masters > with a nginx in front of the clients). > > Regards, > > Nico. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<puppet-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
