seit dem heutigem Update, Fehler in Presence-Modul!

[Markus Bloch]

Kann bitte jemand seine Konfiguration so weiter laufen lassen? Es sind ja aktuell "nur" viele Logmeldungen. Die Checks werden ja dazwischen immer wieder durchgeführt. Ich habe eine Änderung heute in PRESENCE eingecheckt um eine genauere Fehlermeldung zu erhalten, warum der Check abgebrochen wurde. Das gibt es für euch ab morgen via update. Ich vermute ein Fehler in Blocking.pm bei der Prozessverwaltung.

Auf meiner Umgebung tritt dieser Fehler nicht auf und kann das ganze daher nicht nachstellen.

@Rudi: hast du noch Ideen, wie man das ganze in Blocking.pm genauer debuggen kann?

Vielen Dank

dumme Frage wie macht man denn ein downgrade (gibt es dafür einen Befehl in fhem)?

Ja, "restore": http://commandref.fhem.de/#restore

Gruß
Markus

[Kawaci]

Morgen hab auch was in meiner logfile das glaube ich damit zusammen hängt! Reizt bei anderen dieser fhemler auch den cpu aus? nach nem Neustart gehts dann wieder und ich finde nur diese Fehler in der logfile

Code Auswählen Erweitern


50 1: PERL WARNING: Use of uninitialized value $uCmd in concatenation (.) or string at ./FHEM/42_SYSMON.pm line 1350.
2017.10.05 05:50:41 2: ESPEasy espBridge_192.168.x.xxx_20106: No basic authentication active but credentials received
2017.10.05 05:50:44 1: 192.168.1.127:1883 reappeared (Mosquitto)
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:51:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:43903: IO::Socket::INET: connect: Connection timed out
2017.10.05 05:52:50 2: ESPEasy espBridge_192.168.x.xxx_26291: No basic authentication active but credentials received
2017.10.05 05:52:59 1: PERL WARNING: Use of uninitialized value $uInterval in concatenation (.) or string at ./FHEM/42_SYSMON.pm line 1350.
2017.10.05 05:52:59 1: PERL WARNING: Use of uninitialized value $uComment in concatenation (.) or string at ./FHEM/42_SYSMON.pm line 1350.


[mkress]

Update läuft gerade.
Problem ist, dass wohl immer für ein paar Milli-Sekunden das Gerät auf Absent geht und dadurch mein doif auf das Event anspringt. Dadurch schaltet sich mein Zimmerbrunnen teilweise im Minuten-Takt an und wieder aus -

Die ersten Logs nach Neustart

Code Auswählen Erweitern

PRESENCE (presence_YamahaAvr) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:53:38 3: YAMAHA_AVR (AV_Receiver) - could not execute command on device AV_Receiver. Please turn on your device in case of deactivated network standby or check for correct hostaddress.
2017.10.05 08:53:32 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:53:32 2: PRESENCE (HandyMarkus) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:53:32 3: FritzBoxMonitor device opened
2017.10.05 08:53:31 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:53:31 2: PRESENCE (HandyMarkus) - device could not be checked (retrying in 10 seconds): Process died prematurely

[l2r]

moin,

hier auch noch ein paar Logauszüge von mir

Code Auswählen Erweitern

2017.10.05 08:45:30 2: PRESENCE (pr_piPrintSRV) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:45:30 2: PRESENCE (pr_piWeb) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:45:30 2: PRESENCE (pre_IPCam) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:45:30 2: PRESENCE (pr_piPrintSRV) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:45:30 2: PRESENCE (pre_IPCam) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:45:30 2: PRESENCE (pr_piWeb) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:45:33 2: PRESENCE (pr_piFHEM2FHEM) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:45:33 2: PRESENCE (pr_piFHEM2FHEM) - check returned a valid result after 1 unsuccesful retry

gruß Michael

[CoolTux]

Hier melden sich auch Leute.
https://forum.fhem.de/index.php/topic,60595.msg694787.html#msg694787

In dem hier gemeldeten Modul wird Blocking.pm verwendet.

@Rudi
Müssen gegebenenfalls die Module welche Blockieren.pm verwenden noch angepasst werden?


Grüße

[mkress]

Ich habe auch ein structure um mehrere Geräte (presence) zusammen zufassen - evtl. spielt das da auch mit rein...

[karl0123]

Es ist nicht nur das Log. Presence ist auch deutlich unzuverlässiger geworden. Mit der neuen Version (es mag an Blocking.pm liegen) spielt FHEM, wenn es auf PRESENCE als Automatisierungstrigger verwendet, völlig verrückt, weil Devices ständig absent und sofort wieder present gehen, obwohl es keine Probleme mit diesen Devices gibt. Da ich keine Zeit hatte, das ganze genauer zu untersuchen, bin ich zurück auf altes Blocking.pm und auf altes PRESENCE.

[CoolTux]

Ich habe mir erlaubt einen allgemeinen Thread für das Problem zu eröffnen. Ich denke mal es hilft wenn dort weiter gemacht wird da mehrere Module betroffen sind.

