<![CDATA[(Error) ioBroker kurze Zeit nicht erreichbar]]>Hallo đź‘Ť

dachte schon der Raspi4 wäre abgestürzt und wollte schon den Stecker ziehen, da ist ioBroker wieder gekommen. Per Telegram erhalte ich eine Info sollte ioBroker restarten bzw. gestartet werden, das kam nicht, dh nur ioBroker hatte ein Problem.
hier das Log:

2021-03-01 11:23:02.517 - warn: modbus.0 (809) Poll error count: 1 code: "App Timeout"
2021-03-01 11:23:03.004 - warn: modbus.0 (809) Error: undefined
2021-03-01 11:23:03.005 - error: modbus.0 (809) Request timed out.
2021-03-01 11:23:03.005 - error: modbus.0 (809) Client in error state.
2021-03-01 11:23:04.006 - info: modbus.0 (809) Disconnected from slave 192.168.0.9
2021-03-01 11:23:06.255 - warn: modbus.1 (828) Error: undefined
2021-03-01 11:23:06.256 - error: modbus.1 (828) Request timed out.
2021-03-01 11:23:06.256 - error: modbus.1 (828) Client in error state.
2021-03-01 11:23:06.258 - warn: modbus.1 (828) Poll error count: 1 code: {"err":"timeout","timeout":5000}
2021-03-01 11:23:07.256 - info: modbus.1 (828) Disconnected from slave 192.168.0.98
2021-03-01 11:23:12.748 - error: shelly.0 (776) Error in function state.coap.http_cmd for state SHPLG-S#EED8F9#1.Relay0.Switch and request{"url":"http://192.168.0.80/relay/0","timeout":5000,"qs":{"turn":"off","timer":0}} for 192.168.0.80 (shellyplug-s / shellyplug-s-EED8F9 / SHPLG-S#EED8F9#1) (Error: ETIMEDOUT)
2021-03-01 11:23:21.020 - info: mqtt.0 (607) Client [AMIS] connection closed: timeout
2021-03-01 11:23:21.111 - error: cloud.0 (669) Ping timeout
2021-03-01 11:23:21.112 - info: cloud.0 (669) Connection changed: Ping timeout
2021-03-01 11:23:21.112 - info: cloud.0 (669) Connection lost
2021-03-01 11:23:21.113 - info: cloud.0 (669) Restart adapter by disconnect
2021-03-01 11:23:31.116 - warn: cloud.0 (669) Terminated (-100): Without reason
2021-03-01 11:23:31.647 - info: cloud.0 (669) Connection changed: io client disconnect
2021-03-01 11:23:31.807 - info: host.raspi4iobrokerpv instance system.adapter.cloud.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2021-03-01 11:23:31.808 - info: host.raspi4iobrokerpv Restart adapter system.adapter.cloud.0 because enabled
2021-03-01 11:23:32.872 - info: host.raspi4iobrokerpv instance system.adapter.cloud.0 started with pid 7580
2021-03-01 11:23:34.623 - info: cloud.0 (7580) starting. Version 4.0.4 in /opt/iobroker/node_modules/iobroker.cloud, node: v12.21.0, js-controller: 3.2.16
2021-03-01 11:23:34.697 - info: cloud.0 (7580) Connecting with https://iobroker.net:10555 with "richard.nussdorfer@gmail.com_65a2cba0-c435-11ea-b03c-2dda666d26a"
2021-03-01 11:23:34.851 - info: cloud.0 (7580) Trying to connect as system.user.admin
2021-03-01 11:23:40.353 - error: modbus.1 (828) Socket Error
2021-03-01 11:23:40.354 - error: modbus.1 (828) Client in error state.
2021-03-01 11:23:40.355 - warn: modbus.1 (828) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:23:44.846 - error: cloud.0 (7580) Error while connecting to cloud: Error: websocket error
2021-03-01 11:24:07.153 - error: modbus.0 (809) Socket Error
2021-03-01 11:24:07.154 - error: modbus.0 (809) Client in error state.
2021-03-01 11:24:07.155 - warn: modbus.0 (809) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.9","port":502}
2021-03-01 11:24:14.511 - error: modbus.1 (828) Socket Error
2021-03-01 11:24:14.512 - error: modbus.1 (828) Client in error state.
2021-03-01 11:24:14.512 - warn: modbus.1 (828) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:24:34.718 - info: cloud.0 (7580) Trying to connect as system.user.admin
2021-03-01 11:24:44.714 - error: cloud.0 (7580) Error while connecting to cloud: Error: websocket error
2021-03-01 11:24:44.997 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:24:45.000 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:24:45.001 - info: iot.0 (684) Connection lost
2021-03-01 11:24:48.671 - error: modbus.1 (828) Socket Error
2021-03-01 11:24:48.672 - error: modbus.1 (828) Client in error state.
2021-03-01 11:24:48.673 - warn: modbus.1 (828) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:25:10.024 - error: iot.0 (684) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2021-03-01 11:25:10.025 - error: iot.0 (684) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2021-03-01 11:25:10.028 - error: iot.0 (684) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2021-03-01 11:25:10.029 - error: iot.0 (684) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2021-03-01 11:25:10.030 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:25:11.311 - error: modbus.0 (809) Socket Error
2021-03-01 11:25:11.313 - error: modbus.0 (809) Client in error state.
2021-03-01 11:25:11.313 - warn: modbus.0 (809) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.9","port":502}
2021-03-01 11:25:20.049 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:25:20.051 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:25:20.080 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:25:20.081 - warn: iot.0 (684) Looks like your connection certificates are invalid. Please renew them via configuration dialog.
2021-03-01 11:25:20.082 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:25:22.831 - error: modbus.1 (828) Socket Error
2021-03-01 11:25:22.832 - error: modbus.1 (828) Client in error state.
2021-03-01 11:25:22.832 - warn: modbus.1 (828) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:25:34.714 - info: cloud.0 (7580) Trying to connect as system.user.admin
2021-03-01 11:25:44.713 - error: cloud.0 (7580) Error while connecting to cloud: Error: websocket error
2021-03-01 11:25:50.094 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:25:50.095 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:25:56.991 - error: modbus.1 (828) Socket Error
2021-03-01 11:25:56.992 - error: modbus.1 (828) Client in error state.
2021-03-01 11:25:56.992 - warn: modbus.1 (828) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:26:15.117 - error: iot.0 (684) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2021-03-01 11:26:15.118 - error: iot.0 (684) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2021-03-01 11:26:15.119 - error: iot.0 (684) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2021-03-01 11:26:15.120 - error: iot.0 (684) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2021-03-01 11:26:15.121 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:26:15.471 - error: modbus.0 (809) Socket Error
2021-03-01 11:26:15.471 - error: modbus.0 (809) Client in error state.
2021-03-01 11:26:15.472 - warn: modbus.0 (809) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.9","port":502}
2021-03-01 11:26:25.132 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:26:25.133 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:26:25.202 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:26:25.203 - warn: iot.0 (684) Looks like your connection certificates are invalid. Please renew them via configuration dialog.
2021-03-01 11:26:25.204 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:26:31.152 - error: modbus.1 (828) Socket Error
2021-03-01 11:26:31.153 - error: modbus.1 (828) Client in error state.
2021-03-01 11:26:31.154 - warn: modbus.1 (828) On error: {"errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:26:34.719 - info: cloud.0 (7580) Trying to connect as system.user.admin
2021-03-01 11:26:44.711 - error: cloud.0 (7580) Error while connecting to cloud: Error: websocket error
2021-03-01 11:26:55.214 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:26:55.215 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:26:57.733 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:58.034 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:58.334 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:58.635 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:58.936 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:59.237 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:59.537 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:26:59.837 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:00.137 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:00.220 - error: iot.0 (684) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2021-03-01 11:27:00.221 - error: iot.0 (684) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2021-03-01 11:27:00.222 - error: iot.0 (684) Error by device connection: "getaddrinfo EAI_AGAIN a18wym7vjdl22g.iot.eu-west-1.amazonaws.com"
2021-03-01 11:27:00.223 - error: iot.0 (684) DNS name of a18wym7vjdl22g.iot.eu-west-1.amazonaws.com cannot be resolved: connection will be retried in 10 seconds.
2021-03-01 11:27:00.224 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:27:00.437 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:00.738 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:01.038 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:01.338 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:01.638 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:01.938 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:02.156 - error: modbus.1 (828) Socket Error
2021-03-01 11:27:02.157 - error: modbus.1 (828) Client in error state.
2021-03-01 11:27:02.157 - warn: modbus.1 (828) On error: {"errno":"ENETUNREACH","code":"ENETUNREACH","syscall":"connect","address":"192.168.0.98","port":502}
2021-03-01 11:27:02.239 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:02.539 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:02.839 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:03.140 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:03.439 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:03.740 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:04.041 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:04.341 - warn: kecontact.0 (592) UDP send error for 192.168.0.97:7090: Error: send ENETUNREACH 192.168.0.97:7090
2021-03-01 11:27:08.655 - info: mqtt.0 (607) Client [H,] connected with secret 1614594428653_9692
2021-03-01 11:27:10.233 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:27:10.233 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:27:10.254 - error: iot.0 (684) Error by device connection: "premature close"
2021-03-01 11:27:10.256 - warn: iot.0 (684) Looks like your connection certificates are invalid. Please renew them via configuration dialog.
2021-03-01 11:27:10.257 - info: iot.0 (684) Connection changed: disconnect
2021-03-01 11:27:10.698 - info: iot.0 (684) Connection changed: connect
2021-03-01 11:27:16.496 - info: modbus.0 (809) Connected to slave 192.168.0.9
2021-03-01 11:27:33.164 - info: modbus.1 (828) Connected to slave 192.168.0.98
2021-03-01 11:27:34.710 - info: cloud.0 (7580) Trying to connect as system.user.admin
2021-03-01 11:27:35.080 - info: cloud.0 (7580) Adapter redirected temporally to "https://iobroker.net:10556" in one minute. Reason: command from server
2021-03-01 11:27:35.082 - info: cloud.0 (7580) Connection changed: io client disconnect
2021-03-01 11:28:35.089 - info: cloud.0 (7580) Trying to connect as system.user.admin
2021-03-01 11:28:35.419 - info: cloud.0 (7580) Connection changed: connect

danach läuft alles wie gehabt.

Datenträger verfügbar: 76.7 %, gesamte RAM-Nutzung: 1142 MB / Frei: 63% = 1.177 MB [Host: raspi4iobrokerpv - 16 Prozesse]

kann man das besser beobachten bzw. protokollieren, was bei einem verschlucker passiert? bzw. rausfinden wo der Hund begragen ist?

raspi4iobrokerpv
Platform
linux
Betriebssystem
linux
Architektur
arm
CPUs
4
Geschwindigkeit
800 MHz
Modell
ARMv7 Processor rev 3 (v7l)
RAM
1.82 GB
System Betriebszeit
03:01:06
Node.js
v12.21.0
NPM
6.14.11
Festplatte Größe
14.05 GB
Festplatte frei
10.78 GB
Anzahl der Adapter
332
Betriebszeit
03:24:49
Aktive Instanzen
15
Hostname
raspi4iobrokerpv

]]>https://forum.iobroker.net/topic/42793/error-iobroker-kurze-zeit-nicht-erreichbarRSS for NodeThu, 21 May 2026 02:23:39 GMTMon, 01 Mar 2021 10:33:34 GMT60<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 10:44:16 GMT]]>@humidor

