!!! Probleme mit Presence, FRITZBOX und Meldungen von Blocking.pm !!!

Begonnen von CoolTux, 05 Oktober 2017, 09:18:53

Vorheriges Thema - Nächstes Thema

CoolTux

Guten Morgen FHEM User,

Mit dem letzten Update hat sich ein Problem eingeschlichen welches sich zum jetzigen Zeitpunkt im Presence, FRITZBOX und EQ3BT Modul zeigt. Die Vermutung lässt darauf schließen das die Ursache eine Änderung im Modul Blocking.pm ist.

Da es mittlerweile nicht nur Module von Markus Bloch betrifft, eröffne ich diesen Thread um die Informationen über alle betroffenen Module zu zu bündeln.
Bitte seit so nett und postet Eure Logausgaben hier.


Reine Entwickler Diskussionen zum Problem werden hier diskutiert werden



Grüße
Leon
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Otto123

Moin,

das WOL Modul ist auch betroffen, diese Einträge habe ich jetzt zu Hauf:
2017.10.05 01:35:49 2: PRESENCE (Pres_HMUART) - device could not be checked (retrying in 10 seconds)
2017.10.05 01:35:49 2: PRESENCE (Pres_HMUART) - check returned a valid result after 1 unsuccesful retry
2017.10.05 03:55:40 3: BlockingCall for LG_WOL was aborted
2017.10.05 04:46:47 3: BlockingCall for LG_WOL was aborted


Gruß Otto
Viele Grüße aus Leipzig  ⇉  nächster Stammtisch an der Lindennaundorfer Mühle
RaspberryPi B B+ B2 B3 B3+ ZeroW,HMLAN,HMUART,Homematic,Fritz!Box 7590,WRT3200ACS-OpenWrt,Sonos,VU+,Arduino nano,ESP8266,MQTT,Zigbee,deconz

CoolTux

Rudi hat gerade eine Blocking.pm Version ins SVN geladen, kannst Du die mal bitte testen? Ich bekomme leider das Problem auch nicht nachvollzogen.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

darkness

Hallo,

ich habe gerade in SYSMON Error: Blocking call aborted (timeout) stehen.

Ist das das gleiche Problem?

CoolTux

Eher nicht. Das ist eigentlich die ganz normale Meldung wenn Blocking.pm die $finishFn nihct in der angegeben Zeit auf ruft.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

darkness


Kawaci

Hier mein logging für das Problem mit Eq3bt!

_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:09 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:10 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:15 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:15 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:17 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:17 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:23 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:23 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:26 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:26 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:32 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:32 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:39 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:39 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:39 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:39 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (BlockingStart): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (EQ3BT_processGatttoolResult): Can't connect to localhost:37871: IO::Socket::INET: connect: Connection refused
2017.10.05 14:05:40 1: BlockingInformParent (Bl

CoolTux

Bitte einmal Morgen ein Update machen. Es gibt eine angepasste Version von Blocking.pm
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

Otto123

Ich habe die neue Blocking am laufen. Schnelle Ergebnisse kann ich nicht liefern, die Meldungen kamen sehr sporadisch  :-[
Bis jetzt läuft es...
Viele Grüße aus Leipzig  ⇉  nächster Stammtisch an der Lindennaundorfer Mühle
RaspberryPi B B+ B2 B3 B3+ ZeroW,HMLAN,HMUART,Homematic,Fritz!Box 7590,WRT3200ACS-OpenWrt,Sonos,VU+,Arduino nano,ESP8266,MQTT,Zigbee,deconz

CoolTux

Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

viegener

Die presence-Fehlermeldungen beim Start sind bei mir zumindest weg (mit der neuen Blocking aus svn) - die kamen bei jedem Neustart seit dem Update
Kein Support über PM - Anfragen gerne im Forum - Damit auch andere profitieren und helfen können

sku

Ich habe seit dem Update heute folgende Einträge auf meine FHEM VM:
2017.10.05 15:19:34 2: PRESENCE (steffi_p10lite) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:19:34 2: PRESENCE (steffi_p10lite) - check returned a valid result after 1 unsuccesful retry
2017.10.05 15:19:49 2: PRESENCE (stffi_SGS3) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:19:49 2: PRESENCE (stffi_SGS3) - check returned a valid result after 1 unsuccesful retry
2017.10.05 15:20:19 2: PRESENCE (steffi_p10lite) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:20:19 2: PRESENCE (stffi_SGS3) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:20:19 2: PRESENCE (steffi_p10lite) - check returned a valid result after 1 unsuccesful retry
2017.10.05 15:20:19 2: PRESENCE (stffi_SGS3) - check returned a valid result after 1 unsuccesful retry
2017.10.05 15:20:34 2: PRESENCE (presence_P900) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:20:34 2: PRESENCE (presence_P900) - check returned a valid result after 1 unsuccesful retry
2017.10.05 15:20:50 2: PRESENCE (steffi_p10lite) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:20:50 2: PRESENCE (stffi_SGS3) - device could not be checked (retrying in 10 seconds): Process died prematurely
2017.10.05 15:20:50 2: PRESENCE (stffi_SGS3) - check returned a valid result after 1 unsuccesful retry
2017.10.05 15:20:50 2: PRESENCE (steffi_p10lite) - check returned a valid result after 1 unsuccesful retry


Interessant daran ist, dass ein PRESENCE device kein Logeinträge generiert. Konfiguriert sind alle gleich, standard verbose level. Neustart von FHEM und der kompletten VM hat nix geändert.
Edit: Das fehlende device ist doch noch aufgetaucht.

FHEM am raspi3 hat auch solge Einträge, jedoch seltener.

viegener

Wie hier zu lesen - Es gibt ein neues Blocking.pm, das morgen wohl auch per update verfügbar ist - Also morgen update durchführen

Interessant wäre ob die Fehler morgen noch auftreten
Kein Support über PM - Anfragen gerne im Forum - Damit auch andere profitieren und helfen können

sku

Hallo
bei mir ist der Fehler gelöst. Update vor ca. 2h durchgeführt, keine Fehler mehr im Log.

Gruß

viegener

In den letzen 24 h auch bei mir kein weiteres Auftreten, vorsichtig optimistisch...
Kein Support über PM - Anfragen gerne im Forum - Damit auch andere profitieren und helfen können