I ran into an issue a while back on my puppet master where I had upgraded puppet and the result put the puppet executables in a different directory than I expected. The /etc/init.d script that I used to start puppet master was looking in the old directory and starting the wrong version.
Be sure you don't have something similar here. In my case /usr/bin vs. /usr/sbin (not sure which was right now..) On Wed, Feb 8, 2012 at 12:26 PM, Craig White <craig.wh...@ttiltd.com> wrote: > > On Feb 8, 2012, at 9:40 AM, rjl wrote: > > > Thanks everyone. Seems like having an older version of Master causes > > this problem but I do not have an older version. My clients and Master > > are both 2.7.10. > ---- > I'm thinking that perhaps you have more than 1 version of ruby/puppet > installed on the server or possibly you never restarted the puppet master > after the upgrade. > > Craig > > -- > 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. > > -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- 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.
