Comment 20 for bug 1893993
Revision history for this message
| Corey Bryant (corey.bryant) wrote Re: [Bug 1893993] Re: juju unit logging defaults to WARNING and no python tracebacks at any log level | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
On Wed, Sep 9, 2020 at 1:25 PM John A Meinel <email address hidden>
wrote:
> INFO was the intentional default, and when I was bootstrapping and
> testing it, it is what I was seeing. I'm not sure where WARNING vs INFO
> is coming into play, but we can investigate.
>
> As far as the log messages:
> 2020-09-08 14:55:42 DEBUG juju.worker.logger logger.go:92 reconfiguring
> logging from "<root>=DEBUG" to "<root>=WARNING"
>
> All Agents default to DEBUG until the point they can connect to the
> controller and determine what their logging should be.
> If you are seeing that exact message, that means that for that agent, its
> configured logging is <root>=WARNING and not <root>=DEBUG.
>
>
I'm seeing that same log message. I'm not sure where it's getting set to
WARNING though.