On Aug 31, 2011, at 1:47 PM, David Nalley wrote:
> On Wed, Aug 31, 2011 at 4:43 PM, Craig White <craig.wh...@ttiltd.com> wrote:
>> Seems that every cycle, puppet thinks that bind9 service is stopped and
>> wants to restart...
>>
>> info: Applying configuration version '1314822598'
>> notice: /Stage[main]/Bind::Service/Service[bind9]/ensure: ensure changed
>> 'stopped' to 'running'
>> notice: Finished catalog run in 3.70 seconds
>>
>> But it's running and from the logs, puppet doesn't appear to have any impact
>> at all (bind9 was running, continues to run and is not restarted by the
>> puppet cycle).
>>
>> # /etc/init.d/bind9 status
>> * bind9 is running
>>
>> # update-rc.d -n bind9 defaults
>> System start/stop links for /etc/init.d/bind9 already exist.
>>
>> # ps aux | grep `cat /var/run/named/named.pid`|grep -v grep
>> bind 21856 0.0 0.2 326644 39664 ? Ssl Aug26 0:17
>> /usr/sbin/named -u bind
>>
>> Extremely simple class...
>> class bind::service {
>> service { "bind9":
>> ensure => running,
>> require => Class["bind::install"],
>> }
>> }
>>
>> ???
>>
>
>
> I think the issue is that you need to have hasstatus in your service
> definition. Otherwise puppet will think that it can't check to see if
> it's running.
----
yes, that's what I get for not checking out other 'service.pp' files I have
done in the past.
hasrestart => true,
is also useful ;-)
Thanks
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.
