[chef] Re: Strategies for updating chef trough a chef recipe

[Adam Jacob < >]

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 
<
 >
 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:
> 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://workingwithrails.com/person/13395-jacobo-garc-a
>
>



-- 
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: