FHEM Forum

FHEM => Anfängerfragen => Thema gestartet von: Gunther am 04 Januar 2018, 23:45:05

Titel: DOIFs crashen mein System
Beitrag von: Gunther am 04 Januar 2018, 23:45:05
Mein FHEM wollte eben nicht mehr. Nun habe ich 5 DOIFS, die ich anscheinend nicht gut genug getestet habe rausgenommen und komme wenigstens wieder auf die FHEM Oberfläche.
Das Log wurde aber weiter geschrieben, trotz fehlenden Zugriffs.

Ich habe für drei Kühlschränke 5 DOIFS.

Folgende Logmeldungen bekomme ich (Auszug aus dem Logfile):
2018.01.04 22:51:18 3: eval: doif_Auftauwarnung_Eisfach_VorratKG: warning in condition c01
2018.01.04 22:51:18 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8833) line 1.
2018.01.04 22:51:18 3: eval: doif_Auftauwarnung_Eisfach_VorratKG: warning in condition c02
2018.01.04 22:52:13 1: Perfmon: possible freeze starting at 22:50:51, delay is 82.325
2018.01.04 22:52:13 1: Timeout for WOL_Ping reached, terminated process 3697
2018.01.04 22:52:13 3: BlockingCall for winserver was aborted
2018.01.04 22:52:13 1: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 3696
2018.01.04 22:52:14 1: FRITZBOX Fritzbox_7390: Readout_Aborted.1893 Error: Timeout when reading Fritz!Box data.
2018.01.04 22:52:15 2: harmony: disconnect
2018.01.04 22:52:40 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8944) line 1.
2018.01.04 22:52:40 3: eval: doif_Auftauwarnung_Eisfach_VorratKG: warning in condition c01
2018.01.04 22:52:40 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8945) line 1.
2018.01.04 22:52:40 3: eval: doif_Auftauwarnung_Eisfach_VorratKG: warning in condition c02
2018.01.04 22:52:40 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8946) line 1.
2018.01.04 22:52:40 3: eval: doif_Auftauwarnung_Kuehlschrank_VorratKG: warning in condition c01
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8951) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Eisfach_Kueche: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8952) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Eisfach_VorratKG: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8953) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Eisschrank_FlurKG: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8954) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Kuehlschrank_Kueche: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8959) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Eisfach_Kueche: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8960) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Eisfach_VorratKG: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8961) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Eisschrank_FlurKG: warning in condition c02
2018.01.04 22:52:41 1: PERL WARNING: Argument "" isn't numeric in addition (+) at (eval 8962) line 1.
2018.01.04 22:52:41 3: eval: doif_Auftauwarnung_Kuehlschrank_Kueche: warning in condition c02


Was sagen mir die Fehlermeldungen? Können diese mein System killen?

Eines meiner DOIFS:
define doif_Auftauwarnung_Kuehlschrank_Kueche DOIF ([eg_ku_Kuehlschrank:temperature] >= ([eg_ku_Kuehlschrank_solltemp:state] + [eg_ku_Kuehlschrank_difftemp:state]))\
(set kuehlwarnung an) \
(setre
ading kuehlwarnung device Kühlschrank Küche)\
DOELSEIF \
([eg_ku_Kuehlschrank:temperature] <= ([eg_ku_Kuehlschrank_solltemp:state] + [eg_ku_Kuehlschrank_difftemp:state]) and [kuehlwarnung:device] eq "Kühlschrank Küche")\
(set kuehlwarnung aus) \
(deletereading kuehlwarnung device)
attr doif_Auftauwarnung_Kuehlschrank_Kueche do always
attr doif_Auftauwarnung_Kuehlschrank_Kueche group Kuehlschrank
attr doif_Auftauwarnung_Kuehlschrank_Kueche room Logik


EDIT:
Habe heute mein System geupdatet. Kann das damit zusammenhängen?

