search

theotherp / nzbhydra2

Usenet meta search
Other
1.23k stars 75 forks source link

BUG: You have more than 3 logging markers enabled Warning when saving config #886

Open viptampa opened 1 year ago

viptampa commented 1 year ago

I've downloaded and attached the debug file as I've seen recommended on reddit before. nzbhydra2-debug-infos.zip

theotherp commented 1 year ago

That's not a bug. Logging markers fill your log with a lot of stuffs that makes it hard for me to read it. They should only be enabled when asked for. As it is a warning you can ignore it.

On Thu, 10 Aug 2023, 06:46 viptampa, @.***> wrote:

-

What do you expect to happen? - Save w/o this warning

What does happen? "You have more than 3 logging markers enabled" warning appears.

Have you searched for this problem? Yes, google and reddit. Did not produce any results that resolved my isssue.

Can the problem be reproduced? Yes. By saving my config, everytime.

If you use a docker container please tell me which one.: Using the binhex-nzbhydra2 docker container

I've downloaded and attached the debug file as I've seen recommended on reddit before. nzbhydra2-debug-infos.zip https://github.com/theotherp/nzbhydra2/files/12308851/nzbhydra2-debug-infos.zip

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/886, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6J6H2WQCJXF4H3PFO3XURRS7ANCNFSM6AAAAAA3K5JP44 . You are receiving this because you are subscribed to this thread.Message ID: @.***>

viptampa commented 1 year ago

Understood. From what I can tell, I've turned off all the logging markers and have set the log level to warning for log and console log level

While I can ignore it.... its bothersome to see it. How I can correct the issue?

theotherp commented 1 year ago

The logging level is set to WARN but the markers are still enabled. I should probably update the check to disable the warning in this case. For now you can set the level to DEBUG, disable all the markers, and set the level to WARN again.

On Thu, 10 Aug 2023, 16:22 viptampa, @.***> wrote:

Understood. From what I can tell, I've turned off all the logging markers and have set the log level to warning for log and console log level

While I can ignore it.... its bothersome to see it. How I can correct the issue?

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/886#issuecomment-1673321073, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6OGXYARB6OYQ25C6S3XUTVDVANCNFSM6AAAAAA3K5JP44 . You are receiving this because you commented.Message ID: @.***>

viptampa commented 1 year ago

How does one disable the markers? I thought I did that already and need to double check I'm on the same page.

viptampa commented 1 year ago

The logging level is set to WARN but the markers are still enabled. I should probably update the check to disable the warning in this case. For now you can set the level to DEBUG, disable all the markers, and set the level to WARN again. … On Thu, 10 Aug 2023, 16:22 viptampa, @.> wrote: Understood. From what I can tell, I've turned off all the logging markers and have set the log level to warning for log and console log level While I can ignore it.... its bothersome to see it. How I can correct the issue? — Reply to this email directly, view it on GitHub <#886 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6OGXYARB6OYQ25C6S3XUTVDVANCNFSM6AAAAAA3K5JP44 . You are receiving this because you commented.Message ID: @.>

Please point me to the instructions on how to disable the markers.
I found them in the XML file. If I click save on the config page, it automatically adds back in all of the markers...

- "TRAILING"
- "RESULT_ACCEPTOR"
- "PERFORMANCE"
- "DUPLICATES"
- "SCHEDULER"
- "USER_AGENT"
- "DOWNLOAD_STATUS_UPDATE"
- "URL_CALCULATION"
- "HTTP"
theotherp commented 1 year ago

I'm not at home right now and can't test it, will get back to you next weekend.

On Sun, 13 Aug 2023, 21:40 viptampa, @.***> wrote:

The logging level is set to WARN but the markers are still enabled. I should probably update the check to disable the warning in this case. For now you can set the level to DEBUG, disable all the markers, and set the level to WARN again. … <#m-3215606110901919555> On Thu, 10 Aug 2023, 16:22 viptampa, @.> wrote: Understood. From what I can tell, I've turned off all the logging markers and have set the log level to warning for log and console log level While I can ignore it.... its bothersome to see it. How I can correct the issue? — Reply to this email directly, view it on GitHub <#886 (comment) https://github.com/theotherp/nzbhydra2/issues/886#issuecomment-1673321073>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6OGXYARB6OYQ25C6S3XUTVDVANCNFSM6AAAAAA3K5JP44 https://github.com/notifications/unsubscribe-auth/ADNUA6OGXYARB6OYQ25C6S3XUTVDVANCNFSM6AAAAAA3K5JP44 . You are receiving this because you commented.Message ID: @.>

Please point me to the instructions on how to disable the markers. I found them in the XML file. If I click save on the config page, it automatically adds back in all of the markers...

  • "TRAILING"
  • "RESULT_ACCEPTOR"
  • "PERFORMANCE"
  • "DUPLICATES"
  • "SCHEDULER"
  • "USER_AGENT"
  • "DOWNLOAD_STATUS_UPDATE"
  • "URL_CALCULATION"
  • "HTTP"

— Reply to this email directly, view it on GitHub https://github.com/theotherp/nzbhydra2/issues/886#issuecomment-1676445500, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNUA6P3R4WFWAEDEYZOSKLXVEURJANCNFSM6AAAAAA3K5JP44 . You are receiving this because you commented.Message ID: @.***>

viptampa commented 1 year ago

Understood. Thank you kind human!