# Strategies for updating chef trough a chef recipe

**URL:** <https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558>\
**Category:** Chef Infra (archive)\
**Created:** [September 21, 2010, 9:32am UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558 "2010-09-21T09:32:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jacobo\_Garcia](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jacobo_garcia/32/533_2.png) [@Jacobo\_Garcia](https://discourse.chef.io/u/Jacobo_Garcia)\
**Post date:** [September 21, 2010, 9:32am UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/1 "2010-09-21T09:32:07Z")

</div>

Hi,

I’m trying to update all my chef-clients trough a chef recipe, I’m using a  
modified recipe based on opscode’s chef cookbook,

What I’m trying to do is pretty simple:

> <https://gist.github.com/therobot/2fd4fce806aa0c33edb0>

I’m having problems on the first chef run, I use to login to the machine and  
run chef-client as root, then the run hangs (chef does not get restarted)  
and I get the following error:

[Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef] version  
0.9.8  
[Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending restart  
action to service[chef-client] (immediate)  
[Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
[Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
[Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
[Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception: SystemExit -  
exit

If I restart chef as delayed on the recipe I have the same problem but at  
the end of the run.

I am looking some help on the debug or some (better) strategies on auto  
updating chef through minor releases.

Thanks.

Jacobo García López de Araujo  
blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
[http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)

---

<div class="post-metadata">

**Author:** ![Dreamcat4](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/dreamcat4/32/288_2.png) [@Dreamcat4](https://discourse.chef.io/u/Dreamcat4)\
**Post date:** [September 21, 2010, 4:28pm UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/2 "2010-09-21T16:28:22Z")

</div>

Hi Jacobo,

Theres already a chef restart recipe in my cookbooks repository. Its  
been tested and works perfectly with chef-solo. For restarting  
chef-client im unsure how to tackle that. But would very much like to  
see such capability incorporated into the recipe.

> <https://github.com/dreamcat4/site-cookbooks/tree/master/restart/>
>
> //github.com/dreamcat4/site-cookbooks/tree/master/restart/

On Tue, Sep 21, 2010 at 10:32 AM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com) wrote:

> Hi,  
> I'm trying to update all my chef-clients trough a chef recipe, I'm using a  
> modified recipe based on opscode's chef cookbook,  
> What I'm trying to do is pretty simple:  
> [gist:2fd4fce806aa0c33edb0 · GitHub](https://gist.github.com/2fd4fce806aa0c33edb0)  
> I'm having problems on the first chef run, I use to login to the machine and  
> run chef-client as root, then the run hangs (chef does not get restarted)  
> and I get the following error:  
> [Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef] version  
> 0.9.8  
> [Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending restart  
> action to service[chef-client] (immediate)  
> [Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
> [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
> [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
> [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception: SystemExit -  
> exit  
> If I restart chef as delayed on the recipe I have the same problem but at  
> the end of the run.  
> I am looking some help on the debug or some (better) strategies on auto  
> updating chef through minor releases.  
> Thanks.  
> Jacobo García López de Araujo  
> blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)

---

<div class="post-metadata">

**Author:** ![Adam\_Jacob](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/adam_jacob/32/292_2.png) [@Adam\_Jacob](https://discourse.chef.io/u/Adam_Jacob)\
**Post date:** [September 21, 2010, 6:04pm UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/3 "2010-09-21T18:04:41Z")

</div>

This is off the top of my head, but the most brute-force way possible  
would be this:

ruby\_block "replace me with a new process" do  
block do  
exec($0 + ARGV)  
end  
end

And make sure it is the last thing.

We use something like runit, so when the daemon exits, it restarts  
automatically, and a resource like this isn't required.

Adam

On Tue, Sep 21, 2010 at 2:32 AM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com) wrote:

> Hi,  
> I'm trying to update all my chef-clients trough a chef recipe, I'm using a  
> modified recipe based on opscode's chef cookbook,  
> What I'm trying to do is pretty simple:  
> [gist:2fd4fce806aa0c33edb0 · GitHub](https://gist.github.com/2fd4fce806aa0c33edb0)  
> I'm having problems on the first chef run, I use to login to the machine and  
> run chef-client as root, then the run hangs (chef does not get restarted)  
> and I get the following error:  
> [Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef] version  
> 0.9.8  
> [Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending restart  
> action to service[chef-client] (immediate)  
> [Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
> [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
> [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
> [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception: SystemExit -  
> exit  
> If I restart chef as delayed on the recipe I have the same problem but at  
> the end of the run.  
> I am looking some help on the debug or some (better) strategies on auto  
> updating chef through minor releases.  
> Thanks.  
> Jacobo García López de Araujo  
> blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)

--  
Opscode, Inc.  
Adam Jacob, CTO  
T: (206) 508-7449 E: [adam@opscode.com](mailto:adam@opscode.com)

---

<div class="post-metadata">

**Author:** ![Jacobo\_Garcia](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jacobo_garcia/32/533_2.png) [@Jacobo\_Garcia](https://discourse.chef.io/u/Jacobo_Garcia)\
**Post date:** [September 21, 2010, 10:22pm UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/4 "2010-09-21T22:22:06Z")

</div>

Thanks for the answers, your help is quite appreciated.

I'm trying dreamcat4 restart recipe with just a little success.

I get this error:

/var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize': wrong number of arguments (3 for 2) (ArgumentError) from /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize'

I am just running:

restart "login\_shell"

I'm using chef 0.9.0.

Jacobo García López de Araujo  
blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
[http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)

On Tue, Sep 21, 2010 at 8:04 PM, Adam Jacob [adam@opscode.com](mailto:adam@opscode.com) wrote:

> This is off the top of my head, but the most brute-force way possible  
> would be this:
> 
> ruby\_block "replace me with a new process" do  
> block do  
> exec($0 + ARGV)  
> end  
> end
> 
> And make sure it is the last thing.
> 
> We use something like runit, so when the daemon exits, it restarts  
> automatically, and a resource like this isn't required.
> 
> Adam
> 
> On Tue, Sep 21, 2010 at 2:32 AM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com)  
> wrote:
> 
> > Hi,  
> > I'm trying to update all my chef-clients trough a chef recipe, I'm using  
> > a  
> > modified recipe based on opscode's chef cookbook,  
> > What I'm trying to do is pretty simple:  
> > [gist:2fd4fce806aa0c33edb0 · GitHub](https://gist.github.com/2fd4fce806aa0c33edb0)  
> > I'm having problems on the first chef run, I use to login to the machine  
> > and  
> > run chef-client as root, then the run hangs (chef does not get restarted)  
> > and I get the following error:  
> > [Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef]  
> > version  
> > 0.9.8  
> > [Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending restart  
> > action to service[chef-client] (immediate)  
> > [Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
> > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
> > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
> > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception: SystemExit
> 
> - 
> 
> > exit  
> > If I restart chef as delayed on the recipe I have the same problem but at  
> > the end of the run.  
> > I am looking some help on the debug or some (better) strategies on auto  
> > updating chef through minor releases.  
> > Thanks.  
> > Jacobo García López de Araujo  
> > blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> > [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> 
> --  
> Opscode, Inc.  
> Adam Jacob, CTO  
> T: (206) 508-7449 E: [adam@opscode.com](mailto:adam@opscode.com)

---

<div class="post-metadata">

**Author:** ![Gilles\_Devaux](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/gilles_devaux/32/744_2.png) [@Gilles\_Devaux](https://discourse.chef.io/u/Gilles_Devaux)\
**Post date:** [September 22, 2010, 12:14am UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/5 "2010-09-22T00:14:49Z")

</div>

if you are using the 'init' method the chef-client init.d script have  
an error up to 0.9.10:  
[http://tickets.opscode.com/browse/CHEF-1584](http://tickets.opscode.com/browse/CHEF-1584)  
-\> will prevent the restart action of the chef-client service.

SIGTERM seems harsh though...

On Tue, Sep 21, 2010 at 3:22 PM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com) wrote:

> Thanks for the answers, your help is quite appreciated.  
> I'm trying dreamcat4 restart recipe with just a little success.  
> I get this error:  
> /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize': wrong number of arguments (3 for 2) (ArgumentError) from /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize'  
> I am just running:  
> restart "login\_shell"  
> I'm using chef 0.9.0.  
> Jacobo García López de Araujo  
> blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> 
> On Tue, Sep 21, 2010 at 8:04 PM, Adam Jacob [adam@opscode.com](mailto:adam@opscode.com) wrote:
> 
> > This is off the top of my head, but the most brute-force way possible  
> > would be this:
> > 
> > ruby\_block "replace me with a new process" do  
> > block do  
> > exec($0 + ARGV)  
> > end  
> > end
> > 
> > And make sure it is the last thing.
> > 
> > We use something like runit, so when the daemon exits, it restarts  
> > automatically, and a resource like this isn't required.
> > 
> > Adam
> > 
> > On Tue, Sep 21, 2010 at 2:32 AM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com)  
> > wrote:
> > 
> > > Hi,  
> > > I'm trying to update all my chef-clients trough a chef recipe, I'm using  
> > > a  
> > > modified recipe based on opscode's chef cookbook,  
> > > What I'm trying to do is pretty simple:  
> > > [gist:2fd4fce806aa0c33edb0 · GitHub](https://gist.github.com/2fd4fce806aa0c33edb0)  
> > > I'm having problems on the first chef run, I use to login to the machine  
> > > and  
> > > run chef-client as root, then the run hangs (chef does not get  
> > > restarted)  
> > > and I get the following error:  
> > > [Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef]  
> > > version  
> > > 0.9.8  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending  
> > > restart  
> > > action to service[chef-client] (immediate)  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception:  
> > > SystemExit -  
> > > exit  
> > > If I restart chef as delayed on the recipe I have the same problem but  
> > > at  
> > > the end of the run.  
> > > I am looking some help on the debug or some (better) strategies on auto  
> > > updating chef through minor releases.  
> > > Thanks.  
> > > Jacobo García López de Araujo  
> > > blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> > > [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> > 
> > --  
> > Opscode, Inc.  
> > Adam Jacob, CTO  
> > T: (206) 508-7449 E: [adam@opscode.com](mailto:adam@opscode.com)

---

<div class="post-metadata">

**Author:** ![Dreamcat4](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/dreamcat4/32/288_2.png) [@Dreamcat4](https://discourse.chef.io/u/Dreamcat4)\
**Post date:** [September 22, 2010, 2:30pm UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/6 "2010-09-22T14:30:26Z")

</div>

Hi Jacobo  
Near where that line is referenced, change it to this:

```
  # def initialize(name, collection=nil, node=nil)
  # super(name, collection, node)
  def initialize(name, run_context=nil)
    super(name, run_context)
    @resource_name = :restart
    @context = name || "node"
    @shell = nil

```

And should run. Heres the command I used:

$ chef-solo -c /srv/chef/site-cookbooks/restart/files/default/solo.rb  
-j /srv/chef/site-cookbooks/restart/files/default/example.json

as Scotty might say: T'was a mighty core change in the arguments of  
the base class resource initializer function that broke it.

Commit:

> <https://github.com/chef/chef/commit/8403e879048cf5122b36637f0ec28ca7be8392ff#L0L38>

On Tue, Sep 21, 2010 at 11:22 PM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com) wrote:

> Thanks for the answers, your help is quite appreciated.  
> I'm trying dreamcat4 restart recipe with just a little success.  
> I get this error:  
> /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize': wrong number of arguments (3 for 2) (ArgumentError) from /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize'  
> I am just running:  
> restart "login\_shell"  
> I'm using chef 0.9.0.  
> Jacobo García López de Araujo  
> blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> 
> On Tue, Sep 21, 2010 at 8:04 PM, Adam Jacob [adam@opscode.com](mailto:adam@opscode.com) wrote:
> 
> > This is off the top of my head, but the most brute-force way possible  
> > would be this:
> > 
> > ruby\_block "replace me with a new process" do  
> > block do  
> > exec($0 + ARGV)  
> > end  
> > end
> > 
> > And make sure it is the last thing.
> > 
> > We use something like runit, so when the daemon exits, it restarts  
> > automatically, and a resource like this isn't required.
> > 
> > Adam
> > 
> > On Tue, Sep 21, 2010 at 2:32 AM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com)  
> > wrote:
> > 
> > > Hi,  
> > > I'm trying to update all my chef-clients trough a chef recipe, I'm using  
> > > a  
> > > modified recipe based on opscode's chef cookbook,  
> > > What I'm trying to do is pretty simple:  
> > > [gist:2fd4fce806aa0c33edb0 · GitHub](https://gist.github.com/2fd4fce806aa0c33edb0)  
> > > I'm having problems on the first chef run, I use to login to the machine  
> > > and  
> > > run chef-client as root, then the run hangs (chef does not get  
> > > restarted)  
> > > and I get the following error:  
> > > [Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef]  
> > > version  
> > > 0.9.8  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending  
> > > restart  
> > > action to service[chef-client] (immediate)  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
> > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception:  
> > > SystemExit -  
> > > exit  
> > > If I restart chef as delayed on the recipe I have the same problem but  
> > > at  
> > > the end of the run.  
> > > I am looking some help on the debug or some (better) strategies on auto  
> > > updating chef through minor releases.  
> > > Thanks.  
> > > Jacobo García López de Araujo  
> > > blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> > > [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> > 
> > --  
> > Opscode, Inc.  
> > Adam Jacob, CTO  
> > T: (206) 508-7449 E: [adam@opscode.com](mailto:adam@opscode.com)

---

<div class="post-metadata">

**Author:** ![Jacobo\_Garcia](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jacobo_garcia/32/533_2.png) [@Jacobo\_Garcia](https://discourse.chef.io/u/Jacobo_Garcia)\
**Post date:** [September 23, 2010, 5:39pm UTC](https://discourse.chef.io/t/strategies-for-updating-chef-trough-a-chef-recipe/1558/7 "2010-09-23T17:39:13Z")

</div>

Hi,

After that subtle change, its at least, partially working. I'll update the  
thread if I find anything interesting.

Thanks!

Jacobo García López de Araujo  
blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
[http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)

On Wed, Sep 22, 2010 at 4:30 PM, Dreamcat4 [dreamcat4@gmail.com](mailto:dreamcat4@gmail.com) wrote:

> Hi Jacobo  
> Near where that line is referenced, change it to this:
> 
> ```
> # def initialize(name, collection=nil, node=nil)
> # super(name, collection, node)
> def initialize(name, run_context=nil)
> super(name, run_context)
> @resource_name = :restart
> @context = name || "node"
> @shell = nil
> 
> ```
> 
> And should run. Heres the command I used:
> 
> $ chef-solo -c /srv/chef/site-cookbooks/restart/files/default/solo.rb  
> -j /srv/chef/site-cookbooks/restart/files/default/example.json
> 
> as Scotty might say: T'was a mighty core change in the arguments of  
> the base class resource initializer function that broke it.
> 
> Commit:
> 
> [Making Chef::Resource consume the new Chef::RunContext object, as wel… · chef/chef@8403e87 · GitHub](http://github.com/opscode/chef/commit/8403e879048cf5122b36637f0ec28ca7be8392ff#L0L38)
> 
> On Tue, Sep 21, 2010 at 11:22 PM, Jacobo García [jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com)  
> wrote:
> 
> > Thanks for the answers, your help is quite appreciated.  
> > I'm trying dreamcat4 restart recipe with just a little success.  
> > I get this error:  
> > /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in  
> > `initialize': wrong number of arguments (3 for 2) (ArgumentError) from /var/chef/cache/cookbooks/restart/libraries/restart.rb:54:in `initialize'  
> > I am just running:  
> > restart "login\_shell"  
> > I'm using chef 0.9.0.  
> > Jacobo García López de Araujo  
> > blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> > [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> > 
> > On Tue, Sep 21, 2010 at 8:04 PM, Adam Jacob [adam@opscode.com](mailto:adam@opscode.com) wrote:
> > 
> > > This is off the top of my head, but the most brute-force way possible  
> > > would be this:
> > > 
> > > ruby\_block "replace me with a new process" do  
> > > block do  
> > > exec($0 + ARGV)  
> > > end  
> > > end
> > > 
> > > And make sure it is the last thing.
> > > 
> > > We use something like runit, so when the daemon exits, it restarts  
> > > automatically, and a resource like this isn't required.
> > > 
> > > Adam
> > > 
> > > On Tue, Sep 21, 2010 at 2:32 AM, Jacobo García \<[jacobo.garcia@gmail.com](mailto:jacobo.garcia@gmail.com)
> > 
> > > wrote:
> > > 
> > > > Hi,  
> > > > I'm trying to update all my chef-clients trough a chef recipe, I'm  
> > > > using  
> > > > a  
> > > > modified recipe based on opscode's chef cookbook,  
> > > > What I'm trying to do is pretty simple:  
> > > > [gist:2fd4fce806aa0c33edb0 · GitHub](https://gist.github.com/2fd4fce806aa0c33edb0)  
> > > > I'm having problems on the first chef run, I use to login to the  
> > > > machine  
> > > > and  
> > > > run chef-client as root, then the run hangs (chef does not get  
> > > > restarted)  
> > > > and I get the following error:  
> > > > [Mon, 20 Sep 2010 20:33:02 +0000] INFO: Installing gem\_package[chef]  
> > > > version  
> > > > 0.9.8  
> > > > [Mon, 20 Sep 2010 20:33:24 +0000] INFO: gem\_package[chef] sending  
> > > > restart  
> > > > action to service[chef-client] (immediate)  
> > > > [Mon, 20 Sep 2010 20:33:24 +0000] FATAL: SIGTERM received, stopping  
> > > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Running exception handlers  
> > > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Exception handlers complete  
> > > > [Mon, 20 Sep 2010 20:33:24 +0000] ERROR: Re-raising exception:  
> > > > SystemExit -  
> > > > exit  
> > > > If I restart chef as delayed on the recipe I have the same problem but  
> > > > at  
> > > > the end of the run.  
> > > > I am looking some help on the debug or some (better) strategies on  
> > > > auto  
> > > > updating chef through minor releases.  
> > > > Thanks.  
> > > > Jacobo García López de Araujo  
> > > > blog: [http://robotplaysguitar.com](http://robotplaysguitar.com)  
> > > > [http://workingwithrails.com/person/13395-jacobo-garc-a](http://workingwithrails.com/person/13395-jacobo-garc-a)
> > > 
> > > --  
> > > Opscode, Inc.  
> > > Adam Jacob, CTO  
> > > T: (206) 508-7449 E: [adam@opscode.com](mailto:adam@opscode.com)