Zum "Speicherfehler" gibt es einen eigenen Thread. Das ist wenn du ein Blockly speichern willst, das aber nicht funktioniert und alle Änderungen rückgängig gemacht werden.

]]>https://forum.iobroker.net/post/592053https://forum.iobroker.net/post/592053Thu, 04 Mar 2021 10:44:16 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 10:43:11 GMT]]>@saeft_2003 bitte eigenen Thread aufmachen - das verwirrt hier.
Ich lösche gleich die "sachfremden" Posts

]]>https://forum.iobroker.net/post/592052https://forum.iobroker.net/post/592052Thu, 04 Mar 2021 10:43:11 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 10:41:42 GMT]]>@arteck

Ich nutze doch ĂĽberhaupt kein WLAN... jetzt bin ich verwirrt. Du hast gesagt es liegt bei mir am Netwerkkartentreiber.

]]>https://forum.iobroker.net/post/592051https://forum.iobroker.net/post/592051Thu, 04 Mar 2021 10:41:42 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 10:13:36 GMT]]>@humidor sagte in (Error) ioBroker kurze Zeit nicht erreichbar:

und wollte schon den Stecker ziehen

Steckerziehverbot!
Abwarten hilft meist. Kann auch geraume Zeit dauern. Ist aber immer noch besser als die Kiste hart vom Strom zu nehmen.

]]>https://forum.iobroker.net/post/592035https://forum.iobroker.net/post/592035Thu, 04 Mar 2021 10:13:36 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 09:53:26 GMT]]>@saeft_2003 na ja WLAN ist nicht zu 100% stabiel was dein System aber erwartet.. ist die unterbrechung auch nur ganz kurz kommt das system durcheinandner

]]>https://forum.iobroker.net/post/592017https://forum.iobroker.net/post/592017Thu, 04 Mar 2021 09:53:26 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 09:46:59 GMT]]>@saeft_2003 was ist der Speicherfehler? hatte bis vor kurzem noch Fehler beim öffnen eines Blockly und manchmal ging auch gar nichts im Script zu verändern. Das hat sich aber von selbst behoben??

]]>https://forum.iobroker.net/post/592010https://forum.iobroker.net/post/592010Thu, 04 Mar 2021 09:46:59 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 09:46:34 GMT]]>@arteck

