[chef] Re: Trouble reloading a service

[AJ Christensen < >]

What platform? I think the Redhat service provider has supports
:status forced to 'true' always or something dumb like that.

Can you show the full -l debug stack trace regarding your provider
taking action?

--AJ

On 21 July 2012 11:20, Allan Wind 
<
 >
 wrote:
> I am restarting a service with chef 0.10.4 along these lines:
>
> template '/etc/logfmon.conf' do
>         notifies :restart, 'service[logfmon]'
>         ...
> end
>
>
> service 'logfmon' do
>         action [:enable, :start]
>         supports :reload => true, :restart => true, :status => false
> end
>
> and this works just fine:
>
>  ** [out :: s2.leadkarma.com] [Fri, 20 Jul 2012 23:13:39 +0000] INFO: 
> template[/etc/logfmon.conf] sending restart action to service[logfmon] 
> (delayed)
>  ** [out :: s2.leadkarma.com] [Fri, 20 Jul 2012 23:13:39 +0000] INFO: 
> Processing service[logfmon] action restart (logfmon::default line 61)
>  ** [out :: s2.leadkarma.com] [Fri, 20 Jul 2012 23:13:39 +0000] DEBUG: 
> service[logfmon] supports status, running
>  ** [out :: s2.leadkarma.com] [Fri, 20 Jul 2012 23:13:40 +0000] INFO: 
> service[logfmon] restarted
>
> and my service is being called:
>
> status
> status
> start
> status
> restart
>
> It is weird that "supports ... :status => false" is not honored, but more 
> trouble is that
> changing the notifies :restart to :reload means that only these commands 
> are issued to
> my init script (i.e. not reload):
>
> status
> status
> start
> status
>
> Any ideas?
>
>
> /Allan
> --
> Allan Wind
> Life Integrity, LLC
> <http://lifeintegrity.com>