https://forum.fhem.de/index.php/topic,77556.0.html

[n0bbi]

Update läuft gerade.
Problem ist, dass wohl immer für ein paar Milli-Sekunden das Gerät auf Absent geht und dadurch mein doif auf das Event anspringt. Dadurch schaltet sich mein Zimmerbrunnen teilweise im Minuten-Takt an und wieder aus -

Die ersten Logs nach Neustart

Code Auswählen Erweitern

PRESENCE (presence_YamahaAvr) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:53:38 3: YAMAHA_AVR (AV_Receiver) - could not execute command on device AV_Receiver. Please turn on your device in case of deactivated network standby or check for correct hostaddress.
2017.10.05 08:53:32 2: PRESENCE (HandySteffi) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:53:32 2: PRESENCE (HandyMarkus) - check returned a valid result after 1 unsuccesful retry
2017.10.05 08:53:32 3: FritzBoxMonitor device opened
2017.10.05 08:53:31 2: PRESENCE (HandySteffi) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 08:53:31 2: PRESENCE (HandyMarkus) - device could not be checked (retrying in 10 seconds): Process died prematurely

Wenn dich das sonst nicht stört, hilft hier auch schon der WAIT-Parameter ganz gut weiter. Damit kann man zumindest die ganz kurzfristigen Statusänderungen abfedern...

[rudolfkoenig]

@Rudi: hast du noch Ideen, wie man das ganze in Blocking.pm genauer debuggen kann?

Die letzte Aenderung bewirkt "nur", dass abortFn aufgerufen wird, falls kill(0, $pid) Fehler meldet.
Fuers Letztere kommt nur das Sterben als Ursache in Verdacht, Berechtigungsprobleme kann ich mir nicht vorstellen.

Hypothese: Bei mehreren parallel gestarteten Prozessen melden zwei+ Prozesse parallel Vollzug. Bei der Bearbeitung der ersten "Fertig" Meldung werden die anderen als "tot" festgestellt, ohne deren "Fertig" Meldung zu kennen, und dadurch als "fruehzeitig verstorbern" markiert => abortFn aufgerufen.

Ich habe Blocking.pm geaendert: Falls ein abortFn spezifiziert wurde, dann wird vor dem Aufruf der blockierenden Funktion eine Verbindung zum Haupt-FHEM hergestellt, und falls beim "Pruefen auf tot" diese Verbindung noch existiert, dann dieser Prozess als noch lebendig betrachtet. blockinginfo gibt die Verbindung per "ConnectedVia" aus, andersherum kann man auch pruefen mit "list TYPE=telnet BlockingCall" kriegt man alle laufenden Blocking-Prozesse mit AbortFn raus.

Leider konnte ich das auch nicht testen (ich kriege das Problem nicht reproduziert), bin also auf Feedback angewiesen.
Falls jemand eine bessere/einfachere Loesung fuer die Vermeidung des Problems kennt, bitte melden.

[Tom111]

Hab gerade mal blocking.pm und 73_PRESENCE.pm geupdatet, wie Markus sagte, wollte er sehen wie jetzt die Meldungen aussehen,...
bitte sehr:

Code Auswählen Erweitern

