Discussion:
Debug logs
Tom Barber
2017-11-26 00:25:13 UTC
Permalink
Maybe its just me, I dunno.

Has the amount of detail in debug-logs decreased?

I'm not seeing failure causes for example:

2017-11-26 00:11:18 INFO juju.worker.uniter resolver.go:104 found queued
"install" hook
2017-11-26 00:12:26 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:12:26 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:12:31 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:12:32 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:12:32 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:12:42 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:12:43 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:12:43 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:13:03 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:13:05 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:13:05 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:13:43 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:13:44 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:13:44 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:15:01 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:15:02 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:15:02 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:17:39 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:17:40 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
2017-11-26 00:17:40 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:21:42 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:22:40 INFO juju.worker.uniter resolver.go:100 awaiting error
resolution for "install" hook
2017-11-26 00:22:41 ERROR juju.worker.uniter.operation runhook.go:107 hook
"install" failed: exit status 1
--
Spicule Limited is registered in England & Wales. Company Number: 09954122.
Registered office: First Floor, Telecom House, 125-135 Preston Road,
Brighton, England, BN1 6AF. VAT No. 251478891.


All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to whom
it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or copying.
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Spicule Limited. The
company accepts no liability for any damage caused by any virus transmitted
by this email. If you have received this message in error, please notify us
immediately by reply email before deleting it from your system. Service of
legal notice cannot be effected on Spicule Limited by email.
Tim Penhey
2017-11-26 19:47:09 UTC
Permalink
What is the logging level for the model?

The output from the hooks are logged at debug level.

Tim
Post by Tom Barber
Maybe its just me, I dunno.
Has the amount of detail in debug-logs decreased?
2017-11-26 00:11:18 INFO juju.worker.uniter resolver.go:104 found queued
"install" hook
2017-11-26 00:12:26 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:12:26 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:31 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:32 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:12:32 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:42 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:43 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:12:43 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:03 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:05 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:13:05 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:43 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:44 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:13:44 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:15:01 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:15:02 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:15:02 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:17:39 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:17:40 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:17:40 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:21:42 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:22:40 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:22:41 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.
--
Juju mailing list
***@lists.ubuntu.com
Modify settings or unsubscribe a
Cory Johns
2017-12-04 14:36:02 UTC
Permalink
It seems that the default logging level for models was reduced some time
back. This makes the logs much less noisy and saves quite a bit of space,
but it has the unfortunate side effect of making debugging charm failures
from logs more difficult, as most failure messages only show up as stderr
output. It would probably be worth adding explicit logging of uncaught
exceptions to the reactive framework so that they are clearly visible in
the logs.

I've opened this as an issue against reactive here:
https://github.com/juju-solutions/charms.reactive/issues/147
Post by Tim Penhey
What is the logging level for the model?
The output from the hooks are logged at debug level.
Tim
Post by Tom Barber
Maybe its just me, I dunno.
Has the amount of detail in debug-logs decreased?
2017-11-26 00:11:18 INFO juju.worker.uniter resolver.go:104 found queued
"install" hook
2017-11-26 00:12:26 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:12:26 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:31 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:32 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:12:32 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:42 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:43 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:12:43 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:03 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:05 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:13:05 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:43 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:44 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:13:44 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:15:01 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:15:02 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:15:02 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:17:39 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:17:40 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
2017-11-26 00:17:40 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:21:42 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:22:40 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:22:41 ERROR juju.worker.uniter.operation runhook.go:107
hook "install" failed: exit status 1
09954122. Registered office: First Floor, Telecom House, 125-135 Preston
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to
whom it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of Spicule Limited.
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in error,
please notify us immediately by reply email before deleting it from your
system. Service of legal notice cannot be effected on Spicule Limited by
email.
--
Juju mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/
mailman/listinfo/juju
Tom Barber
2017-12-04 14:43:16 UTC
Permalink
Thanks Corey,

Its pretty unfriendly in terms of usability, I currently have to find
this thread every time I want to debug something. Maybe I'll stick it as
a bash alias or something.

I do remember the discussion about the noise, it does make sense, but
being able to change the levels more intuitively I think would help.

Tom
Post by Cory Johns
It seems that the default logging level for models was reduced some
time back.  This makes the logs much less noisy and saves quite a bit
of space, but it has the unfortunate side effect of making debugging
charm failures from logs more difficult, as most failure messages only
show up as stderr output.  It would probably be worth adding explicit
logging of uncaught exceptions to the reactive framework so that they
are clearly visible in the logs.
https://github.com/juju-solutions/charms.reactive/issues/147
What is the logging level for the model?
The output from the hooks are logged at debug level.
Tim
Post by Tom Barber
Maybe its just me, I dunno.
Has the amount of detail in debug-logs decreased?
2017-11-26 00:11:18 INFO juju.worker.uniter resolver.go:104
found queued
Post by Tom Barber
"install" hook
2017-11-26 00:12:26 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:12:26 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:31 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:32 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:12:32 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:42 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:12:43 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:12:43 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:03 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:05 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:13:05 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:43 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:13:44 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:13:44 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:15:01 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:15:02 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:15:02 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:17:39 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:17:40 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
2017-11-26 00:17:40 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:21:42 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:22:40 INFO juju.worker.uniter resolver.go:100 awaiting
error resolution for "install" hook
2017-11-26 00:22:41 ERROR juju.worker.uniter.operation
runhook.go:107
Post by Tom Barber
hook "install" failed: exit status 1
09954122. Registered office: First Floor, Telecom House, 125-135
Preston
Post by Tom Barber
Road, Brighton, England, BN1 6AF. VAT No. 251478891.
All engagements are subject to Spicule Terms and Conditions of
Business.
Post by Tom Barber
This email and its contents are intended solely for the
individual to
Post by Tom Barber
whom it is addressed and may contain information that is
confidential,
Post by Tom Barber
privileged or otherwise protected from disclosure, distributing or
copying. Any views or opinions presented in this email are
solely those
Post by Tom Barber
of the author and do not necessarily represent those of Spicule
Limited.
Post by Tom Barber
The company accepts no liability for any damage caused by any virus
transmitted by this email. If you have received this message in
error,
Post by Tom Barber
please notify us immediately by reply email before deleting it
from your
Post by Tom Barber
system. Service of legal notice cannot be effected on Spicule
Limited by
Post by Tom Barber
email.
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
<https://lists.ubuntu.com/mailman/listinfo/juju>
--
Spicule Limited is registered in England & Wales. Company Number: 09954122.
Registered office: First Floor, Telecom House, 125-135 Preston Road,
Brighton, England, BN1 6AF. VAT No. 251478891.


All engagements are subject to Spicule Terms and Conditions of Business.
This email and its contents are intended solely for the individual to whom
it is addressed and may contain information that is confidential,
privileged or otherwise protected from disclosure, distributing or copying.
Any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Spicule Limited. The
company accepts no liability for any damage caused by any virus transmitted
by this email. If you have received this message in error, please notify us
immediately by reply email before deleting it from your system. Service of
legal notice cannot be effected on Spicule Limited by email.
Loading...