OK krass… Ist das ein bekanntes Problem, weil du das aus der Ferne so sicher sagen kannst? Kannst du auch sagen ob das mit dem Speicherfehler in blockly was zu tun hat? Da würde ich einiges dafür geben um diesen los zu werden...

]]>https://forum.iobroker.net/post/592009https://forum.iobroker.net/post/592009Thu, 04 Mar 2021 09:46:34 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 08:34:18 GMT]]>@saeft_2003 du hast ein anderes problem.. der mit dem NUC Netzwerkkartetreiber liegt...

@Humidor dann hast du das Problem schon selbst erkannt.. WLAN..

]]>https://forum.iobroker.net/post/591967https://forum.iobroker.net/post/591967Thu, 04 Mar 2021 08:34:18 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 08:21:36 GMT]]>das "Problem" kenne. Kommt bei mir aber nur sehr selten vor. Ich nutze einen NUC der am LAN hängt, deshalb vermute ich das es nicht an der Hardware liegt.

@Humidor Hast du zufällig auch den blockly Speicherfehler?

]]>https://forum.iobroker.net/post/591961https://forum.iobroker.net/post/591961Thu, 04 Mar 2021 08:21:36 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Thu, 04 Mar 2021 08:02:26 GMT]]>@arteck WLan

]]>https://forum.iobroker.net/post/591947https://forum.iobroker.net/post/591947Thu, 04 Mar 2021 08:02:26 GMT<![CDATA[Reply to (Error) ioBroker kurze Zeit nicht erreichbar on Mon, 01 Mar 2021 11:25:21 GMT]]>@humidor hängt der pi am lan oder wlan?

]]>https://forum.iobroker.net/post/590184https://forum.iobroker.net/post/590184Mon, 01 Mar 2021 11:25:21 GMT