[gelöst] FHEM sporadische Auslastung (die x-te)

[zife]

Hallo fhem'ler,

mir ist klar, dass dieses Thema schon oft diskutiert wurde - doch ich scheitere trotz ausführlicher Lektüre an der Suche und an der Interpretation der Daten, und insgesamt an einem sinnvoll aufeinander aufbauenden Vorgehen.

Das Problem:
Mein fhem leidet unter sehr häufiger, aber meist nur kurz andauernder Auslastung. Das führt dazu, dass z.B. manche Schaltbefehle nur deutlich verzögert ausgeführt werden (sehr ärgerlich im Alltag), oder die Weboberfläche oft nur sehr träge reagiert (nicht so schlimm). Ab und zu hängt sich fhem dann auch ganz auf (maximal ärgerlich).

Was habe ich gemacht:
... Ich habe meinen Raspi auf den neuesten Stand gebracht
... Ich habe fhem auf den neuesten Stand gebracht
... Ich habe meine Raspi-Auslastung mit "top" geprüft, und es ist immer der fhem-perl-Prozess, der auf 90-100% CPU hochschnellt.
... Ich habe apptime aufgerufen, dabei aber keine Auffälligkeiten gefunden (was vermutlich an meiner mangelnden Fähigkeit liegt, die Daten richtig zu lesen)
... Ich habe freezemon installiert, doch der Output passt (für mich) nicht zum Freeze-Verhalten von fhem.
... Ich habe einzelne Module aus meiner fhem-Config temporär rausgenommen

Erkenntnisse bisher:
... Wenn ich meine Module MieleAtHome und GardenaSmartBridge rausnehme, sind die Probleme mehr oder weniger weg
... Die Interpretation von freezemon, apptime und Co ist für einen Anfänger arg schwierig - ich sehe vermutlich den Wald vor lauter Bäumen nicht. In freezemon taucht recht häufig der Bösewicht tmr-HttpUtils_TimeoutErr(N/A) auf.

Frage:
... Wie kann ich systematisch vorgehen, um die Ursache zu finden?
... Welche Inhalte sollte ich hier posten, ohne den Thread sinnlos aufzublasen?
... Was hat es mit tmr-HttpUtils_TimeoutErr(N/A) auf sich?
... Macht es Sinn, mein Problem in den Fäden zu den o.g. Modulen zu posten? Anscheinend haben ja andere Nutzer das Problem nicht, also liegt es vermutlich NICHT am Modul...

So, genug für den Moment. Dickes Thema, aber auch dickes Problem. Ich hoffe auf Erleuchtung 

[Beta-User]

"Die Antwort" auf die vielfältigen Fragen gibt es vermutlich nicht.

Da du zwei spezielle Module rausgepickt hast, solltest du ggf. mal auf deren Autoren zugehen. Kann aber sein, dass die dich auf einen allgemeinen Punkt verweisen, denn beides könnte damit zu tun haben, dass dein Netz ein Problem hat und die Namensauflösung grade nicht sauber funktioniert:

Code Auswählen Erweitern

attr global dnsServer xy
https://fhem.de/commandref_modular.html#global
(Es kann aber anders herum auch sein, dass genau das das Problem ist, falls es _falsch_ gesetzt ist!)

