Jump to content


Photo

No handlers could be found for logger "AT"


  • Please log in to reply
5 replies to this topic

#1 fogonero

  • Senior Member
  • 77 posts

0
Neutral

Posted 11 May 2019 - 22:03

No handlers could be found for logger "AT"
Unhandled error in Deferred:

I have this error in the log E2 continued in the background.

someone who can explain to me why it happens?
 



Re: No handlers could be found for logger "AT" #2 Dimitrij

  • PLi® Core member
  • 6,413 posts

+208
Excellent

Posted 12 May 2019 - 05:56

This problem solved

AutoTimer - fixed compare service references (#517)


Formuler1/VU+solo4k(thanks guys to gisclub.tv)


Re: No handlers could be found for logger "AT" #3 WanWizard

  • Forum Moderator
    PLi® Core member
  • 46,376 posts

+751
Excellent

Posted 12 May 2019 - 11:30

Fix will be in 7.1-release.


Currently in use: VU+Duo 4K (2xFBC S2), Amiko Viper T2C (T2), SAB Alpha Triple HD (S2+T2), Zgemma H3.T2C (T/C), Zgemma H6 (fallback), VU+Zero (fallback)

Many answers to your question can be found in our new and improved wiki.

note: I do not provide support via PM !

 


Re: No handlers could be found for logger "AT" #4 fogonero

  • Senior Member
  • 77 posts

0
Neutral

Posted 13 May 2019 - 01:11

No handlers could be found for logger "AT"

thx @Dimitrij WanWizard......build with updated core oe must be updated plugin with that commit ... even so it remains in my registry. .... remove the plugin if it disappears.

...........

I still have this that seems to be something different I thought they were similar...It is a constant ( 4-5 seconds) log:

Unhandled error in Deferred:


Re: No handlers could be found for logger "AT" #5 Dimitrij

  • PLi® Core member
  • 6,413 posts

+208
Excellent

Posted 13 May 2019 - 04:58

fogonero

in telnet

init 4
ENIGMA_DEBUG_LVL=4 enigma2

Formuler1/VU+solo4k(thanks guys to gisclub.tv)


Re: No handlers could be found for logger "AT" #6 ims

  • PLi® Core member
  • 10,996 posts

+165
Excellent

Posted 13 May 2019 - 09:33

 

No handlers could be found for logger "AT"

thx @Dimitrij WanWizard......build with updated core oe must be updated plugin with that commit ... even so it remains in my registry. .... remove the plugin if it disappears.

...........

I still have this that seems to be something different I thought they were similar...It is a constant ( 4-5 seconds) log:

Unhandled error in Deferred:

 

 

 

Could you try in telnet (putty):

init 4

ENIGMA_DEBUG_LVL=4 enigma2

 

 

and then wait, when Autotimer will run automaticaly (it is set delay time in minutes in AT setting)? Then there could be visible AT crash in debug.

 

But I think, you have not updated AT still.


Edited by ims, 13 May 2019 - 09:34.

Kdo nic nedělá, nic nezkazí!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users