Fhem stockt immer wieder.

[Caleus]

Guten Morgen

also ich habe nun mal ein paar logs aufgezeichnet und das letzte von "no bad guy found" wäre das hier

Code Auswählen Erweitern


=========================================================

[Freezemon] myFreezemon: possible freeze starting at 05:31:44, delay is 1.242 possibly caused by: no bad guy found :-(

2019.01.13 05:31:43.953 4: : HTTP response code 200

2019.01.13 05:31:43.953 5: HttpUtils : Got data, length: 23

2019.01.13 05:31:43.953 5: HttpUtils response header:

HTTP/1.1 200 OK

Server: nginx/1.12.2

Date: Sun, 13 Jan 2019 04:31:43 GMT

Content-Type: application/json

Content-Length: 23

Connection: close

Access-Control-Allow-Origin: *

Access-Control-Allow-Methods: GET, POST, OPTIONS

Access-Control-Expose-Headers: Content-Length,Content-Type,Date,Server,Connection

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2019.01.13 05:31:43.953 5: TelegramBot_Callback HomeBot: called from Polling

2019.01.13 05:31:43.953 5: TelegramBot_Callback HomeBot: data returned :{"ok":true,"result":[]}:

2019.01.13 05:31:43.954 5: TelegramBot_Deepencode HomeBot: encoded a String from :1: to :1:

2019.01.13 05:31:43.954 5: TelegramBot_Deepencode HomeBot: found an ARRAY

2019.01.13 05:31:43.954 5: TelegramBot_Deepencode HomeBot: found a HASH

2019.01.13 05:31:43.954 5: TelegramBot_Callback HomeBot: after encoding

2019.01.13 05:31:43.954 5: TelegramBot_Callback HomeBot: polling returned result? 0

2019.01.13 05:31:43.954 5: UpdatePoll HomeBot: number of results 0

2019.01.13 05:31:43.954 5: TelegramBot_UpdatePoll HomeBot: called

2019.01.13 05:31:43.954 5: TelegramBot_UpdatePoll HomeBot: - Initiate non blocking polling - With callback set

2019.01.13 05:31:43.955 5: TelegramBot_readToken: Read Telegram API token from file

2019.01.13 05:31:43.956 4: TelegramBot_UpdatePoll HomeBot: initiate polling with nonblockingGet with 120s

2019.01.13 05:31:43.956 5: HttpUtils url=

2019.01.13 05:31:43.957 4: IP: api.telegram.org -> 149.154.167.220

2019.01.13 05:31:43.958 5: TelegramBot_UpdatePoll HomeBot: - Ende > next polling started

2019.01.13 05:31:43.958 4: TelegramBot_Callback HomeBot: resulted in SUCCESS from Polling

2019.01.13 05:31:43.958 5: TelegramBot_Callback HomeBot: - Ende > Control back to FHEM

--- log skips     1.283 secs.

2019.01.13 05:31:45.241 5: HttpUtils request header:

GET /bot588317852:AAEF7WqdNa97iPKMLCVu6yVrrW9gVFOzVm4/getUpdates?offset=11174092&limit=5&timeout=120 HTTP/1.0

Host: api.telegram.org

Accept-Encoding: gzip,deflate

agent: TelegramBot/1.0

User-Agent: TelegramBot/1.0

Accept: application/json

Accept-Charset: utf-8



2019.01.13 05:31:45.242 5: [Freezemon] myFreezemon: ----------- Starting Freeze handling at 2019.01.13 05:31:45.242 ---------------------

[Freezemon] myFreezemon: possible freeze starting at 05:31:44, delay is 1.242 possibly caused by: no bad guy found :-(

Caleus

[KernSani]

Hmmm... da kann man gut sehen, dass der TelegramBot erfolgreich gepollt hat und FHEM dann erstmal ein Weilchen nichts mehr macht -zumindest keine Logeinträge mehr schreibt, d.h. es wird irgendetwas verarbeitet.
Wenn du die Catch*-Attribute noch aktivierdt, finder man möglicherweise mehr Details.
Freezemon kann leider nur Hinweise geben, wer einen Freeze verursacht hat. Das ,,warum" ist dann Handarbeit

global dnsServer hattest du gesetzt, oder?


Kurz, weil mobil

[Caleus]

Ja also global dnsServer habe ich nun gestern gesetzt auf die Fritzbox IP, welche Einstellung für fm_CatchCmds
und fm_CatchFnCalls soll es den sein 0 bis 5 habe ich ?

Caleus

[KernSani]

0 bedeutet inaktiv, alles größer 0 bedeautet aktiv und gibt den Loglevel an... also 3 oder so...


Kurz, weil mobil

[Caleus]

so hier mal  ein log mit gestztem fm_CatchCmds und fm_CatchFnCalls beides auf 5 (hoffe ich)

Code Auswählen Erweitern

=========================================================

[Freezemon] myFreezemon: possible freeze starting at 14:07:51, delay is 4.376 possibly caused by: no bad guy found :-(

2019.01.13 14:07:50.048 4: : HTTP response code 200

2019.01.13 14:07:50.048 5: HttpUtils : Got data, length: 23

2019.01.13 14:07:50.048 5: HttpUtils response header:

HTTP/1.1 200 OK

Server: nginx/1.12.2

Date: Sun, 13 Jan 2019 13:07:50 GMT

Content-Type: application/json

Content-Length: 23

Connection: close

Access-Control-Allow-Origin: *

Access-Control-Allow-Methods: GET, POST, OPTIONS

Access-Control-Expose-Headers: Content-Length,Content-Type,Date,Server,Connection

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

2019.01.13 14:07:50.049 5: TelegramBot_Callback HomeBot: called from Polling

2019.01.13 14:07:50.049 5: TelegramBot_Callback HomeBot: data returned :{"ok":true,"result":[]}:

2019.01.13 14:07:50.049 5: TelegramBot_Deepencode HomeBot: found an ARRAY

2019.01.13 14:07:50.049 5: TelegramBot_Deepencode HomeBot: encoded a String from :1: to :1:

2019.01.13 14:07:50.049 5: TelegramBot_Deepencode HomeBot: found a HASH

2019.01.13 14:07:50.049 5: TelegramBot_Callback HomeBot: after encoding

2019.01.13 14:07:50.049 5: TelegramBot_Callback HomeBot: polling returned result? 0

2019.01.13 14:07:50.049 5: UpdatePoll HomeBot: number of results 0

2019.01.13 14:07:50.050 5: TelegramBot_UpdatePoll HomeBot: called

2019.01.13 14:07:50.050 5: TelegramBot_UpdatePoll HomeBot: - Initiate non blocking polling - With callback set

2019.01.13 14:07:50.051 5: TelegramBot_readToken: Read Telegram API token from file

2019.01.13 14:07:50.052 4: TelegramBot_UpdatePoll HomeBot: initiate polling with nonblockingGet with 120s

2019.01.13 14:07:50.052 5: HttpUtils url=

2019.01.13 14:07:50.053 4: IP: api.telegram.org -> 149.154.167.220

2019.01.13 14:07:50.054 5: TelegramBot_UpdatePoll HomeBot: - Ende > next polling started

2019.01.13 14:07:50.054 4: TelegramBot_Callback HomeBot: resulted in SUCCESS from Polling

2019.01.13 14:07:50.054 5: TelegramBot_Callback HomeBot: - Ende > Control back to FHEM

2019.01.13 14:07:50.073 4: GHoma_d33aa0 RX: 5A A5 00 16 90 01 0A E0 35 23 D3 3A A0 FF FE 01 81 39 00 00 01 01 20 00 02 90 13 5B B5

2019.01.13 14:07:50.080 5: rg_battery: not on any display, ignoring notify

2019.01.13 14:07:50.088 5: End notify loop for GHoma_d33aa0

--- log skips     5.287 secs.

2019.01.13 14:07:55.375 5: HttpUtils request header:

GET /bot588317852:AAEF7WqdNa97iPKMLCVu6yVrrW9gVFOzVm4/getUpdates?offset=11174092&limit=5&timeout=120 HTTP/1.0

Host: api.telegram.org

Accept-Encoding: gzip,deflate

agent: TelegramBot/1.0

User-Agent: TelegramBot/1.0

Accept: application/json

Accept-Charset: utf-8



2019.01.13 14:07:55.376 5: [Freezemon] myFreezemon: ----------- Starting Freeze handling at 2019.01.13 14:07:55.376 ---------------------

[Freezemon] myFreezemon: possible freeze starting at 14:07:51, delay is 4.376 possibly caused by: no bad guy found :-(


Caleus

[Caleus]

Hat keiner eine Idee?