On 11 July 2011 14:54, Dominic Cleal <dcl...@redhat.com> wrote:
> On 11/07/11 09:18, Chris Phillips wrote:
> > Coming into work this morning I've seen a bunch of func processes have
> > stopped and puppet is doing nothing at all about it, despite a manifest
> > advising something else:
> >
> > Manifest says -
> >
> > service { "funcd":
> > ensure => running,
> > enable => true,
> > subscribe => File["/etc/func/minion.conf"],
> > require => Package["func"],
> > hasrestart => true,
> > hasstatus => true
> > }
> >
> >
> > Puppet run is not interested, thinks it's still running? -
> >
> > debug: Service[funcd](provider=redhat): Executing '/sbin/service funcd
> > status'
> > debug: Puppet::Type::Service::ProviderRedhat: Executing '/sbin/chkconfig
> > funcd'
> >
> > However as per the puppet service being turned off when it already is,
> > this is being left off when it should be being turned on - i.e. in both
> > situations it is thinking it is running when it is not - and the init
> > script CONFIRMS that it is NOT running, just like it does with puppet.
>
> Is the init.d 'status' script returning a non-zero exit code? I've seen
> bugs before with scripts that report on stdout that the process isn't
> running, but failed to return the correct exit code (e.g. 1 or 3 for LSB).
>
>
Yes in both cases the status is returned as a 3, which is correct for a
stopped service
Cheers
Chris
--
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.
