NEWS
ioBroker / Vis / Pi sind immer wieder nicht erreichbar
-
Hallo,
habe seit einiger Zeit Probleme mit meinem ioBroker-System auf einem Pi3.
Regelmäßig fällt es aus. Ich konnte bis jetzt nicht den Fehler identifizieren.
Das Tablet kann keine Verbindung aufbauen, und mit dem Terminal komme ich nicht auf den Pi.
Irgendwann ist es dann wieder gut und alles funktioniert wieder.
Ich hänge hier mal die Logdatei dran, vieleicht könnt ihr den Fehler dort lokalisieren.Logdatei ioBroker:
2019-04-19 16:57:09.769 - [33mwarn[39m: sonoff.0 Reconnection to DB.
2019-04-19 16:57:09.772 - [33mwarn[39m: sonoff.0 Reconnection to DB.
2019-04-19 16:57:09.895 - [33mwarn[39m: lgtv.0 Reconnection to DB.
2019-04-19 16:57:09.897 - [33mwarn[39m: lgtv.0 Reconnection to DB.
2019-04-19 16:57:09.978 - [33mwarn[39m: socketio.0 Reconnection to DB.
2019-04-19 16:57:09.981 - [33mwarn[39m: socketio.0 Reconnection to DB.
2019-04-19 16:57:10.593 - [33mwarn[39m: backitup.0 Reconnection to DB.
2019-04-19 16:57:10.598 - [33mwarn[39m: backitup.0 Reconnection to DB.
2019-04-19 16:57:10.654 - [33mwarn[39m: rpi2.0 Reconnection to DB.
2019-04-19 16:57:10.659 - [33mwarn[39m: rpi2.0 Reconnection to DB.
2019-04-19 16:57:11.702 - [34mdebug[39m: statistics.0 redis pmessage io.lgtv.0.states.on io.lgtv.0.states.on {"val":false,"ack":true,"ts":1555685831701,"q":0,"from":"system.adapter.lgtv.0","lc":1555617750672}
2019-04-19 16:57:11.702 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= lgtv.0.states.on =======================
2019-04-19 16:57:11.703 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => false [true]
2019-04-19 16:57:11.703 - [34mdebug[39m: statistics.0 [STATE CHANGE] count call lgtv.0.states.on with false
2019-04-19 16:57:11.703 - [34mdebug[39m: statistics.0 new pulse false ? false
2019-04-19 16:57:11.704 - [34mdebug[39m: statistics.0 [STATE CHANGE] timecount call lgtv.0.states.on with false
2019-04-19 16:57:11.706 - [34mdebug[39m: statistics.0 [STATE CHANGE] 1->0 delta 10703171 state 1555617750672 last 1555607047501
2019-04-19 16:57:11.715 - [34mdebug[39m: statistics.0 redis pmessage io.lgtv.0.states.on io.lgtv.0.states.on {"val":false,"ack":true,"ts":1555685831710,"q":0,"from":"system.adapter.lgtv.0","lc":1555617750672}
2019-04-19 16:57:11.715 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= lgtv.0.states.on =======================
2019-04-19 16:57:11.716 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => false [true]
2019-04-19 16:57:11.716 - [34mdebug[39m: statistics.0 [STATE CHANGE] count call lgtv.0.states.on with false
2019-04-19 16:57:11.716 - [34mdebug[39m: statistics.0 new pulse false ? false
2019-04-19 16:57:11.716 - [34mdebug[39m: statistics.0 [STATE CHANGE] timecount call lgtv.0.states.on with false
2019-04-19 16:57:11.723 - [34mdebug[39m: statistics.0 [STATE CHANGE] 1->0 delta 10703171 state 1555617750672 last 1555607047501
2019-04-19 16:57:12.531 - [32minfo[39m: sonoff.0 Client [Schalter_WZ] connected with secret 1555685832530_7368
2019-04-19 16:57:12.587 - [32minfo[39m: sonoff.0 Client [Temp_Gefrierschrank] connected with secret 1555685832585_5997
2019-04-19 16:57:16.194 - [32minfo[39m: web.0 ==>Connected system.user.admin from ::ffff:192.168.10.86
2019-04-19 16:57:28.171 - [32minfo[39m: modbus.0 Connected to slave 192.168.10.99
2019-04-19 16:57:38.151 - [32minfo[39m: denon.0 [CONNECT] Adapter connected to DENON-AVR: 192.168.10.14:23
2019-04-19 16:57:38.602 - [32minfo[39m: host.ioBroker-RasPi instance system.adapter.javascript.0 started with pid 9341
2019-04-19 16:57:38.757 - [34mdebug[39m: statistics.0 redis pmessage io.denon.0.zoneMain.powerZone io.denon.0.zoneMain.powerZone {"val":false,"ack":true,"ts":1555685858756,"q":0,"from":"system.adapter.denon.0","lc":1555617653545}
2019-04-19 16:57:38.758 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= denon.0.zoneMain.powerZone =======================
2019-04-19 16:57:38.758 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => false [true]
2019-04-19 16:57:38.758 - [34mdebug[39m: statistics.0 [STATE CHANGE] count call denon.0.zoneMain.powerZone with false
2019-04-19 16:57:38.758 - [34mdebug[39m: statistics.0 new pulse false ? false
2019-04-19 16:57:38.758 - [34mdebug[39m: statistics.0 [STATE CHANGE] timecount call denon.0.zoneMain.powerZone with false
2019-04-19 16:57:38.761 - [34mdebug[39m: statistics.0 [STATE CHANGE] 1->0 delta 17936947 state 1555617653545 last 1555599716598
2019-04-19 16:57:39.245 - [32minfo[39m: host.ioBroker-RasPi instance system.adapter.ping.0 started with pid 9347
2019-04-19 16:57:41.154 - [32minfo[39m: ping.0 States connected to redis: 127.0.0.1:6379
2019-04-19 16:57:41.318 - [32minfo[39m: ping.0 starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.ping, node: v8.15.0
2019-04-19 16:57:43.784 - [32minfo[39m: javascript.0 States connected to redis: 127.0.0.1:6379
2019-04-19 16:57:43.858 - [32minfo[39m: javascript.0 starting. Version 4.1.12 in /opt/iobroker/node_modules/iobroker.javascript, node: v8.15.0
2019-04-19 16:57:43.882 - [32minfo[39m: javascript.0 requesting all states
2019-04-19 16:57:43.886 - [32minfo[39m: javascript.0 requesting all objects
2019-04-19 16:57:46.741 - [32minfo[39m: javascript.0 received all states
2019-04-19 16:58:25.978 - [33mwarn[39m: modbus.0 Poll error count: 1 code: "App Timeout"
2019-04-19 16:58:26.005 - [32minfo[39m: sonoff.0 Client [Temp_Gefrierschrank] reconnected. Old secret 1555685832585_5997. New secret 1555685905971_6052
2019-04-19 16:58:26.005 - [33mwarn[39m: modbus.0 Error: undefined
2019-04-19 16:58:26.006 - [31merror[39m: modbus.0 Request timed out.
2019-04-19 16:58:26.007 - [31merror[39m: modbus.0 Client in error state.
2019-04-19 16:58:26.236 - [32minfo[39m: sonoff.0 Client [Schalter_WZ] reconnected. Old secret 1555685832530_7368. New secret 1555685906002_9696
2019-04-19 16:58:26.251 - [32minfo[39m: sonoff.0 Client [Temp_Gefrierschrank] connection closed: closed
2019-04-19 16:58:26.367 - [31merror[39m: ping.0 uncaught exception: spawn ENOMEM
2019-04-19 16:58:26.368 - [31merror[39m: ping.0 Error: spawn ENOMEM
at ChildProcess.spawn (internal/child_process.js:313:11)
at Object.exports.spawn (child_process.js:508:9)
at Object.probe (/opt/iobroker/node_modules/iobroker.ping/lib/ping.js:35:17)
at pingAll (/opt/iobroker/node_modules/iobroker.ping/main.js:98:10)
at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.ping/main.js:107:17)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
2019-04-19 16:58:26.659 - [33mwarn[39m: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated due to SIGKILL
2019-04-19 16:58:26.661 - [31merror[39m: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code null ()
2019-04-19 16:58:26.663 - [32minfo[39m: host.ioBroker-RasPi Restart adapter system.adapter.javascript.0 because enabled
2019-04-19 16:58:26.678 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610099542.power io.fritzdect.0.DECT200_087610099542.power {"val":24.53,"ack":true,"ts":1555685906677,"q":0,"from":"system.adapter.fritzdect.0","lc":1555685829023}
2019-04-19 16:58:26.679 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610099542.power =======================
2019-04-19 16:58:26.683 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 24.53 [true]
2019-04-19 16:58:26.684 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610099542.power value 24.53
2019-04-19 16:58:26.691 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610450557.power io.fritzdect.0.DECT200_087610450557.power {"val":98.91,"ack":true,"ts":1555685906685,"q":0,"from":"system.adapter.fritzdect.0","lc":1555685906685}
2019-04-19 16:58:26.692 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610450557.power =======================
2019-04-19 16:58:26.692 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 98.91 [true]
2019-04-19 16:58:26.694 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610450557.power value 98.91
2019-04-19 16:58:26.697 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610490139.power io.fritzdect.0.DECT200_087610490139.power {"val":0.28,"ack":true,"ts":1555685906692,"q":0,"from":"system.adapter.fritzdect.0","lc":1555682653521}
2019-04-19 16:58:26.697 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610490139.power =======================
2019-04-19 16:58:26.698 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 0.28 [true]
2019-04-19 16:58:26.698 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610490139.power value 0.28
2019-04-19 16:58:26.706 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610473548.power io.fritzdect.0.DECT200_087610473548.power {"val":0,"ack":true,"ts":1555685906697,"q":0,"from":"system.adapter.fritzdect.0","lc":1555346195409}
2019-04-19 16:58:26.706 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610473548.power =======================
2019-04-19 16:58:26.706 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 0 [true]
2019-04-19 16:58:26.712 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610473548.power value 0
2019-04-19 16:58:26.715 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610029095.power io.fritzdect.0.DECT200_087610029095.power {"val":108.21,"ack":true,"ts":1555685906710,"q":0,"from":"system.adapter.fritzdect.0","lc":1555685906710}
2019-04-19 16:58:26.715 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610029095.power =======================
2019-04-19 16:58:26.715 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 108.21 [true]
2019-04-19 16:58:26.715 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610029095.power value 108.21
2019-04-19 16:58:26.718 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610490149.power io.fritzdect.0.DECT200_087610490149.power {"val":0,"ack":true,"ts":1555685906715,"q":0,"from":"system.adapter.fritzdect.0","lc":1555541923767}
2019-04-19 16:58:26.718 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610490149.power =======================
2019-04-19 16:58:26.718 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 0 [true]
2019-04-19 16:58:26.719 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610490149.power value 0
2019-04-19 16:58:26.721 - [34mdebug[39m: statistics.0 redis pmessage io.fritzdect.0.DECT200_087610482090.power io.fritzdect.0.DECT200_087610482090.power {"val":0,"ack":true,"ts":1555685906718,"q":0,"from":"system.adapter.fritzdect.0","lc":1555175962730}
2019-04-19 16:58:26.721 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= fritzdect.0.DECT200_087610482090.power =======================
2019-04-19 16:58:26.722 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => 0 [true]
2019-04-19 16:58:26.722 - [34mdebug[39m: statistics.0 [STATE CHANGE] avg call: fritzdect.0.DECT200_087610482090.power value 0
2019-04-19 16:58:26.816 - [33mwarn[39m: fritzbox.0 Reconnection to DB.
2019-04-19 16:58:26.821 - [33mwarn[39m: fritzdect.0 Reconnection to DB.
2019-04-19 16:58:26.823 - [33mwarn[39m: fritzbox.0 Reconnection to DB.
2019-04-19 16:58:26.824 - [33mwarn[39m: fritzdect.0 Reconnection to DB.
2019-04-19 16:58:26.876 - [33mwarn[39m: backitup.0 Reconnection to DB.
2019-04-19 16:58:26.878 - [32minfo[39m: ping.0 terminating
2019-04-19 16:58:26.881 - [33mwarn[39m: backitup.0 Reconnection to DB.
2019-04-19 16:58:26.949 - [31merror[39m: Caught by controller[0]: { Error: spawn ENOMEM
2019-04-19 16:58:26.950 - [31merror[39m: Caught by controller[0]: at ChildProcess.spawn (internal/child_process.js:313:11)
2019-04-19 16:58:26.950 - [31merror[39m: Caught by controller[0]: at Object.exports.spawn (child_process.js:508:9)
2019-04-19 16:58:26.950 - [31merror[39m: Caught by controller[0]: at Object.probe (/opt/iobroker/node_modules/iobroker.ping/lib/ping.js:35:17)
2019-04-19 16:58:26.950 - [31merror[39m: Caught by controller[0]: at pingAll (/opt/iobroker/node_modules/iobroker.ping/main.js:98:10)
2019-04-19 16:58:26.951 - [31merror[39m: Caught by controller[0]: at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.ping/main.js:107:17)
2019-04-19 16:58:26.951 - [31merror[39m: Caught by controller[0]: at ontimeout (timers.js:498:11)
2019-04-19 16:58:26.951 - [31merror[39m: Caught by controller[0]: at tryOnTimeout (timers.js:323:5)
2019-04-19 16:58:26.951 - [31merror[39m: Caught by controller[0]: at Timer.listOnTimeout (timers.js:290:5) errno: 'ENOMEM', code: 'ENOMEM', syscall: 'spawn' }
2019-04-19 16:58:26.951 - [31merror[39m: host.ioBroker-RasPi instance system.adapter.ping.0 terminated with code 0 (OK)
2019-04-19 16:58:26.951 - [32minfo[39m: host.ioBroker-RasPi Restart adapter system.adapter.ping.0 because enabled
2019-04-19 16:58:27.007 - [32minfo[39m: modbus.0 Disconnected from slave 192.168.10.99
2019-04-19 16:58:27.061 - [33mwarn[39m: history.0 Reconnection to DB.
2019-04-19 16:58:27.065 - [33mwarn[39m: history.0 Reconnection to DB.
2019-04-19 16:58:27.101 - [33mwarn[39m: maxcube.0 Reconnection to DB.
2019-04-19 16:58:27.105 - [33mwarn[39m: maxcube.0 Reconnection to DB.
2019-04-19 16:58:27.256 - [33mwarn[39m: tr-064.0 Reconnection to DB.
2019-04-19 16:58:27.258 - [33mwarn[39m: tr-064.0 Reconnection to DB.
2019-04-19 16:58:27.280 - [33mwarn[39m: discovery.0 Reconnection to DB.
2019-04-19 16:58:27.283 - [33mwarn[39m: discovery.0 Reconnection to DB.
2019-04-19 16:58:27.308 - [33mwarn[39m: statistics.0 Reconnection to DB.
2019-04-19 16:58:27.311 - [33mwarn[39m: statistics.0 Reconnection to DB.
2019-04-19 16:58:27.385 - [33mwarn[39m: socketio.0 Reconnection to DB.
2019-04-19 16:58:27.388 - [33mwarn[39m: socketio.0 Reconnection to DB.
2019-04-19 16:58:27.419 - [33mwarn[39m: web.0 Reconnection to DB.
2019-04-19 16:58:27.422 - [33mwarn[39m: web.0 Reconnection to DB.
2019-04-19 16:58:27.471 - [33mwarn[39m: modbus.0 Reconnection to DB.
2019-04-19 16:58:27.474 - [33mwarn[39m: modbus.0 Reconnection to DB.
2019-04-19 16:58:27.944 - [33mwarn[39m: cloud.0 Reconnection to DB.
2019-04-19 16:58:27.944 - [33mwarn[39m: admin.0 Reconnection to DB.
2019-04-19 16:58:27.947 - [33mwarn[39m: cloud.0 Reconnection to DB.
2019-04-19 16:58:27.947 - [33mwarn[39m: admin.0 Reconnection to DB.
2019-04-19 16:58:27.957 - [33mwarn[39m: lgtv.0 Reconnection to DB.
2019-04-19 16:58:27.964 - [33mwarn[39m: tr-064.1 Reconnection to DB.
2019-04-19 16:58:27.966 - [33mwarn[39m: tr-064.1 Reconnection to DB.
2019-04-19 16:58:27.959 - [33mwarn[39m: lgtv.0 Reconnection to DB.
2019-04-19 16:58:27.995 - [33mwarn[39m: sonoff.0 Reconnection to DB.
2019-04-19 16:58:27.998 - [33mwarn[39m: sonoff.0 Reconnection to DB.
2019-04-19 16:58:28.181 - [33mwarn[39m: denon.0 Reconnection to DB.
2019-04-19 16:58:28.184 - [33mwarn[39m: denon.0 Reconnection to DB.
2019-04-19 16:58:28.715 - [33mwarn[39m: rpi2.0 Reconnection to DB.
2019-04-19 16:58:28.720 - [33mwarn[39m: rpi2.0 Reconnection to DB.
2019-04-19 16:58:29.384 - [32minfo[39m: sonoff.0 Client [Temp_Gefrierschrank] connected with secret 1555685909382_1458
2019-04-19 16:58:29.459 - [34mdebug[39m: statistics.0 redis pmessage io.lgtv.0.states.on io.lgtv.0.states.on {"val":false,"ack":true,"ts":1555685909458,"q":0,"from":"system.adapter.lgtv.0","lc":1555617750672}
2019-04-19 16:58:29.460 - [34mdebug[39m: statistics.0 [STATE CHANGE] ======================= lgtv.0.states.on =======================
2019-04-19 16:58:29.460 - [34mdebug[39m: statistics.0 [STATE CHANGE] stateChange => false [true]
2019-04-19 16:58:29.460 - [34mdebug[39m: statistics.0 [STATE CHANGE] count call lgtv.0.states.on with false
2019-04-19 16:58:29.461 - [34mdebug[39m: statistics.0 new pulse false ? false
2019-04-19 16:58:29.461 - [34mdebug[39m: statistics.0 [STATE CHANGE] timecount call lgtv.0.states.on with false
2019-04-19 16:58:29.464 - [34mdebug[39m: statistics.0 [STATE CHANGE] 1->0 delta 10703171 state 1555617750672 last 1555607047501Noch zur Info:
History und Statistic werden auf einem USB-Stick gespeichert.
Die Datenpunkte im RAM habe ich auf 400 verkleinert.Ich hoffe das Log ist aussagekräftig. Wollte nicht noch mehr hier hinein kopieren.
Ich danke Euch
Gregor
-
@GregorS sagte in ioBroker / Vis / Pi sind immer wieder nicht erreichbar:
code: 'ENOMEM
Dein Speicher ist voll.
Wieviele Adapter laufen bei dir
-
@Homoran
Es sind 31 Adapter mit Instanzen und 20 Prozesse.
Woran hast du es erkannt?
-
@GregorS
Ein pi 2/3 ist nur bis 15/20 Adapter "sicher".
Darüberhinaus wird das RAM knapp.Mit 31 Adaptern hast du den RAM schon 3xtrem ausgereizt.
Hier solltest du dir über eine andere Hardware Gedanken machen. -
@Homoran
Ok. Das ist natürlich Mist.
Aber so ein System wird von selber immer größer.
Weclche Hardware würdest du empfehlen?
Sollte ein kleiner Rechner sein wegen dem Stromverbrauch.Ich danke dir für deine Hilfe.
Hätte ewig nach dem Fehler gesucht.
-
@GregorS sagte in ioBroker / Vis / Pi sind immer wieder nicht erreichbar:
Hätte ewig nach dem Fehler gesucht.
Steht doch im log. Hatte ich dir im vorletzten post rausgesucht.
@GregorS sagte in ioBroker / Vis / Pi sind immer wieder nicht erreichbar:
Weclche Hardware würdest du empfehlen?
Wenn die immer größer wird, solltest du vielleict an ei en NUC denken.
Ich hatte allerdings meine Installation (die produktive) über Jahre auf einem Tinkerboard bevor ich jetzt wegen proxmox auch auf einen nuc mit mehreren VMs umgezogen bin.Der Nuc (je nach Modell) braucht etwa 6-10W, was im Bereich von 2-3 raspis liegt.
-
@Homoran
Hab mir mal das Tinkerboard angeschaut.
Würde mir persönlich zusagen, die Version mit 16GB MMC
Wo ist bei ihm die Leistungsgrenze erreicht?
Kann ich mit einem Backup und dem entsprechenden Image für das Tinkerboard direkt umsteigen,
oder muss ich alles neu konfigurieren?Last but not least
Vielen Dank für die kompetente Hilfe.Gruß
Gregor -
@GregorS sagte in ioBroker / Vis / Pi sind immer wieder nicht erreichbar:
Würde mir persönlich zusagen, die Version mit 16GB MMC
Wo ist bei ihm die Leistungsgrenze erreicht?Ich habe noch das gute alte Tinkerboard (ohne S und ohne emmc).
Ich bin damit nie an Grenzen gestoßen, obwohl meine Installation nicht gerade klein ist.
Allerdings keine alexa und noch wenig scripte.Das Tinkerboard war/ist mein Favorit, weil es den schnellsten Cardreader (bei emmc nicht wichtig) und ein dual achannel ddr4 ram besitzt.
Dadurch ist er um längen besser was die I/O last sngeht, als anderer SBC.