Hi, I''m just getting started with puppet, and using the RPMS provided (on CentOS 4.3), and RedHat''s killproc is annoying me again. The process is called ''ruby'' instead of ''puppetmasterd''. $ ps 7869 PID TTY STAT TIME COMMAND 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] So, service puppetmaster restart|condrestart|stop all fail because RH is looking for a process called /usr/sbin/puppetmaster, and not ruby. I''m wondering if anyone else is having problems with this ? thanks, -sharif
On Fri, 2006-08-18 at 20:04 -0700, Sharif Nassar wrote:> > Hi, > > I''m just getting started with puppet, and using the RPMS provided > (on CentOS 4.3), and RedHat''s killproc is annoying me again. > > The process is called ''ruby'' instead of ''puppetmasterd''. > > $ ps 7869 > PID TTY STAT TIME COMMAND > 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] > > So, service puppetmaster restart|condrestart|stop all fail because RH is > looking for a process called /usr/sbin/puppetmaster, and not ruby. > > I''m wondering if anyone else is having problems with this ?What version of puppet are you using ? There was a bug that lead to those problems; that has been fixed in the specfile for 0.18.4-2 .. and I just noticed that I haven''t rebuilt the RHEL rpm''s for that. I''ll update my yum repo early next week. The trick is that /usr/sbin/puppetmasterd should say ''#! /usr/bin/ruby'' in the first line instead of ''#! /usr/bin/env ruby'' David
On Sat, 19 Aug 2006, David Lutterkort wrote:> On Fri, 2006-08-18 at 20:04 -0700, Sharif Nassar wrote: >> >> Hi, >> >> I''m just getting started with puppet, and using the RPMS provided >> (on CentOS 4.3), and RedHat''s killproc is annoying me again. >> >> The process is called ''ruby'' instead of ''puppetmasterd''. >> >> $ ps 7869 >> PID TTY STAT TIME COMMAND >> 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] >> >> So, service puppetmaster restart|condrestart|stop all fail because RH is >> looking for a process called /usr/sbin/puppetmaster, and not ruby. >> >> I''m wondering if anyone else is having problems with this ? > > What version of puppet are you using ? There was a bug that lead to > those problems; that has been fixed in the specfile for 0.18.4-2 .. and > I just noticed that I haven''t rebuilt the RHEL rpm''s for that. I''ll > update my yum repo early next week. > > The trick is that /usr/sbin/puppetmasterd should say ''#! /usr/bin/ruby'' > in the first line instead of ''#! /usr/bin/env ruby''Yeah, I''m a genius for posting this message and not mentioning the version. I did indeed grab the SRPMs for 0.18.4-1, and rebuilt them myself. And you are exactly right. I''ll fix/update my end Monday. thanks, -sharif
On Sat, 2006-08-19 at 00:29 -0700, David Lutterkort wrote:> On Fri, 2006-08-18 at 20:04 -0700, Sharif Nassar wrote: > > > > Hi, > > > > I''m just getting started with puppet, and using the RPMS provided > > (on CentOS 4.3), and RedHat''s killproc is annoying me again. > > > > The process is called ''ruby'' instead of ''puppetmasterd''. > > > > $ ps 7869 > > PID TTY STAT TIME COMMAND > > 7869 ? Ss 0:00 ruby /usr/sbin/puppetmasterd [ etc ] > > > > So, service puppetmaster restart|condrestart|stop all fail because RH is > > looking for a process called /usr/sbin/puppetmaster, and not ruby. > > > > I''m wondering if anyone else is having problems with this ? > > What version of puppet are you using ? There was a bug that lead to > those problems; that has been fixed in the specfile for 0.18.4-2 .. and > I just noticed that I haven''t rebuilt the RHEL rpm''s for that. I''ll > update my yum repo early next week. > > The trick is that /usr/sbin/puppetmasterd should say ''#! /usr/bin/ruby'' > in the first line instead of ''#! /usr/bin/env ruby''I''d been wondering about this as well -- 0.18-2.1 certainly has this wrong and I''d been manually killing/restarting the puppet master. Glad to hear it''s been fixed. Updating puppet is now on my queue :-) jeff