EDIT 2: Mist mein System startet gerade trotzdem nicht... Hmm :-(
Titel: Antw:DOIFs crashen mein System
Beitrag von: Gunther am 04 Januar 2018, 23:54:30
Hier mal ein Auszug aus meinem Logfile (Nachdem ich ein Backup der fhem.cfg von 18 Uhr wieder eingespielt habe, wo leider noch Milightkram usw. drin ist, den ich heute rausgeworfen habe).

2018.01.04 23:36:31 1: Perfmon: possible freeze starting at 23:36:28, delay is 3.612
2018.01.04 23:36:32 2: HueBridge: http request failed: http://192.168.0.177/api/FByzLNQkCmZAL-1YudCHtx1u5bHmS6fo3dSr4iSP: empty answer received
2018.01.04 23:36:34 1: Timeout for MilightBridge_DoPing reached, terminated process 3134
2018.01.04 23:36:34 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:36:36 1: Perfmon: possible freeze starting at 23:36:35, delay is 1.154
2018.01.04 23:36:43 1: Perfmon: possible freeze starting at 23:36:42, delay is 1.478
2018.01.04 23:36:47 1: Perfmon: possible freeze starting at 23:36:45, delay is 2.668
2018.01.04 23:36:49 1: Perfmon: possible freeze starting at 23:36:48, delay is 1.401
2018.01.04 23:36:52 1: Timeout for MilightBridge_DoPing reached, terminated process 3136
2018.01.04 23:36:52 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:36:52 1: Perfmon: possible freeze starting at 23:36:50, delay is 2.162
2018.01.04 23:36:54 1: Perfmon: possible freeze starting at 23:36:53, delay is 1.423
2018.01.04 23:37:02 1: Perfmon: possible freeze starting at 23:36:57, delay is 5.882
2018.01.04 23:37:05 1: Timeout for MilightBridge_DoPing reached, terminated process 3158
2018.01.04 23:37:05 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:37:15 1: Perfmon: possible freeze starting at 23:37:14, delay is 1.126
2018.01.04 23:37:23 1: Perfmon: possible freeze starting at 23:37:22, delay is 1.699
2018.01.04 23:37:41 3: CUL_HM set eg_ki_licht_lichtrahmen_mitte getConfig
2018.01.04 23:37:41 1: Perfmon: possible freeze starting at 23:37:40, delay is 1.681
2018.01.04 23:37:54 1: Perfmon: possible freeze starting at 23:37:46, delay is 8.289
2018.01.04 23:37:58 1: Perfmon: possible freeze starting at 23:37:55, delay is 3.819
2018.01.04 23:37:58 1: Timeout for MilightBridge_DoPing reached, terminated process 3178
2018.01.04 23:37:58 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:38:00 3: CUL_HM set eg_ki_licht_lichtrahmen_pano getConfig
2018.01.04 23:38:07 1: Timeout for WOL_Ping reached, terminated process 3179
2018.01.04 23:38:07 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.04 23:38:07 1: Perfmon: possible freeze starting at 23:37:59, delay is 8.344
2018.01.04 23:38:07 1: Timeout for WOL_Ping reached, terminated process 3180
2018.01.04 23:38:07 3: BlockingCall for winserver was aborted
2018.01.04 23:38:08 3: CUL_HM set eg_ki_licht_lichtrahmen_rechts getConfig
2018.01.04 23:38:10 1: Perfmon: possible freeze starting at 23:38:08, delay is 2.785
2018.01.04 23:38:18 1: Perfmon: possible freeze starting at 23:38:11, delay is 7.403
2018.01.04 23:38:18 1: Timeout for MilightBridge_DoPing reached, terminated process 3197
2018.01.04 23:38:18 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:38:20 3: CUL_HM set og_fl_licht_lichtrahmen_links getConfig
2018.01.04 23:38:20 1: Timeout for WOL_Ping reached, terminated process 3198
2018.01.04 23:38:20 3: BlockingCall for DS2413 was aborted
2018.01.04 23:38:20 1: Timeout for WOL_Ping reached, terminated process 3199
2018.01.04 23:38:20 3: BlockingCall for DS1010 was aborted
2018.01.04 23:38:20 1: Timeout for WOL_Ping reached, terminated process 3200
2018.01.04 23:38:20 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:38:20 1: Timeout for WOL_Ping reached, terminated process 3201
2018.01.04 23:38:20 3: BlockingCall for Epson830 was aborted
2018.01.04 23:38:27 1: Perfmon: possible freeze starting at 23:38:19, delay is 8.563
2018.01.04 23:38:27 1: Timeout for WOL_Ping reached, terminated process 3202
2018.01.04 23:38:27 3: BlockingCall for MacBookPro2017 was aborted
2018.01.04 23:38:27 1: Timeout for WOL_Ping reached, terminated process 3203
2018.01.04 23:38:27 3: BlockingCall for IMAC was aborted
2018.01.04 23:38:29 3: CUL_HM set og_fl_licht_lichtrahmen_rechts getConfig
2018.01.04 23:38:33 1: Perfmon: possible freeze starting at 23:38:28, delay is 5.081
2018.01.04 23:38:36 3: CUL_HM set og_sz_JalousieLinks getConfig
2018.01.04 23:38:36 1: Perfmon: possible freeze starting at 23:38:34, delay is 2.016
2018.01.04 23:38:36 1: Timeout for MilightBridge_DoPing reached, terminated process 3204
2018.01.04 23:38:36 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:38:36 2: HueBridge: http request failed: http://192.168.0.177/api/FByzLNQkCmZAL-1YudCHtx1u5bHmS6fo3dSr4iSP/lights: empty answer received
2018.01.04 23:38:44 1: Perfmon: possible freeze starting at 23:38:42, delay is 2.113
2018.01.04 23:38:51 1: Perfmon: possible freeze starting at 23:38:50, delay is 1.885
2018.01.04 23:39:00 1: Perfmon: possible freeze starting at 23:38:58, delay is 2.594
2018.01.04 23:39:34 1: Perfmon: possible freeze starting at 23:39:01, delay is 33.95
2018.01.04 23:39:36 2: harmony: disconnect
2018.01.04 23:40:08 1: Perfmon: possible freeze starting at 23:39:35, delay is 33.652
2018.01.04 23:40:08 1: Timeout for MilightBridge_DoPing reached, terminated process 3224
2018.01.04 23:40:08 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:40:08 3: harmony: connected
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3225
2018.01.04 23:40:09 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3226
2018.01.04 23:40:09 3: BlockingCall for winserver was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3227
2018.01.04 23:40:09 3: BlockingCall for DS2413 was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3228
2018.01.04 23:40:09 3: BlockingCall for DS1010 was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3229
2018.01.04 23:40:09 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3230
2018.01.04 23:40:09 3: BlockingCall for Epson830 was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3231
2018.01.04 23:40:09 3: BlockingCall for MacBookPro2017 was aborted
2018.01.04 23:40:09 1: Timeout for WOL_Ping reached, terminated process 3232
2018.01.04 23:40:09 3: BlockingCall for IMAC was aborted
2018.01.04 23:40:10 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2018.01.04 23:40:52 1: Perfmon: possible freeze starting at 23:40:09, delay is 43.458
2018.01.04 23:41:05 1: Calendar Abfall: retrieval failed with error message <hidden>: Can't connect(2) to https://www.google.com:443:  SSL connect attempt failed because of handshake problems error:00000000:lib(0):func(0):reason(0)
2018.01.04 23:41:05 1: Calendar Abfall: retrieved no or empty data
2018.01.04 23:41:05 1: PERL WARNING: Use of uninitialized value $t in numeric le (<=) at ./FHEM/57_Calendar.pm line 609.
2018.01.04 23:41:05 1: PERL WARNING: Use of uninitialized value $t in numeric lt (<) at ./FHEM/57_Calendar.pm line 564.
2018.01.04 23:41:05 1: PERL WARNING: Use of uninitialized value $t in numeric lt (<) at ./FHEM/57_Calendar.pm line 562.
2018.01.04 23:41:06 3: ABFALL myAbfall - CALENDAR:Abfall triggered, updating ABFALL myAbfall ...
2018.01.04 23:41:06 3: ABFALL_UPDATE
2018.01.04 23:41:06 1: PERL WARNING: Use of uninitialized value $t in numeric gt (>) at ./FHEM/57_Calendar.pm line 618.
2018.01.04 23:41:06 1: PERL WARNING: Use of uninitialized value $t in numeric gt (>) at ./FHEM/57_Calendar.pm line 1924.
2018.01.04 23:41:41 1: Perfmon: possible freeze starting at 23:40:53, delay is 48.18
2018.01.04 23:41:41 1: Timeout for MilightBridge_DoPing reached, terminated process 3283
2018.01.04 23:41:41 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:41:41 1: Timeout for WOL_Ping reached, terminated process 3299
2018.01.04 23:41:41 3: BlockingCall for winserver was aborted
2018.01.04 23:41:41 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2018.01.04 23:41:41 1: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 3281
2018.01.04 23:41:41 1: FRITZBOX Fritzbox: Readout_Aborted.1893 Error: Timeout when reading Fritz!Box data.
2018.01.04 23:41:41 1: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 3282
2018.01.04 23:41:42 1: FRITZBOX Fritzbox_7390: Readout_Aborted.1893 Error: Timeout when reading Fritz!Box data.
2018.01.04 23:42:24 1: Perfmon: possible freeze starting at 23:41:42, delay is 42.54
2018.01.04 23:42:24 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.04 23:42:24 3: BlockingCall for DS2413 was aborted
2018.01.04 23:42:24 3: BlockingCall for DS1010 was aborted
2018.01.04 23:42:24 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:42:24 3: BlockingCall for Epson830 was aborted
2018.01.04 23:42:24 3: BlockingCall for MacBookPro2017 was aborted
2018.01.04 23:42:24 1: Timeout for WOL_Ping reached, terminated process 3322
2018.01.04 23:42:24 3: BlockingCall for IMAC was aborted
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3284
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3285
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3286
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3290
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3292
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3293
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3294
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3295
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3296
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3297
2018.01.04 23:42:24 1: Timeout for TRAFFIC_DoUpdate reached, terminated process 3298
2018.01.04 23:42:27 3: harmony: new config
2018.01.04 23:43:10 1: Perfmon: possible freeze starting at 23:42:25, delay is 45.259
2018.01.04 23:43:10 1: Timeout for MilightBridge_DoPing reached, terminated process 3345
2018.01.04 23:43:10 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:43:10 1: Timeout for WOL_Ping reached, terminated process 3346
2018.01.04 23:43:10 3: BlockingCall for winserver was aborted
2018.01.04 23:43:10 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2018.01.04 23:43:47 1: Perfmon: possible freeze starting at 23:43:11, delay is 36.409
2018.01.04 23:43:48 2: harmony: disconnect
2018.01.04 23:44:19 1: Perfmon: possible freeze starting at 23:43:48, delay is 31.465
2018.01.04 23:44:19 1: Timeout for MilightBridge_DoPing reached, terminated process 3363
2018.01.04 23:44:19 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:44:19 3: BlockingCall for DS2413 was aborted
2018.01.04 23:44:19 3: harmony: connected
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3364
2018.01.04 23:44:19 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3366
2018.01.04 23:44:19 3: BlockingCall for DS1010 was aborted
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3367
2018.01.04 23:44:19 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3368
2018.01.04 23:44:19 3: BlockingCall for Epson830 was aborted
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3369
2018.01.04 23:44:19 3: BlockingCall for MacBookPro2017 was aborted
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3370
2018.01.04 23:44:19 3: BlockingCall for IMAC was aborted
2018.01.04 23:44:19 1: Timeout for WOL_Ping reached, terminated process 3371
2018.01.04 23:44:19 3: BlockingCall for winserver was aborted
2018.01.04 23:44:19 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2018.01.04 23:44:53 1: Perfmon: possible freeze starting at 23:44:20, delay is 33.317
2018.01.04 23:45:24 1: Perfmon: possible freeze starting at 23:44:54, delay is 30.291
2018.01.04 23:45:24 1: Timeout for MilightBridge_DoPing reached, terminated process 3389
2018.01.04 23:45:24 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:45:24 1: Timeout for WOL_Ping reached, terminated process 3390
2018.01.04 23:45:24 3: BlockingCall for winserver was aborted
2018.01.04 23:45:24 2: HueBridge: http request failed: write to http://192.168.0.177:80 timed out
2018.01.04 23:45:57 1: Perfmon: possible freeze starting at 23:45:25, delay is 32.06
2018.01.04 23:45:57 3: BlockingCall for DS2413 was aborted
2018.01.04 23:45:57 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.04 23:45:57 1: Timeout for WOL_Ping reached, terminated process 3447
2018.01.04 23:45:57 3: BlockingCall for DS1010 was aborted
2018.01.04 23:45:57 1: Timeout for WOL_Ping reached, terminated process 3448
2018.01.04 23:45:57 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:45:57 1: Timeout for WOL_Ping reached, terminated process 3449
2018.01.04 23:45:57 3: BlockingCall for Epson830 was aborted
2018.01.04 23:45:57 1: Timeout for WOL_Ping reached, terminated process 3450
2018.01.04 23:45:57 3: BlockingCall for MacBookPro2017 was aborted
2018.01.04 23:45:57 1: Timeout for WOL_Ping reached, terminated process 3451
2018.01.04 23:45:57 3: BlockingCall for IMAC was aborted
2018.01.04 23:45:57 3: MeinWetter: write to https://query.yahooapis.com:443 timed out
2018.01.04 23:45:59 3: harmony: new config
2018.01.04 23:46:27 1: Perfmon: possible freeze starting at 23:45:58, delay is 29.323
2018.01.04 23:46:27 1: Timeout for MilightBridge_DoPing reached, terminated process 3454
2018.01.04 23:46:27 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:46:27 1: Timeout for WOL_Ping reached, terminated process 3455
2018.01.04 23:46:27 3: BlockingCall for winserver was aborted
2018.01.04 23:46:27 1: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 3443
2018.01.04 23:46:28 1: FRITZBOX Fritzbox: Readout_Aborted.1893 Error: Timeout when reading Fritz!Box data.
2018.01.04 23:46:28 1: Timeout for FRITZBOX_Readout_Run_Web reached, terminated process 3444
2018.01.04 23:46:28 1: FRITZBOX Fritzbox_7390: Readout_Aborted.1893 Error: Timeout when reading Fritz!Box data.
2018.01.04 23:46:34 1: Perfmon: possible freeze starting at 23:46:28, delay is 6.22
2018.01.04 23:46:36 2: HueBridge: http request failed: http://192.168.0.177/api/FByzLNQkCmZAL-1YudCHtx1u5bHmS6fo3dSr4iSP/lights: empty answer received
2018.01.04 23:46:36 1: Perfmon: possible freeze starting at 23:46:35, delay is 1.407
2018.01.04 23:46:38 1: Perfmon: possible freeze starting at 23:46:37, delay is 1.545
2018.01.04 23:46:40 1: Perfmon: possible freeze starting at 23:46:39, delay is 1.714
2018.01.04 23:46:43 1: Timeout for MilightBridge_DoPing reached, terminated process 3472
2018.01.04 23:46:43 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:46:43 1: Perfmon: possible freeze starting at 23:46:41, delay is 2.562
2018.01.04 23:46:48 1: Perfmon: possible freeze starting at 23:46:45, delay is 3.349
2018.01.04 23:46:50 1: Perfmon: possible freeze starting at 23:46:49, delay is 1.458
2018.01.04 23:46:53 1: Perfmon: possible freeze starting at 23:46:52, delay is 1.946
2018.01.04 23:46:55 1: Perfmon: possible freeze starting at 23:46:54, delay is 1.901
2018.01.04 23:46:59 1: Timeout for MilightBridge_DoPing reached, terminated process 3473
2018.01.04 23:46:59 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:46:59 1: Perfmon: possible freeze starting at 23:46:56, delay is 3.147
2018.01.04 23:47:02 1: Perfmon: possible freeze starting at 23:47:01, delay is 1.328
2018.01.04 23:47:03 1: Timeout for WOL_Ping reached, terminated process 3475
2018.01.04 23:47:03 3: BlockingCall for InoKeyFingerprint2 was aborted
2018.01.04 23:47:04 1: Timeout for WOL_Ping reached, terminated process 3476
2018.01.04 23:47:04 3: BlockingCall for DS1010 was aborted
2018.01.04 23:47:04 1: Timeout for WOL_Ping reached, terminated process 3477
2018.01.04 23:47:04 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:47:04 1: Timeout for WOL_Ping reached, terminated process 3478
2018.01.04 23:47:04 3: BlockingCall for Epson830 was aborted
2018.01.04 23:47:04 1: Timeout for WOL_Ping reached, terminated process 3479
2018.01.04 23:47:04 3: BlockingCall for MacBookPro2017 was aborted
2018.01.04 23:47:04 1: Timeout for WOL_Ping reached, terminated process 3480
2018.01.04 23:47:04 3: BlockingCall for IMAC was aborted
2018.01.04 23:47:04 1: Timeout for WOL_Ping reached, terminated process 3481
2018.01.04 23:47:04 3: BlockingCall for winserver was aborted
2018.01.04 23:47:05 1: Perfmon: possible freeze starting at 23:47:04, delay is 1.912
2018.01.04 23:47:14 1: Perfmon: possible freeze starting at 23:47:12, delay is 2.627
2018.01.04 23:47:24 1: Perfmon: possible freeze starting at 23:47:15, delay is 9.926
2018.01.04 23:47:34 1: Perfmon: possible freeze starting at 23:47:25, delay is 9.766
2018.01.04 23:47:37 1: Perfmon: possible freeze starting at 23:47:35, delay is 2.875
2018.01.04 23:47:37 1: Timeout for MilightBridge_DoPing reached, terminated process 3500
2018.01.04 23:47:37 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:47:40 1: Perfmon: possible freeze starting at 23:47:38, delay is 2.24
2018.01.04 23:47:40 1: Timeout for WOL_Ping reached, terminated process 3501
2018.01.04 23:47:40 3: BlockingCall for winserver was aborted
2018.01.04 23:47:46 1: Perfmon: possible freeze starting at 23:47:45, delay is 1.341
2018.01.04 23:47:47 3: harmony: IODev for device 43861964 is harmony
2018.01.04 23:47:54 1: Perfmon: possible freeze starting at 23:47:47, delay is 7.55
2018.01.04 23:47:56 1: Perfmon: possible freeze starting at 23:47:55, delay is 1.684
2018.01.04 23:47:56 1: Timeout for MilightBridge_DoPing reached, terminated process 3502
2018.01.04 23:47:56 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:48:02 1: Perfmon: possible freeze starting at 23:48:01, delay is 1.549
2018.01.04 23:48:10 1: Perfmon: possible freeze starting at 23:48:09, delay is 1.138
2018.01.04 23:48:15 1: Perfmon: possible freeze starting at 23:48:12, delay is 3.032
2018.01.04 23:48:18 1: Perfmon: possible freeze starting at 23:48:17, delay is 1.178
2018.01.04 23:48:21 1: Perfmon: possible freeze starting at 23:48:19, delay is 2.685
2018.01.04 23:48:23 1: Perfmon: possible freeze starting at 23:48:22, delay is 1.18
2018.01.04 23:48:23 1: Timeout for MilightBridge_DoPing reached, terminated process 3536
2018.01.04 23:48:23 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:48:29 1: Perfmon: possible freeze starting at 23:48:25, delay is 4.64
2018.01.04 23:48:34 1: Perfmon: possible freeze starting at 23:48:30, delay is 4.842
2018.01.04 23:48:39 1: Perfmon: possible freeze starting at 23:48:37, delay is 2.996
2018.01.04 23:48:41 3: CUL_HM set eg_ki_steckdose_beamer_Sw off
2018.01.04 23:48:41 3: CUL_HM set eg_ki_steckdose_subwoofer_Sw off
2018.01.04 23:48:41 3: CUL_HM set eg_ki_steckdose off
2018.01.04 23:48:47 3: CUL_HM set eg_ki_steckdose_beamer_Sw off
2018.01.04 23:48:47 3: CUL_HM set eg_ki_steckdose_beamer_Sw off
2018.01.04 23:48:48 3: CUL_HM set eg_ki_steckdose_subwoofer_Sw off
2018.01.04 23:48:48 3: CUL_HM set eg_ki_steckdose_subwoofer_Sw off
2018.01.04 23:48:49 1: Perfmon: possible freeze starting at 23:48:40, delay is 9.25
2018.01.04 23:48:51 1: Perfmon: possible freeze starting at 23:48:50, delay is 1.554
2018.01.04 23:48:53 1: Timeout for WOL_Ping reached, terminated process 3542
2018.01.04 23:48:53 3: BlockingCall for winserver was aborted
2018.01.04 23:49:03 1: Perfmon: possible freeze starting at 23:49:01, delay is 2.353
2018.01.04 23:49:05 1: Perfmon: possible freeze starting at 23:49:04, delay is 1.034
2018.01.04 23:49:08 1: Perfmon: possible freeze starting at 23:49:06, delay is 2.367
2018.01.04 23:49:10 1: Perfmon: possible freeze starting at 23:49:09, delay is 1.283
2018.01.04 23:49:12 1: Timeout for WOL_Ping reached, terminated process 3566
2018.01.04 23:49:12 3: BlockingCall for InoKeyFingerprint was aborted
2018.01.04 23:49:16 1: Timeout for MilightBridge_DoPing reached, terminated process 3576
2018.01.04 23:49:16 3: BlockingCall for eg_ki_MilightBridge_Leuchtkaesten was aborted
2018.01.04 23:49:20 1: Perfmon: possible freeze starting at 23:49:18, delay is 2.215
2018.01.04 23:49:29 1: Perfmon: possible freeze starting at 23:49:27, delay is 2.677



Gerade startet FHEM mal wieder - ändert sich vielleicht gleich wieder...
Speicherplatz habe ich noch genügend auf der SD Karte.

Also: erstmal interessieren mich die Fehlermeldungen bzgl. der DOIFs. Wenn da mal einer der erfahrenen User draufschauen mag, wäre das klasse.
Titel: Antw:DOIFs crashen mein System
Beitrag von: Damian am 05 Januar 2018, 00:28:31
Die DOIF-Warnungen sind harmlos und bedeuten nur, dass du keine Werte, die nicht Zahlen sind, addieren kannst. Das hat mit deinen freeze/BlockingCall-Meldungen nichts zu tun.
Titel: Antw:DOIFs crashen mein System
Beitrag von: Gunther am 05 Januar 2018, 00:30:17
habe meine Milight Devices mal händisch aus der fhem.cfg gelöscht und jetzt läuft FHEM seit 15 Min. stabil...
komischerweise gab es die schon lange