[chef] Re: chef-client not started

[Eric Herot < >]

The "solution" I came up with was to send an email instructing the admin to restart the chef-client (but note that if this accidentally runs during a convergence, you will end up with a stopped chef-client service like you have now).  Other possibilities include setting a cron job to bounce it occasionally, or running the whole convergence from cron (you will lose the splay factor).  Unfortunately it seems like it is quite impossible to successfully bounce chef from within chef, at least as currently written.

One possibility for why it doesn't always happen is that it isn't always finding a reason to notify => restart the chef-client service...

On Jan 16, 2014, at 12:38 PM, Cyril Scetbon < "> > wrote:

yep it looks really similar. But why it works now that's the question :D

-- 
Cyril SCETBON

On 16 Jan 2014, at 18:14, Eric Herot < "> > wrote:

It could be related to this issue:

https://tickets.opscode.com/browse/COOK-1825

On Jan 16, 2014, at 11:53 AM, Cyril Scetbon < "> > wrote:

Hi,

I'm trying to deploy and start chef-client using recipe chef-client. It doesn't work with cookbook version 3.2.0 and chef 11.8.2. That is to say, chef-client does not start at the end even if it says :

* service[chef-client] action enable
- enable service service[chef-client]

* service[chef-client] action start
- start service service[chef-client]

* service[chef-client] action restart
- restart service service[chef-client]

Chef Client finished, 10 resources updated

at the end of the deployment.

However, if I use cookbook version 1.2.0 it works as expected !

:~$"> :~$ ps -ef|grep -i chef
root 3232 1 0 16:10 ? 00:00:00 /opt/chef/embedded/bin/ruby /usr/bin/chef-client -d -P /var/run/chef/client.pid -c /etc/chef/client.rb -i 1800 -s 300 -L /var/log/chef/client.log

outputs of chef are the same with both versions but not the results.

Thanks
--
Cyril SCETBON