On Saturday, March 1, 2014 9:40:57 AM UTC-6, Jeff Bachtel wrote: > > While implementing restart is good, if for some reason you were unable to > do that you need only set *hasrestart => false* for the service resource, > per http://docs.puppetlabs.com/references/latest/type.html#service . That > will cause Puppet to issue a service stop then service start, instead of > attempting service restart. > > Jeff > > On 03/01/2014 08:55 AM, Robert Shady wrote: > > Sorry for such a delay in replies, I had figured this out and forgot about > this thread. ;) > > Yes, I did run it in debug mode and found out the problem was that > pdns-recursor > does not have a 'status' available, so puppet didn't know what to do. > > Quite true. And you can also specify a different restart procedure via the Service's 'restart' property.
None of that is directly relevant to the Service's 'status' command, however, which is where the OP reported the problem residing. Services really, really should have working 'status' commands. Moreover, although Puppet has a default method for trying to determine the status of a Service declared with hasstatus => false, it is just a best guess, unsuitable for some services. The good news is that you can also specify a custom 'status' command for your service in Puppet. If ever you need to declare hasstatus => false, I highly recommend explicitly declaring a 'status' command, too. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0c3badba-dbd3-46c7-8abc-e05a23123613%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
