On Fri, Sep 28, 2012 at 2:29 PM, Forrie <for...@gmail.com> wrote: > I'm not at PuppetConf, unfortunately. In this case, all I did was a > simple CentOS "service puppetmaster restart" as I have in the past. > > But, I wonder if the fact there are older versions still present might > contribute to this -- though it shouldn't be reading code from those > locations. >
Definitely. Your stack trace shows puppetmasterd running out of 2.7 but the main puppet code loaded out of 3.0. This is probably because 3.0 no longer ships a puppetmasterd command (it was deprecated in 2.7 in favor of 'puppet master'). Rubygems allows you to have multiple versions installed at the same time, so probably all you need to do is make sure only 3.0 is installed and then make sure your init script calls puppet master instead of puppetmasterd. -Patrick -- 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.
