- From: Albert Llop <
>
- To:
- Subject: [chef] Re: Problem when starting and stoping chef-client as init service
- Date: Tue, 13 Jul 2010 13:07:39 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=xd1YPF+891b+XWSn5b5gvDr+rgjFtQhpWf1eKcQeQwFfqz+5xwggjvnnmlWbRzrTFu vwEIuXI8sK9vASmkMXD3DoHzSRaiA5ZPVxLCpr0cjy9bkCroIvkw/wENoXDfpj23Ycnm jsR+ygmLFIn3jBBrDVIxvzSZL2Tognaj3eqx4=
Hola Jacobo!
Check the pidfile variable in /etc/init.d/chef-client and see if it's the same than in /etc/chef/client.rb. Otherwise when starting the client it will create the pidfile where specified in the /etc/chef/client.rb configuration, but will try to stop it checking the pidfile specified in the init.d one.
:D hope it helps
--
{ :name => "Albert Llop" }
On 13 July 2010 12:58, Jacobo García
<
">
> wrote:
Hi chefs,
I'm having a problem when using chef debian init scripts. The
screenshot attached explains it better. The problem is that chef init
script does not behave consistently; It does not stop chef-client when
you try it but returns success, you have to manually kill chef-client.
It returns fail when starting it but the client is started.
I've seen this behavior at least on 0.8.16 and 0.9.0 also on both
ubuntu 8.04 and 10.04.
Is it a bug on the script?, does anyone know about this problem?.
Thanks in advance.
Jacobo García López de Araujo
blog: http://robotplaysguitar.com
http://workingwithrails.com/person/13395-jacobo-garc-a
Archive powered by MHonArc 2.6.16.