Puppet users - Sep 2010 - service puppet status / /etc/init.d/puppet status

Hello All,

     I''m running puppet 0.25.5, and CentOS 5.4.  Whenever I run either
service puppet status or /etc/init.d/puppet status it tells me the
service is stopped when the service is actually running.  I remember
this being an issue w/ 0.25.4, but I thought it was addressed in
0.25.5.  Does anyone know how to circumvent this issue?  I know can
just do kill -9 $puppet_pid, but I rather do service puppet stop, or /
etc/init.d/puppet stop.

Thanks,

Henry

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Sep 23, 2010 at 9:00 AM, CraftyTech <hmmedina@gmail.com>
wrote:
> Hello All,
>
>     I''m running puppet 0.25.5, and CentOS 5.4.  Whenever I run
either
> service puppet status or /etc/init.d/puppet status it tells me the
> service is stopped when the service is actually running.  I remember
> this being an issue w/ 0.25.4, but I thought it was addressed in
> 0.25.5.  Does anyone know how to circumvent this issue?  I know can
> just do kill -9 $puppet_pid, but I rather do service puppet stop, or /
> etc/init.d/puppet stop.
Puppet is probably scanning the process table to determine if the
service is running or not.  I recommend making sure the init script
has a proper status method and then configure puppet to call the
status method using hasstatus => true in the service resource.

Hope this helps,
-- 
Jeff McCune
http://www.puppetlabs.com/

-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Thanks Jeff.. It was the location of the PID file that was holding me
back.  I fixed it in /etc/init.d/puppet, and then distributed via
puppet to the rest of the nodes.

Thanks,



On Sep 23, 12:32 pm, Jeff McCune <j...@puppetlabs.com>
wrote:
> On Thu, Sep 23, 2010 at 9:00 AM, CraftyTech <hmmed...@gmail.com>
wrote:
> > Hello All,
>
> >     I''m running puppet 0.25.5, and CentOS 5.4.  Whenever I
run either
> > service puppet status or /etc/init.d/puppet status it tells me the
> > service is stopped when the service is actually running.  I remember
> > this being an issue w/ 0.25.4, but I thought it was addressed in
> > 0.25.5.  Does anyone know how to circumvent this issue?  I know can
> > just do kill -9 $puppet_pid, but I rather do service puppet stop, or /
> > etc/init.d/puppet stop.
>
> Puppet is probably scanning the process table to determine if the
> service is running or not.  I recommend making sure the init script
> has a proper status method and then configure puppet to call the
> status method using hasstatus => true in the service resource.
>
> Hope this helps,
> --
> Jeff McCunehttp://www.puppetlabs.com/
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hi Henry,

what was exactly wrong with your PID file? It seems i have a very
similar problem with the init.d puppetd stop start service. I checked
the PIDFILE path and the file was written correctly there. Also a
process id is written in that file.

Christian

On 23 Sep., 22:28, CraftyTech <hmmed...@gmail.com>
wrote:
> Thanks Jeff.. It was the location of the PID file that was holding me
> back.  I fixed it in /etc/init.d/puppet, and then distributed via
> puppet to the rest of the nodes.
>
> Thanks,
>
> On Sep 23, 12:32 pm, Jeff McCune <j...@puppetlabs.com> wrote:
>
> > On Thu, Sep 23, 2010 at 9:00 AM, CraftyTech <hmmed...@gmail.com>
wrote:
> > > Hello All,
>
> > >     I''m running puppet 0.25.5, and CentOS 5.4.  Whenever
I run either
> > > service puppet status or /etc/init.d/puppet status it tells me
the
> > > service is stopped when the service is actually running.  I
remember
> > > this being an issue w/ 0.25.4, but I thought it was addressed in
> > > 0.25.5.  Does anyone know how to circumvent this issue?  I know
can
> > > just do kill -9 $puppet_pid, but I rather do service puppet stop,
or /
> > > etc/init.d/puppet stop.
>
> > Puppet is probably scanning the process table to determine if the
> > service is running or not.  I recommend making sure the init script
> > has a proper status method and then configure puppet to call the
> > status method using hasstatus => true in the service resource.
>
> > Hope this helps,
> > --
> > Jeff McCunehttp://www.puppetlabs.com/
>
>
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hello Chris,

     For me it was just the path to the pid file from puppet''s init
script.  If I was you, I''d check the location of the lock file, and
the executable as well.  Otherwise, you should try Jeff''s suggestion.
Hope it helps.

Cheers,

Henry

On Sep 24, 3:32 am, Christian <berwangerchrist...@googlemail.com>
wrote:
> Hi Henry,
>
> what was exactly wrong with your PID file? It seems i have a very
> similar problem with the init.d puppetd stop start service. I checked
> the PIDFILE path and the file was written correctly there. Also a
> process id is written in that file.
>
> Christian
>
> On 23 Sep., 22:28, CraftyTech <hmmed...@gmail.com> wrote:
>
>
>
> > Thanks Jeff.. It was the location of the PID file that was holding me
> > back.  I fixed it in /etc/init.d/puppet, and then distributed via
> > puppet to the rest of the nodes.
>
> > Thanks,
>
> > On Sep 23, 12:32 pm, Jeff McCune <j...@puppetlabs.com> wrote:
>
> > > On Thu, Sep 23, 2010 at 9:00 AM, CraftyTech
<hmmed...@gmail.com> wrote:
> > > > Hello All,
>
> > > >     I''m running puppet 0.25.5, and CentOS 5.4.
 Whenever I run either
> > > > service puppet status or /etc/init.d/puppet status it tells
me the
> > > > service is stopped when the service is actually running.  I
remember
> > > > this being an issue w/ 0.25.4, but I thought it was
addressed in
> > > > 0.25.5.  Does anyone know how to circumvent this issue?  I
know can
> > > > just do kill -9 $puppet_pid, but I rather do service puppet
stop, or /
> > > > etc/init.d/puppet stop.
>
> > > Puppet is probably scanning the process table to determine if the
> > > service is running or not.  I recommend making sure the init
script
> > > has a proper status method and then configure puppet to call the
> > > status method using hasstatus => true in the service resource.
>
> > > Hope this helps,
> > > --
> > > Jeff McCunehttp://www.puppetlabs.com/
-- 
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.