2017.10.05 11:38:53 0: Server shutdown
2017.10.05 11:38:55 1: BlockingInformParent (BlockingStart): Can't connect to localhost:42051: IO::Socket::INET: connect: Connection refused
2017.10.05 11:38:55 1: BlockingInformParent (PRESENCE_ProcessLocalScan): Can't connect to localhost:42051: IO::Socket::INET: connect: Connection refused
2017.10.05 11:38:56 1: Including fhem.cfg
2017.10.05 11:38:56 3: telnetPort: port 7072 opened
2017.10.05 11:38:56 3: WEB: port 8083 opened
2017.10.05 11:38:56 3: WEBphone: port 8084 opened
2017.10.05 11:38:56 3: WEBtablet: port 8085 opened
2017.10.05 11:38:57 2: eventTypes: loaded 1878 events from ./log/eventTypes.txt
2017.10.05 11:38:57 3: Opening CUL_0 device /dev/ttyACM0
2017.10.05 11:38:57 3: Setting CUL_0 serial parameters to 9600,8,N,1
2017.10.05 11:38:57 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2017.10.05 11:38:57 3: CUL_0 device opened
2017.10.05 11:39:05 1: Including ./log/fhem.save
2017.10.05 11:39:06 0: Featurelevel: 5.8
2017.10.05 11:39:06 0: Server started with 345 defined entities (fhem.pl:15182/2017-10-03 perl:5.014002 os:linux user:fhem pid:5548)
2017.10.05 11:39:07 3: telnetForBlockingFn_1507196347: port 38887 opened
2017.10.05 11:39:10 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (CAM_09_Raspberry) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Comp_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (FritzBox) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Homepage) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Powerline_Keller) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Powerline_Wohnen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Repeater_300E) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Tab_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Lap_LAN_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Laptop_LAN) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Laptop_WLAN) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Raspberry_Pi) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Tablet_XORO) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Comp_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 3: FS20 set Sleep_DVBT on
2017.10.05 11:39:10 3: FS20 set Sleep_tablet on
2017.10.05 11:39:10 2: PRESENCE (CAM_09_Raspberry) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (FritzBox) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (Homepage) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Powerline_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Powerline_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Laptop_LAN) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 3: FS20 set Steckdose_Laptop off
2017.10.05 11:39:11 2: PRESENCE (Lap_LAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Laptop_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Repeater_300E) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Tablet_XORO) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Tab_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Raspberry_Pi) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Tablet_WLAN) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:11 2: PRESENCE (Tablet_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:13 2: PRESENCE (CAM_04_Wohnen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:13 2: PRESENCE (CAM_05_Schlafen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:13 2: PRESENCE (CAM_04_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:13 2: PRESENCE (CAM_05_Schlafen) - check returned a valid result after 1 unsuccesful retry
Danach natürlich blocking.pm ..... "back to roots"! 

[CoolTux]

Hab gerade mal blocking.pm und 73_PRESENCE.pm geupdatet, wie Markus sagte, wollte er sehen wie jetzt die Meldungen aussehen,...
bitte sehr:

Code Auswählen Erweitern

2017.10.05 11:38:53 0: Server shutdown
2017.10.05 11:38:55 1: BlockingInformParent (BlockingStart): Can't connect to localhost:42051: IO::Socket::INET: connect: Connection refused
2017.10.05 11:38:55 1: BlockingInformParent (PRESENCE_ProcessLocalScan): Can't connect to localhost:42051: IO::Socket::INET: connect: Connection refused
2017.10.05 11:38:56 1: Including fhem.cfg
2017.10.05 11:38:56 3: telnetPort: port 7072 opened
2017.10.05 11:38:56 3: WEB: port 8083 opened
2017.10.05 11:38:56 3: WEBphone: port 8084 opened
2017.10.05 11:38:56 3: WEBtablet: port 8085 opened
2017.10.05 11:38:57 2: eventTypes: loaded 1878 events from ./log/eventTypes.txt
2017.10.05 11:38:57 3: Opening CUL_0 device /dev/ttyACM0
2017.10.05 11:38:57 3: Setting CUL_0 serial parameters to 9600,8,N,1
2017.10.05 11:38:57 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2017.10.05 11:38:57 3: CUL_0 device opened
2017.10.05 11:39:05 1: Including ./log/fhem.save
2017.10.05 11:39:06 0: Featurelevel: 5.8
2017.10.05 11:39:06 0: Server started with 345 defined entities (fhem.pl:15182/2017-10-03 perl:5.014002 os:linux user:fhem pid:5548)
2017.10.05 11:39:07 3: telnetForBlockingFn_1507196347: port 38887 opened
2017.10.05 11:39:10 2: PRESENCE (CAM_08_Wohnen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (CAM_08_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (CAM_09_Raspberry) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Comp_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Computer) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (FritzBox) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Homepage) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Powerline_Keller) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Powerline_Wohnen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Repeater_300E) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Tab_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Lap_LAN_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Lap_WLAN_2) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Laptop_LAN) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Laptop_WLAN) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Raspberry_Pi) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Tablet_XORO) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:10 2: PRESENCE (Comp_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 3: FS20 set Sleep_DVBT on
2017.10.05 11:39:10 3: FS20 set Sleep_tablet on
2017.10.05 11:39:10 2: PRESENCE (CAM_09_Raspberry) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (FritzBox) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (Computer) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:10 2: PRESENCE (Homepage) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Powerline_Keller) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Powerline_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Laptop_LAN) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Lap_WLAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 3: FS20 set Steckdose_Laptop off
2017.10.05 11:39:11 2: PRESENCE (Lap_LAN_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Laptop_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Repeater_300E) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Tablet_XORO) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Tab_2) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Raspberry_Pi) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:11 2: PRESENCE (Tablet_WLAN) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:11 2: PRESENCE (Tablet_WLAN) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:13 2: PRESENCE (CAM_04_Wohnen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:13 2: PRESENCE (CAM_05_Schlafen) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 11:39:13 2: PRESENCE (CAM_04_Wohnen) - check returned a valid result after 1 unsuccesful retry
2017.10.05 11:39:13 2: PRESENCE (CAM_05_Schlafen) - check returned a valid result after 1 unsuccesful retry
Danach natürlich blocking.pm ..... "back to roots"! 

Du musst das neue Blocking.pm aus dem SVN nehmen oder bis morgen früh warten.

[Tom111]

Du musst das neue Blocking.pm aus dem SVN nehmen oder bis morgen früh warten.

Oh, dann warte ich bis morgen. 

[CoolTux]

Schade: Es werden Tester gesucht um das Problem schneller abschließend lösen zu können.

[Tom111]

Schade: Es werden Tester gesucht um das Problem schneller abschließend lösen zu können.

Auf dieser Seite wird mir angezeigt, dass "blocking.pm" 3 Tage alt sei  :
https://github.com/mhop/fhem-mirror/tree/master/fhem/FHEM