10.14.4 broken output formatters?


#1

I’m playing with an upgrade to 10.14.4 (from 10.12)… and I noticed that when
I use “-F min”… in addition to one “.” per resource, I also get all the
normal INFO output for every resource I would normally get.

I seem to remember testing 10.14.0-rc and just getting dots.

Anyone else seeing this?


Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

#2

You’ve always needed to do -lfatal along with -Fdoc to spare the regular
output.

I’m sure Dan can explain why to us. :slight_smile:

Bryan
On Sep 28, 2012 9:53 PM, “Phil Dibowitz” phil@ipom.com wrote:

I’m playing with an upgrade to 10.14.4 (from 10.12)… and I noticed that
when
I use “-F min”… in addition to one “.” per resource, I also get all the
normal INFO output for every resource I would normally get.

I seem to remember testing 10.14.0-rc and just getting dots.

Anyone else seeing this?


Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

#3

On 09/28/2012 08:28 PM, Bryan McLellan wrote:

You’ve always needed to do -lfatal along with -Fdoc to spare the regular output.

I’m sure Dan can explain why to us. :slight_smile:

Ah. Indeed. Not intuitive, but accurate. Thanks!


Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

#4

You can put these in your client.rb:

log_level :fatal
formatter “min”

On Friday, September 28, 2012 at 19:53, Phil Dibowitz wrote:

I’m playing with an upgrade to 10.14.4 (from 10.12)… and I noticed that when
I use “-F min”… in addition to one “.” per resource, I also get all the
normal INFO output for every resource I would normally get.

I seem to remember testing 10.14.0-rc and just getting dots.

Anyone else seeing this?


Phil Dibowitz phil@ipom.commailto:phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

#5

On Sunday, September 30, 2012 at 6:06 PM, Joshua Timberman wrote:

You can put these in your client.rb:

log_level :fatal
formatter “min”

On Friday, September 28, 2012 at 19:53, Phil Dibowitz wrote:

I’m playing with an upgrade to 10.14.4 (from 10.12)… and I noticed that when
I use “-F min”… in addition to one “.” per resource, I also get all the
normal INFO output for every resource I would normally get.

I seem to remember testing 10.14.0-rc and just getting dots.

Anyone else seeing this?


Phil Dibowitz phil@ipom.com (mailto:phil@ipom.com)
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss

To reply to Bryan’s comment about logging vs. formatter output, the reason why it works this way now is simply that output formatters are a new feature that we’d like to have people test in the real world (before they become the default in Chef 11.0). When the formatter output does become the default, we need to decide what we do about the logger output.

Presently, my opinion is that the logger output should go to a logfile[0] (though I’m open to being convinced otherwise, if there are good arguments), but for a subset of users running Chef as a non-root user additional changes are required to make chef log to a location writable by non-root users. Rather than tackle these issues up-front, we decided to leave the choice up to users who are opting-in to using the formatter feature for now.

  1. e.g., chef-client -L/var/log/chef_client.log -Fmin (or -Fdoc, etc.)


Daniel DeLeo


#6

On 10/02/2012 09:28 AM, Daniel DeLeo wrote:

To reply to Bryan’s comment about logging vs. formatter output, the reason why
it works this way now is simply that output formatters are a new feature that
we’d like to have people test in the real world (before they become the
default in Chef 11.0). When the formatter output does become the default, we
need to decide what we do about the logger output.

Presently, my opinion is that the logger output should go to a logfile[0]
(though I’m open to being convinced otherwise, if there are good arguments),
but for a subset of users running Chef as a non-root user additional changes
are required to make chef log to a location writable by non-root users. Rather
than tackle these issues up-front, we decided to leave the choice up to users
who are opting-in to using the formatter feature for now.

  1. e.g., chef-client -L/var/log/chef_client.log -Fmin (or -Fdoc, etc.)

Well, the thing here that I missed and that I think most people will miss
until they look closely is that you’re always getting both because they are
two independent logging systems. So setting -lfatal just minimizes the logger
output so your formatter output isn’t trampled over.

Once I realized that, it all made more sense. :slight_smile:


Phil Dibowitz phil@ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/

“Be who you are and say what you feel, because those who mind don’t matter
and those who matter don’t mind.”

  • Dr. Seuss