FHEM Freeze - was tun?

[Gunther]

Ich habe heute festgestellt, das FHEM nicht mehr ansprechbar ist.
Über Terminal komme ich noch auf die Oberfläche. Ein stop und Neustart hilft kurzfristig.

Die einigen Änderungen, die ich durchgeführt habe, sind an meinen TabletUI Seiten.

Im Log sieht es komisch aus. Freezes und irgendwie keine Connection zu meinen Netzwerkdevices.
Habt Ihr eine Idee, wie ich der Ursache auf den Leib gehe?

Hier mal ein Auszug aus dem Log:

Code Auswählen Erweitern

2017.12.04 16:01:12 1: Perfmon: possible freeze starting at 15:59:42, delay is 90.951
2017.12.04 16:01:12 3: CUL_HM set eg_ez_rauchmelder statusRequest
2017.12.04 16:01:12 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2017.12.04 16:01:12 3: BlockingCall for DS1010 was aborted
2017.12.04 16:01:12 3: BlockingCall for IMAC was aborted
2017.12.04 16:01:13 3: harmony: connected
2017.12.04 16:01:13 1: Timeout for WOL_Ping reached, terminated process 3990
2017.12.04 16:01:13 3: BlockingCall for winserver was aborted
2017.12.04 16:01:13 1: Timeout for WOL_Ping reached, terminated process 3991
2017.12.04 16:01:13 3: BlockingCall for Epson830 was aborted
2017.12.04 16:01:13 1: Timeout for WOL_Ping reached, terminated process 3992
2017.12.04 16:01:13 3: BlockingCall for DS2413 was aborted
2017.12.04 16:01:13 1: Timeout for WOL_Ping reached, terminated process 3993
2017.12.04 16:01:13 3: BlockingCall for MacBookPro2017 was aborted
2017.12.04 16:01:17 3: MeinWetter: write to https://query.yahooapis.com:443 timed out
2017.12.04 16:01:18 1: Calendar Abfall: retrieval failed with error message connect to https://www.google.com:443 timed out
2017.12.04 16:01:18 1: Calendar Abfall: retrieved no or empty data
2017.12.04 16:01:18 1: PERL WARNING: Use of uninitialized value $t in numeric le (<=) at ./FHEM/57_Calendar.pm line 602.
2017.12.04 16:01:18 1: PERL WARNING: Use of uninitialized value $t in numeric lt (<) at ./FHEM/57_Calendar.pm line 557.
2017.12.04 16:01:18 1: PERL WARNING: Use of uninitialized value $t in numeric lt (<) at ./FHEM/57_Calendar.pm line 555.
2017.12.04 16:01:19 3: ABFALL myAbfall - CALENDAR:Abfall triggered, updating ABFALL myAbfall ...
2017.12.04 16:01:19 3: ABFALL_UPDATE
2017.12.04 16:01:19 1: PERL WARNING: Use of uninitialized value $t in numeric gt (>) at ./FHEM/57_Calendar.pm line 611.
2017.12.04 16:01:19 1: PERL WARNING: Use of uninitialized value $t in numeric gt (>) at ./FHEM/57_Calendar.pm line 1915.
2017.12.04 16:01:19 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3996
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3997
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3998
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3999
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4000
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4001
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4002
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4003
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4004
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4005
2017.12.04 16:01:20 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 4008
2017.12.04 16:02:29 1: Perfmon: possible freeze starting at 16:01:13, delay is 76.233
2017.12.04 16:02:29 3: CUL_HM set og_sz_JalousieLinks statusRequest
2017.12.04 16:02:29 1: Timeout for WOL_Ping reached, terminated process 4100
2017.12.04 16:02:29 3: BlockingCall for InoKeyFingerprint2 was aborted
2017.12.04 16:02:29 1: Timeout for WOL_Ping reached, terminated process 4101
2017.12.04 16:02:29 3: BlockingCall for InoKeyFingerprint was aborted
2017.12.04 16:02:29 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2017.12.04 16:02:53 1: Perfmon: possible freeze starting at 16:02:30, delay is 23.02
2017.12.04 16:02:53 1: FRITZBOX Fritzbox_7390: Readout_Aborted.1865 Error: Timeout when reading Fritz!Box data.
2017.12.04 16:02:53 1: Timeout for MilightBridge_DoPing reached, terminated process 4118
2017.12.04 16:02:53 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2017.12.04 16:02:53 1: Timeout for WOL_Ping reached, terminated process 4123
2017.12.04 16:02:53 3: BlockingCall for winserver was aborted
2017.12.04 16:02:54 1: Timeout for WOL_Ping reached, terminated process 4124
2017.12.04 16:02:54 3: BlockingCall for DS1010 was aborted
2017.12.04 16:02:54 1: Timeout for WOL_Ping reached, terminated process 4125
2017.12.04 16:02:54 3: BlockingCall for IMAC was aborted
2017.12.04 16:02:54 1: Timeout for WOL_Ping reached, terminated process 4126
2017.12.04 16:02:54 3: BlockingCall for Epson830 was aborted
2017.12.04 16:02:54 1: Timeout for WOL_Ping reached, terminated process 4127
2017.12.04 16:02:54 3: BlockingCall for DS2413 was aborted
2017.12.04 16:02:54 1: Timeout for WOL_Ping reached, terminated process 4128
2017.12.04 16:02:54 3: BlockingCall for MacBookPro2017 was aborted
2017.12.04 16:02:54 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2017.12.04 16:02:54 3: MeinWetter: connect to https://query.yahooapis.com:443 timed out
2017.12.04 16:02:55 2: harmony: disconnect
2017.12.04 16:03:08 3: ENIGMA2 VUDuo2: ERROR: Unable to read tv bouquet '1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.favourites-sd.tv" ORDER BY bouquet' from device
2017.12.04 16:03:08 1: Perfmon: possible freeze starting at 16:02:54, delay is 14.57
2017.12.04 16:03:08 3: harmony: connected
2017.12.04 16:03:12 1: Perfmon: possible freeze starting at 16:03:09, delay is 3.006
2017.12.04 16:03:12 1: Timeout for MilightBridge_DoPing reached, terminated process 4145
2017.12.04 16:03:12 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2017.12.04 16:03:14 1: Perfmon: possible freeze starting at 16:03:13, delay is 1.462
2017.12.04 16:03:16 3: harmony: new config
2017.12.04 16:03:16 3: ENIGMA2 VUDuo2: ERROR: Unable to read tv bouquet '1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.favourites-sd.tv" ORDER BY bouquet' from device
2017.12.04 16:03:18 1: Perfmon: possible freeze starting at 16:03:15, delay is 3.373
2017.12.04 16:03:20 1: Perfmon: possible freeze starting at 16:03:19, delay is 1.285
2017.12.04 16:03:22 3: CUL_HM set og_sz_Wandthermostat_Climate desired-temp 18.5
2017.12.04 16:03:22 1: Perfmon: possible freeze starting at 16:03:21, delay is 1.832
2017.12.04 16:03:24 1: Perfmon: possible freeze starting at 16:03:23, delay is 1.437

Edit: Ein Hinweis noch: Ich habe vor 2-3 Tagen einige Statistics-Devices hinzugefügt (unter anderem Tendency). Hier werden ja ziemlich viele Readings erzeugt.
Kann das zu diesen Problemen führen?

[Gunther]

jetzt läuft es gerade wieder. komisch...

[Amenophis86]

Wenn du der Meinung bist, dass es ein bestimmtes Modul sein kann, setz es auf disable und schau, ob es wieder geht. Ansonsten kannst du auch mittels apptime mal schauen was dir so angezeigt wird.