[chef] RE: Re: Re: Re: Monitoring chef runs

[Paul McCallick < >]

Thanks everyone, it sounds like handlers are the way to go.

 

 

From: Tetsu Soh [mailto:
Sent: Thursday, September 06, 2012 7:53 AM
To:
Subject: [chef] Re: Re: Re: Monitoring chef runs

 

Hi,

 

well, it really depends on how you manage operations carried out by chef.

 

By running chef as daemon, chef will apply your changes in next time it runs.

So longer the interval between 2 converges is, more changes may be made.

And more changes you make once, more risk you have.

For example, if one recipes failed, all recipes after that will not be run.

So you need to figure out which one failed, fix it an run everything again.

 

OMP, running chef-client on demand will be a better solution. 

 

Regards,

 

Tetsu

 

On Sep 6, 2012, at 11:36 PM, Joshua Miller < "> > wrote:

Tetsu, can you elaborate on the concerns you've got for running chef-client as a daemon?

On Sep 6, 2012 7:26 AM, "Tetsu Soh" < "> > wrote:

Hello,

 

You can use exception handler to get runtime exception on your recipes.

 

To monitor chef-client process, you can use god, which is a process monitor written in Ruby.

 

btw, running chef-client as a daemon is not good in some case. be careful with that.

 

Regards,

 

Tetsu

 

On Sep 6, 2012, at 8:32 AM, Paul McCallick < " target="_blank"> > wrote:

Hi all,

 

We’re fairly new to chef and have been manually executing chef runs on one or many nodes.  We just made the move to run it as a service via the chef-client cookbook.

 

What’s the quickest way to make sure that we’re getting notified when there are problems during a chef run?  What’s the best way?

 

Thanks,

Paul