Debug logs
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. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Debug logs
What is the logging level for the model? The output from the hooks are logged at debug level. Tim On 26/11/17 13:25, Tom Barber wrote: > 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. > > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Debug logs
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 On Sun, Nov 26, 2017 at 2:47 PM, Tim Penhey wrote: > What is the logging level for the model? > > The output from the hooks are logged at debug level. > > Tim > > On 26/11/17 13:25, Tom Barber wrote: > > 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. > > > > > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Debug logs
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 On 04/12/17 14:36, Cory Johns wrote: 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 On Sun, Nov 26, 2017 at 2:47 PM, Tim Penhey <mailto:tim.pen...@canonical.com>> wrote: What is the logging level for the model? The output from the hooks are logged at debug level. Tim On 26/11/17 13:25, Tom Barber wrote: > 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. > Thi