[chef] Re: Re: Re: Grepping chef-client output


Chronological Thread 
  • From: Dylan Northrup < >
  • To:
  • Subject: [chef] Re: Re: Re: Grepping chef-client output
  • Date: Fri, 1 Mar 2013 18:04:38 -0500

Nope.  I don't get any of the INFO lines when I do that.

On Fri, Mar 1, 2013 at 2:46 PM, Andrew Gross < " target="_blank"> > wrote:
Is this just an issue with greps buffering?  Does it work if you use

grep --line-buffered -v [WARN]


On Fri, Mar 1, 2013 at 2:39 PM, Mike < " target="_blank"> > wrote:
Change log_level :info
to
log_level :warn

for one run?

That's an easy way. :)

On Fri, Mar 1, 2013 at 1:37 PM, Dylan Northrup < " target="_blank"> > wrote:
> Running chef-client 10.24.0 on some hosts I get a veritable deluge of WARN
> messages about things that aren't being done quite right and should be
> changed (many things, I'll add, that had not issued WARN messages in prior
> versions of chef-client).  I'd like to be able to grep out those WARN
> messages, but when I do it kills all chef-client output.  Trying to redirect
> STDERR doesn't make a difference.
>
> Is there a best practice way of filtering chef-client output?
>
> --
> Dylan Northrup





Archive powered by MHonArc 2.6.16.

§