Surely it would be obvious with debug logging. :-)
On Jun 13, 2011 5:48 PM, "Jason J. W. Williams" <
">
> wrote:
> That helped. Turns out also that my git :sync on the repo is
> triggering the restart:
>
> git "/git/programname" do
> repository "<redacted>"
> reference node[:programname][:version]
> ssh_wrapper "/usr/bin/deploy-ssh-wrapper.sh"
> action :sync
> notifies :restart, "service[programname]"
> end
>
> Is there anyway to keep it from triggering a notifies event if the
> repo hasn't changed?
>
> -J
>
> On Mon, Jun 13, 2011 at 6:21 PM, AJ Christensen <
">
> wrote:
>> Use supports :status to check the init script for status, or specify a
>> pattern for the default "ps and grep" behavior
>>
>> On Jun 13, 2011 5:19 PM, "Jason J. W. Williams" <
">
>
>> wrote:
>>> I've been noticing that at least one of my cookbooks is causing the
>>> associated service to be restarted everytime chef runs. None of the
>>> config files that trigger "notifies" are being changed and the Chef
>>> logs confirm that. The only thing that seems to be triggering the
>>> restart is:
>>>
>>> service "programname" do
>>> action [:enable, :start]
>>> supports :restart => true
>>> end
>>>
>>> In the logs:
>>>
>>> [Tue, 14 Jun 2011 00:14:27 +0000] INFO: Processing
>>> service[programname] action enable (programname::default line 86)
>>> [Tue, 14 Jun 2011 00:14:27 +0000] INFO: Processing
>>> service[programname] action start (programname::default line 86)
>>>
>>> The service is restarting properly, but interrupting active sessions
>>> every 15 minutes is not acceptable. How can I keep Chef from
>>> restarting the process unless something has changed?
>>>
>>> -J
>>