Ansonsten wären die ersten weiteren Schritte:
- Events beobachten (=> Event-Monitor) und ggf. ausdünnen, (eocr & Co)
- regexe bei Event-Handlern ansehen und ggf. anpassen (NOTIFYDEV bei notify etc. auch gesetzt?)
- Eventhandling an sich optimieren (eher ein "Großnotify", das die Events ggf. intern "dispatcht" als viele kleine (z.B. on/off per Taster-Device in ein notify statt zwei)

[zife]

Danke, Beta-User.

Das mit der Namensauflösung muss ich mir ansehen, darüber hab ich mir noch nie Gedanken gemacht.


Zum Eventhandling:
Events habe ich im Schnitt alle 10 Sekunden eins, wenige davon lösen etwas aus - die meisten sind Statusmeldungen von Geräten. Da die fhem CPU-Nutzung laut "TOP" im Normalfall irgendwo bei 0,3 und 1% liegt und dann plötzlich auf 90-100% ansteigt und wieder fällt, ging ich davon aus, dass die Events und deren allgemeines Handling nicht die Ursache sei. Auch die gute Performance bei deaktivierten Modulen habe ich so gedeutet.

Ist das ein Trugschluss??

Beim Event-Handling gibt es bei mir mit Sicherheit Optimierungsbedarf. Das ist - zumindest für mich - aber ein ziemlich großes Projekt, denn ich muss meine DOIFs und NOTIFYs grundsätzlich umbauen. Ich schätze mal, ich hab davon 100-150 Stück, viele werten in der Tat Taster (Kurz-/Langdruck, Mehrfach-Druck, etc.) aus. Keine Ahnung, ob diese Anzahl viel ist...

Ich will mich nicht vor einer Sanierung meiner CFG drücken, aber ich hatte gehofft, dass es einen Weg gibt, VORHER herauszufinden, ob der Grund im Eventhandling liegt. Frei nach dem Motto: first things first.

[Beta-User]

Bei so wenigen Events dürfte es kaum an deren Verarbeitung liegen. (Es sei denn natürlich, du machst was völlig blockierendes auf der _Ausgangsseite_)...

Sieht mir nach einem "typischen Netzwerkproblem" aus. (Bin da aber alles andere als Experte!)

[zife]

Nicht, dass mir irgendwelche Blocker bewusst wären...

Ich poste hier mal einen der Top-Favoriten aus "apptime maxDly"... kann mir einer sagen, was das ist?

Code Auswählen Erweitern

tmr-FW_closeInactiveClients              0                                        5       29     121.23     4.18  4527.85  1078.61 28.01. 17:32:44 0

[Beta-User]

Damit solltest du rausfinden können, zu welchem Modul der aufzurufende Code gehört:

Code Auswählen Erweitern

user@server:/opt/fhem/FHEM$ grep FW_closeInactiveClients *

[CoolTux]

FW dürfte FHEMWEB sein.

Ich tippe aber in der Tat auf DNS

[Pfriemler]

Ich lese hier mal mit. Das mit der Namensauflösung ist interessant. Ich nutze außer Telegram und Alexa eigentlich keine mir bekannt "äußeren" Dienste. Ich habe aber ebenfalls die beschriebenen Probleme und teilweise Freezemon-Hänger über 50 Sekunden, wenn meine Internetverbindung down ist (völlig absurd: man baut sich mühsam ein prinzipiell cloudfreies System ...). Weder die Abfrage der Fritzbox noch die nur einmal täglich stattfindende Abfrage der externen IP sind dabei auffällig geworden - es hilft aber auch nicht, Alexa und Telegram zu deaktivieren, die Hänger bleiben dennoch bestehen. Bin gespannt, ob ich einen der Tricks auch bei mir verwenden kann...

[zife]

Ich hab jetzt mal im global Attribut meine Fritzbox als DNS Server eingetragen... so ist das gedacht, oder? (Hilft aber leider nicht )

Gibts noch Alternativen?
Und kann es am Switch liegen? Zwischen meiner Fritzbox und dem Raspi hängt ein Netgear 108...

Ich will dieses Forum nicht zur Netzwerkberatung werden lassen, aber das Thema hat ja doch ne Menge Einfluss auf fhem. Und wenn die Ehrendoktoren hier Ideen haben, lern ich natürlich gern mehr...

[CoolTux]

Schau mal ins FHEM Log kopiere alle freezmon Einträge der letzten Stunden raus. Die dann hier veröffentlichen bitte.

[Wernieman]

Mal Grundsätzlich:
Bei DNS-Problemen geht FHEM auf 100% Auslastung? Ich kann mir damit Freeze erklären, aber nicht die Große Auslastung. oder irre ich mich?

@zife
Wegen Switch, wenn Der keine Weboberfläche hat: Du kannst mal auf Shell-Ebene prüfen, ob Deine Netzwerkkarte Fehler" wirft.

Code Auswählen Erweitern

ifconfig
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
.....
        RX packets 9331  bytes 5490555 (5.4 MB)
        RX errors 0  dropped 1224  overruns 0  frame 0
        TX packets 5813  bytes 776756 (776.7 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
.....

Bei "errors" etc. sollte 0 stehen (Es sei denn, Dein Rechner läuft schon seit Monaten)

Und noch eine spontane Frage:
Verwendest Du Presence o.Ä.?

[zife]

Schau mal ins FHEM Log kopiere alle freezmon Einträge der letzten Stunden raus. Die dann hier veröffentlichen bitte.

Also, ich habe das Gefühl, dass es seit dem global-Attribut "attr global dnsServer 192.168.178.1" schlimmer geworden ist, das kann aber auch Einbildung sein.

Hier die Freezemon-Einträge aus dem Log der letzten 2 Stunden, ganz schön was los:

Code Auswählen Erweitern

2022.01.29 10:11:16 1: [Freezemon] myFreezeMon: possible freeze starting at 10:11:10, delay is 6.049 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:12:16 1: [Freezemon] myFreezeMon: possible freeze starting at 10:12:11, delay is 5.855 possibly caused by: no bad guy found :-(
2022.01.29 10:12:21 1: [Freezemon] myFreezeMon: possible freeze starting at 10:12:19, delay is 2.033 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:13:18 1: [Freezemon] myFreezeMon: possible freeze starting at 10:13:12, delay is 6.047 possibly caused by: no bad guy found :-(
2022.01.29 10:14:18 1: [Freezemon] myFreezeMon: possible freeze starting at 10:14:13, delay is 5.536 possibly caused by: no bad guy found :-(
2022.01.29 10:15:19 1: [Freezemon] myFreezeMon: possible freeze starting at 10:15:14, delay is 5.488 possibly caused by: no bad guy found :-(
2022.01.29 10:16:20 1: [Freezemon] myFreezeMon: possible freeze starting at 10:16:15, delay is 5.267 possibly caused by: no bad guy found :-(
2022.01.29 10:16:23 1: [Freezemon] myFreezeMon: possible freeze starting at 10:16:22, delay is 1.65 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:17:21 1: [Freezemon] myFreezeMon: possible freeze starting at 10:17:15, delay is 6.083 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:18:21 1: [Freezemon] myFreezeMon: possible freeze starting at 10:18:16, delay is 5.921 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 10:18:27 1: [Freezemon] myFreezeMon: possible freeze starting at 10:18:23, delay is 4.447 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:19:22 1: [Freezemon] myFreezeMon: possible freeze starting at 10:19:17, delay is 5.881 possibly caused by: no bad guy found :-(
2022.01.29 10:20:23 1: [Freezemon] myFreezeMon: possible freeze starting at 10:20:18, delay is 5.787 possibly caused by: no bad guy found :-(
2022.01.29 10:20:27 1: [Freezemon] myFreezeMon: possible freeze starting at 10:20:25, delay is 2.244 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:20:29 1: [Freezemon] myFreezeMon: possible freeze starting at 10:20:28, delay is 1.535 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:21:24 1: [Freezemon] myFreezeMon: possible freeze starting at 10:21:19, delay is 5.642 possibly caused by: no bad guy found :-(
2022.01.29 10:21:47 1: [Freezemon] myFreezeMon: possible freeze starting at 10:21:42, delay is 5.637 possibly caused by: no bad guy found :-(
2022.01.29 10:22:25 1: [Freezemon] myFreezeMon: possible freeze starting at 10:22:20, delay is 5.915 possibly caused by: no bad guy found :-(
2022.01.29 10:22:29 1: [Freezemon] myFreezeMon: possible freeze starting at 10:22:27, delay is 2.021 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 10:23:26 1: [Freezemon] myFreezeMon: possible freeze starting at 10:23:21, delay is 5.886 possibly caused by: no bad guy found :-(
2022.01.29 10:24:27 1: [Freezemon] myFreezeMon: possible freeze starting at 10:24:22, delay is 5.692 possibly caused by: no bad guy found :-(
2022.01.29 10:24:31 1: [Freezemon] myFreezeMon: possible freeze starting at 10:24:30, delay is 1.011 possibly caused by: tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:25:29 1: [Freezemon] myFreezeMon: possible freeze starting at 10:25:24, delay is 5.4 possibly caused by: tmr-MAH_updateValues(Geschirrspueler)
2022.01.29 10:26:30 1: [Freezemon] myFreezeMon: possible freeze starting at 10:26:25, delay is 5.28 possibly caused by: no bad guy found :-(
2022.01.29 10:26:34 1: [Freezemon] myFreezeMon: possible freeze starting at 10:26:32, delay is 2.457 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:27:31 1: [Freezemon] myFreezeMon: possible freeze starting at 10:27:25, delay is 6.096 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:28:32 1: [Freezemon] myFreezeMon: possible freeze starting at 10:28:26, delay is 6.005 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 10:28:36 1: [Freezemon] myFreezeMon: possible freeze starting at 10:28:34, delay is 2.027 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:29:32 1: [Freezemon] myFreezeMon: possible freeze starting at 10:29:27, delay is 5.813 possibly caused by: no bad guy found :-(
2022.01.29 10:30:33 1: [Freezemon] myFreezeMon: possible freeze starting at 10:30:28, delay is 5.581 possibly caused by: no bad guy found :-(
2022.01.29 10:30:36 1: [Freezemon] myFreezeMon: possible freeze starting at 10:30:35, delay is 1.435 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:30:39 1: [Freezemon] myFreezeMon: possible freeze starting at 10:30:37, delay is 2.343 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:31:35 1: [Freezemon] myFreezeMon: possible freeze starting at 10:31:29, delay is 6.002 possibly caused by: no bad guy found :-(
2022.01.29 10:32:35 1: [Freezemon] myFreezeMon: possible freeze starting at 10:32:30, delay is 5.793 possibly caused by: no bad guy found :-(
2022.01.29 10:32:39 1: [Freezemon] myFreezeMon: possible freeze starting at 10:32:38, delay is 1.998 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:33:36 1: [Freezemon] myFreezeMon: possible freeze starting at 10:33:31, delay is 5.645 possibly caused by: no bad guy found :-(
2022.01.29 10:34:37 1: [Freezemon] myFreezeMon: possible freeze starting at 10:34:32, delay is 5.523 possibly caused by: no bad guy found :-(
2022.01.29 10:34:40 1: [Freezemon] myFreezeMon: possible freeze starting at 10:34:39, delay is 1.174 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:34:42 1: [Freezemon] myFreezeMon: possible freeze starting at 10:34:41, delay is 1.564 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:34:58 1: [Freezemon] myFreezeMon: possible freeze starting at 10:34:57, delay is 1.187 possibly caused by: no bad guy found :-(
2022.01.29 10:35:12 1: [Freezemon] myFreezeMon: possible freeze starting at 10:35:11, delay is 1.646 possibly caused by: no bad guy found :-(
2022.01.29 10:35:38 1: [Freezemon] myFreezeMon: possible freeze starting at 10:35:33, delay is 5.387 possibly caused by: no bad guy found :-(
2022.01.29 10:36:39 1: [Freezemon] myFreezeMon: possible freeze starting at 10:36:34, delay is 5.217 possibly caused by: no bad guy found :-(
2022.01.29 10:36:43 1: [Freezemon] myFreezeMon: possible freeze starting at 10:36:41, delay is 2.326 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:37:40 1: [Freezemon] myFreezeMon: possible freeze starting at 10:37:34, delay is 6.156 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:38:41 1: [Freezemon] myFreezeMon: possible freeze starting at 10:38:35, delay is 6.096 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 10:38:47 1: [Freezemon] myFreezeMon: possible freeze starting at 10:38:43, delay is 4.453 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:39:42 1: [Freezemon] myFreezeMon: possible freeze starting at 10:39:36, delay is 6.13 possibly caused by: no bad guy found :-(
2022.01.29 10:40:43 1: [Freezemon] myFreezeMon: possible freeze starting at 10:40:37, delay is 6.023 possibly caused by: no bad guy found :-(
2022.01.29 10:40:47 1: [Freezemon] myFreezeMon: possible freeze starting at 10:40:45, delay is 2.894 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:40:49 1: [Freezemon] myFreezeMon: possible freeze starting at 10:40:48, delay is 1.714 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:41:43 1: [Freezemon] myFreezeMon: possible freeze starting at 10:41:38, delay is 5.896 possibly caused by: no bad guy found :-(
2022.01.29 10:42:44 1: [Freezemon] myFreezeMon: possible freeze starting at 10:42:39, delay is 5.502 possibly caused by: no bad guy found :-(
2022.01.29 10:42:47 1: [Freezemon] myFreezeMon: possible freeze starting at 10:42:46, delay is 1.494 possibly caused by: no bad guy found :-(
2022.01.29 10:42:49 1: [Freezemon] myFreezeMon: possible freeze starting at 10:42:48, delay is 1.201 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:43:45 1: [Freezemon] myFreezeMon: possible freeze starting at 10:43:40, delay is 5.472 possibly caused by: no bad guy found :-(
2022.01.29 10:44:46 1: [Freezemon] myFreezeMon: possible freeze starting at 10:44:41, delay is 5.317 possibly caused by: no bad guy found :-(
2022.01.29 10:44:48 1: [Freezemon] myFreezeMon: possible freeze starting at 10:44:47, delay is 1.081 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 10:44:50 1: [Freezemon] myFreezeMon: possible freeze starting at 10:44:49, delay is 1.653 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:45:47 1: [Freezemon] myFreezeMon: possible freeze starting at 10:45:41, delay is 6.163 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:46:48 1: [Freezemon] myFreezeMon: possible freeze starting at 10:46:43, delay is 5.54 possibly caused by: no bad guy found :-(
2022.01.29 10:46:51 1: [Freezemon] myFreezeMon: possible freeze starting at 10:46:50, delay is 1.505 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:47:49 1: [Freezemon] myFreezeMon: possible freeze starting at 10:47:44, delay is 5.585 possibly caused by: no bad guy found :-(
2022.01.29 10:48:50 1: [Freezemon] myFreezeMon: possible freeze starting at 10:48:45, delay is 5.573 possibly caused by: no bad guy found :-(
2022.01.29 10:48:56 1: [Freezemon] myFreezeMon: possible freeze starting at 10:48:52, delay is 4.243 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:49:51 1: [Freezemon] myFreezeMon: possible freeze starting at 10:49:46, delay is 5.335 possibly caused by: no bad guy found :-(
2022.01.29 10:50:52 1: [Freezemon] myFreezeMon: possible freeze starting at 10:50:46, delay is 6.191 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:50:55 1: [Freezemon] myFreezeMon: possible freeze starting at 10:50:54, delay is 1.444 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:50:58 1: [Freezemon] myFreezeMon: possible freeze starting at 10:50:56, delay is 2.02 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:51:53 1: [Freezemon] myFreezeMon: possible freeze starting at 10:51:47, delay is 6.12 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 10:52:54 1: [Freezemon] myFreezeMon: possible freeze starting at 10:52:48, delay is 6.066 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 10:52:56 1: [Freezemon] myFreezeMon: possible freeze starting at 10:52:55, delay is 1.793 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 10:52:58 1: [Freezemon] myFreezeMon: possible freeze starting at 10:52:57, delay is 1.501 possibly caused by: no bad guy found :-(
2022.01.29 10:53:54 1: [Freezemon] myFreezeMon: possible freeze starting at 10:53:49, delay is 5.896 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 10:54:55 1: [Freezemon] myFreezeMon: possible freeze starting at 10:54:50, delay is 5.796 possibly caused by: no bad guy found :-(
2022.01.29 10:54:58 1: [Freezemon] myFreezeMon: possible freeze starting at 10:54:57, delay is 1.447 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:55:00 1: [Freezemon] myFreezeMon: possible freeze starting at 10:54:59, delay is 1.157 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:55:56 1: [Freezemon] myFreezeMon: possible freeze starting at 10:55:51, delay is 5.751 possibly caused by: no bad guy found :-(
2022.01.29 10:56:57 1: [Freezemon] myFreezeMon: possible freeze starting at 10:56:52, delay is 5.476 possibly caused by: no bad guy found :-(
2022.01.29 10:57:01 1: [Freezemon] myFreezeMon: possible freeze starting at 10:57:00, delay is 1.635 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 10:57:58 1: [Freezemon] myFreezeMon: possible freeze starting at 10:57:53, delay is 5.535 possibly caused by: no bad guy found :-(
2022.01.29 10:59:00 1: [Freezemon] myFreezeMon: possible freeze starting at 10:58:54, delay is 6.137 possibly caused by: no bad guy found :-(
2022.01.29 10:59:05 1: [Freezemon] myFreezeMon: possible freeze starting at 10:59:02, delay is 3.941 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:00:00 1: [Freezemon] myFreezeMon: possible freeze starting at 10:59:55, delay is 5.711 possibly caused by: no bad guy found :-(
2022.01.29 11:01:01 1: [Freezemon] myFreezeMon: possible freeze starting at 11:00:56, delay is 5.558 possibly caused by: no bad guy found :-(
2022.01.29 11:01:04 1: [Freezemon] myFreezeMon: possible freeze starting at 11:01:03, delay is 1.299 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:01:07 1: [Freezemon] myFreezeMon: possible freeze starting at 11:01:05, delay is 2.282 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:02:02 1: [Freezemon] myFreezeMon: possible freeze starting at 11:01:57, delay is 5.528 possibly caused by: no bad guy found :-(
2022.01.29 11:03:03 1: [Freezemon] myFreezeMon: possible freeze starting at 11:02:58, delay is 5.355 possibly caused by: no bad guy found :-(
2022.01.29 11:03:07 1: [Freezemon] myFreezeMon: possible freeze starting at 11:03:05, delay is 2.58 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:04:04 1: [Freezemon] myFreezeMon: possible freeze starting at 11:03:58, delay is 6.516 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:05:05 1: [Freezemon] myFreezeMon: possible freeze starting at 11:04:59, delay is 6.071 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:05:08 1: [Freezemon] myFreezeMon: possible freeze starting at 11:05:06, delay is 2.215 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-CODE(0x2d95ae0)(GetStatus) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:06:06 1: [Freezemon] myFreezeMon: possible freeze starting at 11:06:00, delay is 6.08 possibly caused by: no bad guy found :-(
2022.01.29 11:07:07 1: [Freezemon] myFreezeMon: possible freeze starting at 11:07:02, delay is 5.455 possibly caused by: no bad guy found :-(
2022.01.29 11:07:09 1: [Freezemon] myFreezeMon: possible freeze starting at 11:07:08, delay is 1.757 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:07:12 1: [Freezemon] myFreezeMon: possible freeze starting at 11:07:10, delay is 2.48 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:08:08 1: [Freezemon] myFreezeMon: possible freeze starting at 11:08:03, delay is 5.359 possibly caused by: no bad guy found :-(
2022.01.29 11:09:09 1: [Freezemon] myFreezeMon: possible freeze starting at 11:09:03, delay is 6.207 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:09:13 1: [Freezemon] myFreezeMon: possible freeze starting at 11:09:11, delay is 2.853 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:09:15 1: [Freezemon] myFreezeMon: possible freeze starting at 11:09:14, delay is 1.575 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:10:10 1: [Freezemon] myFreezeMon: possible freeze starting at 11:10:04, delay is 6.014 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:11:10 1: [Freezemon] myFreezeMon: possible freeze starting at 11:11:05, delay is 5.871 possibly caused by: no bad guy found :-(
2022.01.29 11:11:12 1: [Freezemon] myFreezeMon: possible freeze starting at 11:11:11, delay is 1.115 possibly caused by: tmr-MAH_updateValues(Geschirrspueler) tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:11:17 1: [Freezemon] myFreezeMon: possible freeze starting at 11:11:13, delay is 4.187 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:12:11 1: [Freezemon] myFreezeMon: possible freeze starting at 11:12:06, delay is 5.836 possibly caused by: no bad guy found :-(
2022.01.29 11:13:12 1: [Freezemon] myFreezeMon: possible freeze starting at 11:13:07, delay is 5.646 possibly caused by: no bad guy found :-(
2022.01.29 11:13:16 1: [Freezemon] myFreezeMon: possible freeze starting at 11:13:14, delay is 2.311 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:14:13 1: [Freezemon] myFreezeMon: possible freeze starting at 11:14:08, delay is 5.567 possibly caused by: no bad guy found :-(
2022.01.29 11:15:14 1: [Freezemon] myFreezeMon: possible freeze starting at 11:15:09, delay is 5.386 possibly caused by: no bad guy found :-(
2022.01.29 11:15:19 1: [Freezemon] myFreezeMon: possible freeze starting at 11:15:17, delay is 2.256 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:16:15 1: [Freezemon] myFreezeMon: possible freeze starting at 11:16:10, delay is 5.801 possibly caused by: no bad guy found :-(
2022.01.29 11:17:16 1: [Freezemon] myFreezeMon: possible freeze starting at 11:17:11, delay is 5.723 possibly caused by: no bad guy found :-(
2022.01.29 11:17:20 1: [Freezemon] myFreezeMon: possible freeze starting at 11:17:18, delay is 2.565 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:18:17 1: [Freezemon] myFreezeMon: possible freeze starting at 11:18:12, delay is 5.961 possibly caused by: no bad guy found :-(
2022.01.29 11:19:18 1: [Freezemon] myFreezeMon: possible freeze starting at 11:19:13, delay is 5.566 possibly caused by: no bad guy found :-(
2022.01.29 11:19:21 1: [Freezemon] myFreezeMon: possible freeze starting at 11:19:20, delay is 1.455 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:19:24 1: [Freezemon] myFreezeMon: possible freeze starting at 11:19:22, delay is 2.344 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:20:19 1: [Freezemon] myFreezeMon: possible freeze starting at 11:20:14, delay is 5.451 possibly caused by: no bad guy found :-(
2022.01.29 11:21:20 1: [Freezemon] myFreezeMon: possible freeze starting at 11:21:15, delay is 5.27 possibly caused by: no bad guy found :-(
2022.01.29 11:21:25 1: [Freezemon] myFreezeMon: possible freeze starting at 11:21:22, delay is 3.066 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:22:21 1: [Freezemon] myFreezeMon: possible freeze starting at 11:22:16, delay is 5.257 possibly caused by: no bad guy found :-(
2022.01.29 11:23:22 1: [Freezemon] myFreezeMon: possible freeze starting at 11:23:16, delay is 6.085 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:23:26 1: [Freezemon] myFreezeMon: possible freeze starting at 11:23:24, delay is 2.251 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:24:23 1: [Freezemon] myFreezeMon: possible freeze starting at 11:24:17, delay is 6.133 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 11:25:24 1: [Freezemon] myFreezeMon: possible freeze starting at 11:25:18, delay is 6.053 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 11:25:27 1: [Freezemon] myFreezeMon: possible freeze starting at 11:25:26, delay is 1.02 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:26:25 1: [Freezemon] myFreezeMon: possible freeze starting at 11:26:19, delay is 6.247 possibly caused by: no bad guy found :-(
2022.01.29 11:27:26 1: [Freezemon] myFreezeMon: possible freeze starting at 11:27:20, delay is 6.153 possibly caused by: no bad guy found :-(
2022.01.29 11:27:28 1: [Freezemon] myFreezeMon: possible freeze starting at 11:27:27, delay is 1.101 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:27:30 1: [Freezemon] myFreezeMon: possible freeze starting at 11:27:29, delay is 1.868 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:28:27 1: [Freezemon] myFreezeMon: possible freeze starting at 11:28:21, delay is 6.066 possibly caused by: no bad guy found :-(
2022.01.29 11:29:27 1: [Freezemon] myFreezeMon: possible freeze starting at 11:29:22, delay is 5.567 possibly caused by: no bad guy found :-(
2022.01.29 11:29:33 1: [Freezemon] myFreezeMon: possible freeze starting at 11:29:30, delay is 3.088 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:30:28 1: [Freezemon] myFreezeMon: possible freeze starting at 11:30:23, delay is 5.407 possibly caused by: no bad guy found :-(
2022.01.29 11:31:29 1: [Freezemon] myFreezeMon: possible freeze starting at 11:31:24, delay is 5.565 possibly caused by: no bad guy found :-(
2022.01.29 11:31:32 1: [Freezemon] myFreezeMon: possible freeze starting at 11:31:31, delay is 1.439 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:31:35 1: [Freezemon] myFreezeMon: possible freeze starting at 11:31:33, delay is 2.551 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:32:30 1: [Freezemon] myFreezeMon: possible freeze starting at 11:32:24, delay is 6.458 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:33:31 1: [Freezemon] myFreezeMon: possible freeze starting at 11:33:25, delay is 6.298 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 11:33:35 1: [Freezemon] myFreezeMon: possible freeze starting at 11:33:34, delay is 1.886 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:34:31 1: [Freezemon] myFreezeMon: possible freeze starting at 11:34:26, delay is 5.938 possibly caused by: no bad guy found :-(
2022.01.29 11:35:33 1: [Freezemon] myFreezeMon: possible freeze starting at 11:35:27, delay is 6.192 possibly caused by: no bad guy found :-(
2022.01.29 11:35:35 1: [Freezemon] myFreezeMon: possible freeze starting at 11:35:34, delay is 1.053 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:35:37 1: [Freezemon] myFreezeMon: possible freeze starting at 11:35:36, delay is 1.67 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:36:34 1: [Freezemon] myFreezeMon: possible freeze starting at 11:36:28, delay is 6.086 possibly caused by: tmr-CODE(0x18974e8)(dnsQuery)
2022.01.29 11:37:34 1: [Freezemon] myFreezeMon: possible freeze starting at 11:37:29, delay is 5.934 possibly caused by: no bad guy found :-(
2022.01.29 11:37:39 1: [Freezemon] myFreezeMon: possible freeze starting at 11:37:37, delay is 2.217 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:38:35 1: [Freezemon] myFreezeMon: possible freeze starting at 11:38:30, delay is 5.975 possibly caused by: no bad guy found :-(
2022.01.29 11:39:36 1: [Freezemon] myFreezeMon: possible freeze starting at 11:39:31, delay is 5.445 possibly caused by: no bad guy found :-(
2022.01.29 11:39:39 1: [Freezemon] myFreezeMon: possible freeze starting at 11:39:38, delay is 1.824 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:39:42 1: [Freezemon] myFreezeMon: possible freeze starting at 11:39:40, delay is 2.789 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:40:37 1: [Freezemon] myFreezeMon: possible freeze starting at 11:40:32, delay is 5.332 possibly caused by: no bad guy found :-(
2022.01.29 11:41:38 1: [Freezemon] myFreezeMon: possible freeze starting at 11:41:32, delay is 6.157 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:41:43 1: [Freezemon] myFreezeMon: possible freeze starting at 11:41:40, delay is 3.962 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:42:39 1: [Freezemon] myFreezeMon: possible freeze starting at 11:42:33, delay is 6.172 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:43:40 1: [Freezemon] myFreezeMon: possible freeze starting at 11:43:34, delay is 6.088 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:44:41 1: [Freezemon] myFreezeMon: possible freeze starting at 11:44:35, delay is 6.214 possibly caused by: no bad guy found :-(
2022.01.29 11:45:41 1: [Freezemon] myFreezeMon: possible freeze starting at 11:45:36, delay is 5.973 possibly caused by: no bad guy found :-(
2022.01.29 11:45:43 1: [Freezemon] myFreezeMon: possible freeze starting at 11:45:42, delay is 1.162 possibly caused by: tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:45:47 1: [Freezemon] myFreezeMon: possible freeze starting at 11:45:45, delay is 2.118 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:46:42 1: [Freezemon] myFreezeMon: possible freeze starting at 11:46:37, delay is 5.69 possibly caused by: no bad guy found :-(
2022.01.29 11:47:44 1: [Freezemon] myFreezeMon: possible freeze starting at 11:47:38, delay is 6.327 possibly caused by: no bad guy found :-(
2022.01.29 11:47:49 1: [Freezemon] myFreezeMon: possible freeze starting at 11:47:47, delay is 2.351 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:48:44 1: [Freezemon] myFreezeMon: possible freeze starting at 11:48:39, delay is 5.807 possibly caused by: no bad guy found :-(
2022.01.29 11:49:46 1: [Freezemon] myFreezeMon: possible freeze starting at 11:49:41, delay is 5.233 possibly caused by: no bad guy found :-(
2022.01.29 11:49:51 1: [Freezemon] myFreezeMon: possible freeze starting at 11:49:48, delay is 3.364 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:50:47 1: [Freezemon] myFreezeMon: possible freeze starting at 11:50:41, delay is 6.183 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:51:48 1: [Freezemon] myFreezeMon: possible freeze starting at 11:51:42, delay is 6.13 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:51:52 1: [Freezemon] myFreezeMon: possible freeze starting at 11:51:49, delay is 3.042 possibly caused by: tmr-MAH_updateValues(Geschirrspueler) tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 11:52:49 1: [Freezemon] myFreezeMon: possible freeze starting at 11:52:43, delay is 6.05 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 11:53:49 1: [Freezemon] myFreezeMon: possible freeze starting at 11:53:44, delay is 5.99 possibly caused by: no bad guy found :-(
2022.01.29 11:53:54 1: [Freezemon] myFreezeMon: possible freeze starting at 11:53:53, delay is 1.158 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:54:50 1: [Freezemon] myFreezeMon: possible freeze starting at 11:54:45, delay is 5.788 possibly caused by: no bad guy found :-(
2022.01.29 11:55:51 1: [Freezemon] myFreezeMon: possible freeze starting at 11:55:46, delay is 5.646 possibly caused by: no bad guy found :-(
2022.01.29 11:56:52 1: [Freezemon] myFreezeMon: possible freeze starting at 11:56:47, delay is 5.54 possibly caused by: no bad guy found :-(
2022.01.29 11:57:53 1: [Freezemon] myFreezeMon: possible freeze starting at 11:57:48, delay is 5.858 possibly caused by: no bad guy found :-(
2022.01.29 11:57:57 1: [Freezemon] myFreezeMon: possible freeze starting at 11:57:55, delay is 2.023 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 11:58:54 1: [Freezemon] myFreezeMon: possible freeze starting at 11:58:49, delay is 5.372 possibly caused by: no bad guy found :-(
2022.01.29 11:59:55 1: [Freezemon] myFreezeMon: possible freeze starting at 11:59:50, delay is 5.235 possibly caused by: no bad guy found :-(
2022.01.29 12:00:00 1: [Freezemon] myFreezeMon: possible freeze starting at 11:59:57, delay is 3.783 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:00:56 1: [Freezemon] myFreezeMon: possible freeze starting at 12:00:51, delay is 5.457 possibly caused by: no bad guy found :-(
2022.01.29 12:01:57 1: [Freezemon] myFreezeMon: possible freeze starting at 12:01:51, delay is 6.154 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 12:02:00 1: [Freezemon] myFreezeMon: possible freeze starting at 12:01:58, delay is 2.266 possibly caused by: tmr-MAH_updateValues(Geschirrspueler) tmr-MAH_updateValues(Waermeschublade) tmr-MAH_updateValues(Dampfgarer) tmr-MAH_updateValues(Backofen) tmr-CODE(0x2d95ae0)(GetStatus) tmr-FW_closeInactiveClients(N/A) tmr-SamsungAV_Init(Fernseher) tmr-MQTT2_SERVER_keepaliveChecker(MQTT2_fhem)
2022.01.29 12:02:02 1: [Freezemon] myFreezeMon: possible freeze starting at 12:02:01, delay is 1.575 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:02:58 1: [Freezemon] myFreezeMon: possible freeze starting at 12:02:52, delay is 6.047 possibly caused by: tmr-FHEM::GardenaSmartBridge::getDevices(GardenaZentrale)
2022.01.29 12:03:58 1: [Freezemon] myFreezeMon: possible freeze starting at 12:03:53, delay is 5.875 possibly caused by: no bad guy found :-(
2022.01.29 12:04:02 1: [Freezemon] myFreezeMon: possible freeze starting at 12:04:01, delay is 1.372 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:04:59 1: [Freezemon] myFreezeMon: possible freeze starting at 12:04:54, delay is 5.721 possibly caused by: no bad guy found :-(
2022.01.29 12:06:00 1: [Freezemon] myFreezeMon: possible freeze starting at 12:05:55, delay is 5.52 possibly caused by: no bad guy found :-(
2022.01.29 12:06:03 1: [Freezemon] myFreezeMon: possible freeze starting at 12:06:02, delay is 1.171 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:07:01 1: [Freezemon] myFreezeMon: possible freeze starting at 12:06:56, delay is 5.555 possibly caused by: no bad guy found :-(
2022.01.29 12:08:02 1: [Freezemon] myFreezeMon: possible freeze starting at 12:07:57, delay is 5.417 possibly caused by: no bad guy found :-(
2022.01.29 12:08:06 1: [Freezemon] myFreezeMon: possible freeze starting at 12:08:04, delay is 2.614 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:09:03 1: [Freezemon] myFreezeMon: possible freeze starting at 12:08:58, delay is 5.282 possibly caused by: no bad guy found :-(
2022.01.29 12:10:04 1: [Freezemon] myFreezeMon: possible freeze starting at 12:09:59, delay is 5.48 possibly caused by: no bad guy found :-(
2022.01.29 12:10:10 1: [Freezemon] myFreezeMon: possible freeze starting at 12:10:07, delay is 3.095 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:11:05 1: [Freezemon] myFreezeMon: possible freeze starting at 12:11:00, delay is 5.647 possibly caused by: no bad guy found :-(
2022.01.29 12:12:06 1: [Freezemon] myFreezeMon: possible freeze starting at 12:12:01, delay is 5.31 possibly caused by: no bad guy found :-(
2022.01.29 12:12:11 1: [Freezemon] myFreezeMon: possible freeze starting at 12:12:08, delay is 3.815 possibly caused by: tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A) tmr-HttpUtils_TimeoutErr(N/A)
2022.01.29 12:12:13 1: [Freezemon] myFreezeMon: possible freeze starting at 12:12:12, delay is 1.067 possibly caused by: no bad guy found :-(

[zife]

Wegen Switch, wenn Der keine Weboberfläche hat: Du kannst mal auf Shell-Ebene prüfen, ob Deine Netzwerkkarte Fehler" wirft.
...
Bei "errors" etc. sollte 0 stehen (Es sei denn, Dein Rechner läuft schon seit Monaten)

Und noch eine spontane Frage:
Verwendest Du Presence o.Ä.?

Hier der Output von "IFCONFIG":

Code Auswählen Erweitern

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.178.50  netmask 255.255.255.0  broadcast 192.168.178.255
        inet6 2a01:41e3:18cd:ef00:e93:fcc2:660b:b8fe  prefixlen 64  scopeid 0x0<                                           global>
        inet6 2a01:41e3:2c70:5d00:ee17:ec17:696a:28ea  prefixlen 64  scopeid 0x0                                           <global>
        inet6 fe80::f2c0:df84:569:fc9d  prefixlen 64  scopeid 0x20<link>
        inet6 fd00::91bf:dcbd:163d:a05a  prefixlen 64  scopeid 0x0<global>
        ether b8:27:eb:68:0c:3a  txqueuelen 1000  (Ethernet)
        RX packets 2250988  bytes 496568310 (473.5 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 2124797  bytes 345868105 (329.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Lokale Schleife)
        RX packets 1605  bytes 116688 (113.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1605  bytes 116688 (113.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


So wie ich das sehe... keine Fehler.

Presence verwende ich nicht.

Allgemein: ich finde Eure Hilfsbereitschaft grandios. Danke!

[Wernieman]

Code Auswählen Erweitern

        RX packets 2250988  bytes 496568310 (473.5 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0

Ist nicht schlimm, sehe ich aus so ... ABER ... "dropped 2" behalte das mal im Auge.
Einmalig: Vergiss es (bei 2250988 Packete 2 droped ...)
Häufiger: Wenn jeden Tag mehr als 2 dazukommen würden .....

Hinweis:
Habe jetzt gerade mal bei mir geprüft. Meine Netzboot-Pi haben bei einer Update von 17 Tagen als Daten:

Code Auswählen Erweitern

        RX packets 24340769  bytes 5203370408 (4.8 GiB)
        RX errors 0  dropped 16  overruns 0  frame 0

Was total Unkritisch ist. Habe aber auch ein Monitoring (Zabbix) drauf, welches bei Problemen sofort "meckern" würde ....

Ergänzung:
Für Dein jetziges Problem ist dieses Ganze aber total Unkritisch!

Ergänzung2
Ich glaube immer noch nicht, das solche Probleme Dein FHEM auf 100% bringen kann. Wenn FHEM z.B. auf DNS wartet, verbraucht es keine CPU-Time, sondern eher wartet (oder? Lasse mich von FHEM-Interna-Spezialisten gerne korrigieren)
Was aber bekannt ist, das z.B. bei USB-Discover FHEM viel CPU-Last erzeugt. jetzt wirst Du im laufenden Betrieb kein USB-Discover machen .... trotzdem die Frage: Hast Du USB-Geräte in FHEM?

[zife]

ich hab 1 USB-Gerät am RASPI/in fhem: den Enocean-USB-Stick.

List:

Code Auswählen Erweitern


Internals:
   BaseID     FFBE4100
   ChipID     058B7C82
   DEF        ESP3 /dev/ttyUSB0@57600
   DeviceName /dev/ttyUSB0@57600
   FD         13
   FUUID      5f8dd7ad-f33f-93cd-74e8-2288b3260a69a70c
   LastID     FFBE417F
   MODEL      ESP3
   NAME       TCM_ESP3_0
   NOTIFYDEV  global
   NR         56
   NTFY_ORDER 45-TCM_ESP3_0
   PARTIAL   
   RSSI       -73
   STATE      initialized
   TYPE       TCM
   READINGS:
     2022-01-28 20:22:25   baseID          BaseID: FFBE4100 RemainingWriteCycles: 0A
     2022-01-28 20:22:25   maturity        01
     2022-01-28 20:22:25   repeater        RepEnable: 00 RepLevel: 00
     2022-01-28 20:22:25   state           initialized
     2022-01-28 20:22:25   version         APIVersion: 02060900 APPVersion: 020F0000 ChipID: 058B7C82 ChipVersion: 454F0103 Desc: GATEWAYCTRL
   helper:
     cdmSeq     2
     init_done  1
     telegramSentTimeLast 1643458461.26176
     BaseID:
       FFBE4100
     ChipID:
       058B7C82
     awaitCmdResp:
Attributes:
   icon       cul_868
   learningDev all
   room       Geraete
   sendInterval 0
   smartAckMailboxMax 0
   verbose    0


Dazu habe ich in global den USB-Check ausgesetzt:

Code Auswählen Erweitern


attr initialUsbCheck disable 1



Das Problem, dass fhem Schaltbefehle sehr häufig verzögert umsetzt, ist mein eigentliches Problem. Ob die laut TOP immer wieder auf 100% hochschnellende CPU-Last (meist für ca 3-6 Sekunden) der Grund dafür ist, ist nur meine erste Interpretation gewesen.