NEWS
Neu aufgesetzten PI3 System und wieder Fehler
-
Ich hatte nachdem mein System sehr unstabil wurde eine neue SD Karte genommen und das System neu aufgesetzt.
Leider hängt sich das System trotzdem hin und wieder auf. Ich bin recht ratlos. Ich nutze IObroker schon seit Jahren und sehr lange Fehlerfrei.
Aber was jetzt los ist kann ich nicht finden.
Könnt ihr was erkennen?
2019-02-03 14:12:28.904 - info: harmony.0 [DISCOVER] Discovered Harmony Hub (192.168.1.17) and will try to connect 2019-02-03 14:12:28.876 - info: javascript.0 script.js.Skript1: request: http://192.168.1.59/fsapi/GET/netRemote.play.info.name?pin=1234&sid=1313667682 2019-02-03 14:12:28.878 - info: javascript.0 script.js.Skript1: request: http://192.168.1.59/fsapi/GET/netRemote.play.info.text?pin=1234&sid=1313667682 2019-02-03 14:12:28.880 - info: javascript.0 script.js.Skript1: request: http://192.168.1.59/fsapi/GET/netRemote.sys.audio.volume?pin=1234&sid=1313667682 2019-02-03 14:12:36.690 - info: smartmeter.1 Received 7 values, 3 updated 2019-02-03 14:12:37.040 - info: harmony.0 [DISCOVER] Discovered Harmony Hub (192.168.1.17) and will try to connect 2019-02-03 14:12:38.476 - debug: admin.0 statesDB connected 2019-02-03 14:12:38.490 - debug: admin.0 statesDB connected 2019-02-03 14:12:38.508 - warn: harmony.0 Reconnection to DB. 2019-02-03 14:12:38.512 - warn: harmony.0 Reconnection to DB. 2019-02-03 14:12:38.524 - warn: spotify-premium.0 Reconnection to DB. 2019-02-03 14:12:38.527 - warn: spotify-premium.0 Reconnection to DB. 2019-02-03 14:12:38.531 - warn: simple-api.0 Reconnection to DB. 2019-02-03 14:12:38.539 - warn: hue.0 Reconnection to DB. 2019-02-03 14:12:38.528 - warn: socketio.0 Reconnection to DB. 2019-02-03 14:12:38.537 - warn: socketio.0 Reconnection to DB. 2019-02-03 14:12:38.537 - warn: simple-api.0 Reconnection to DB. 2019-02-03 14:12:38.544 - warn: hue.0 Reconnection to DB. 2019-02-03 14:12:38.555 - warn: pushover.0 Reconnection to DB. 2019-02-03 14:12:38.557 - warn: fritzbox.0 Reconnection to DB. 2019-02-03 14:12:38.564 - warn: scenes.0 Reconnection to DB. 2019-02-03 14:12:38.564 - warn: fritzbox.0 Reconnection to DB. 2019-02-03 14:12:38.564 - warn: pushover.0 Reconnection to DB. 2019-02-03 14:12:38.577 - warn: alexa2.0 Reconnection to DB. 2019-02-03 14:12:38.580 - warn: backitup.0 Reconnection to DB. 2019-02-03 14:12:38.584 - warn: hm-rpc.0 Reconnection to DB. 2019-02-03 14:12:38.587 - warn: smartmeter.1 Reconnection to DB. 2019-02-03 14:12:38.589 - warn: hm-rpc.0 Reconnection to DB. 2019-02-03 14:12:38.585 - warn: alexa2.0 Reconnection to DB. 2019-02-03 14:12:38.594 - warn: backitup.0 Reconnection to DB. 2019-02-03 14:12:38.591 - warn: smartmeter.1 Reconnection to DB. 2019-02-03 14:12:38.569 - warn: scenes.0 Reconnection to DB. 2019-02-03 14:12:38.607 - warn: web.0 Reconnection to DB. 2019-02-03 14:12:38.616 - warn: cloud.0 Reconnection to DB. 2019-02-03 14:12:38.611 - warn: web.0 Reconnection to DB. 2019-02-03 14:12:38.619 - warn: cloud.0 Reconnection to DB. 2019-02-03 14:12:38.631 - warn: smartmeter.0 Reconnection to DB. 2019-02-03 14:12:38.634 - warn: admin.0 Reconnection to DB. 2019-02-03 14:12:38.639 - warn: tr-064.0 Reconnection to DB. 2019-02-03 14:12:38.641 - warn: hm-rega.0 Reconnection to DB. 2019-02-03 14:12:38.635 - warn: smartmeter.0 Reconnection to DB. 2019-02-03 14:12:38.643 - warn: tr-064.0 Reconnection to DB. 2019-02-03 14:12:38.645 - warn: hm-rega.0 Reconnection to DB. 2019-02-03 14:12:38.649 - warn: admin.0 Reconnection to DB. 2019-02-03 14:12:38.977 - warn: javascript.1 Reconnection to DB. 2019-02-03 14:12:38.985 - warn: javascript.0 Reconnection to DB. 2019-02-03 14:12:38.995 - warn: javascript.2 Reconnection to DB. 2019-02-03 14:12:39.026 - error: javascript.0 already running 2019-02-03 14:12:39.048 - error: javascript.2 already running 2019-02-03 14:12:39.082 - error: simple-api.0 already running 2019-02-03 14:12:39.087 - error: javascript.1 already running 2019-02-03 14:12:39.118 - error: scenes.0 already running 2019-02-03 14:12:39.131 - error: hue.0 already running 2019-02-03 14:12:39.137 - error: socketio.0 already running 2019-02-03 14:12:39.136 - error: web.0 already running 2019-02-03 14:12:39.209 - error: spotify-premium.0 already running 2019-02-03 14:12:39.271 - error: hm-rpc.0 already running 2019-02-03 14:12:39.289 - error: smartmeter.1 already running 2019-02-03 14:12:39.343 - info: fritzbox.0 starting. Version 0.2.1 in /opt/iobroker/node_modules/iobroker.fritzbox, node: v8.11.1 2019-02-03 14:12:39.344 - info: pushover.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.pushover, node: v8.11.1 2019-02-03 14:12:39.356 - info: harmony.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.harmony, node: v8.11.1 2019-02-03 14:12:39.356 - info: backitup.0 starting. Version 1.0.8 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.11.1 2019-02-03 14:12:39.370 - info: tr-064.0 starting. Version 0.4.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v8.11.1 2019-02-03 14:12:39.371 - info: smartmeter.0 starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v8.11.1 2019-02-03 14:12:39.361 - info: fritzbox.0 try to connect: 192.168.1.1 2019-02-03 14:12:39.374 - info: fritzbox.0 adapter connected to fritzbox: 192.168.1.1 2019-02-03 14:12:39.382 - info: cloud.0 starting. Version 2.6.2 in /opt/iobroker/node_modules/iobroker.cloud, node: v8.11.1 2019-02-03 14:12:39.388 - info: cloud.0 Connecting with https://iobroker.net:10555 with "Chemieka_0d01b110-dfb8-11e6-a107-8fb94d042cff" 2019-02-03 14:12:39.403 - info: alexa2.0 starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.alexa2, node: v8.11.1 2019-02-03 14:12:39.407 - info: hm-rega.0 starting. Version 2.1.7 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v8.11.1 2019-02-03 14:12:39.411 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v8.11.1 2019-02-03 14:12:39.840 - info: smartmeter.0 Received 7 values, 3 updated 2019-02-03 14:12:40.149 - error: host.ioBroker-RasPi instance system.adapter.spotify-premium.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.150 - info: host.ioBroker-RasPi Restart adapter system.adapter.spotify-premium.0 because enabled 2019-02-03 14:12:40.159 - error: host.ioBroker-RasPi instance system.adapter.javascript.2 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.159 - info: host.ioBroker-RasPi Restart adapter system.adapter.javascript.2 because enabled 2019-02-03 14:12:40.167 - error: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.167 - info: host.ioBroker-RasPi Restart adapter system.adapter.javascript.0 because enabled 2019-02-03 14:12:40.175 - error: host.ioBroker-RasPi instance system.adapter.hue.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.176 - info: host.ioBroker-RasPi Restart adapter system.adapter.hue.0 because enabled 2019-02-03 14:12:40.184 - error: host.ioBroker-RasPi instance system.adapter.smartmeter.1 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.184 - info: host.ioBroker-RasPi Restart adapter system.adapter.smartmeter.1 because enabled 2019-02-03 14:12:40.192 - error: host.ioBroker-RasPi instance system.adapter.scenes.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.193 - info: host.ioBroker-RasPi Restart adapter system.adapter.scenes.0 because enabled 2019-02-03 14:12:40.201 - error: host.ioBroker-RasPi instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.201 - info: host.ioBroker-RasPi Restart adapter system.adapter.socketio.0 because enabled 2019-02-03 14:12:40.209 - error: host.ioBroker-RasPi instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.209 - info: host.ioBroker-RasPi Restart adapter system.adapter.simple-api.0 because enabled 2019-02-03 14:12:40.217 - error: host.ioBroker-RasPi instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.218 - info: host.ioBroker-RasPi Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-03 14:12:40.226 - error: host.ioBroker-RasPi instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.226 - info: host.ioBroker-RasPi Restart adapter system.adapter.web.0 because enabled 2019-02-03 14:12:40.234 - error: host.ioBroker-RasPi instance system.adapter.javascript.1 terminated with code 7 (Adapter already running) 2019-02-03 14:12:40.234 - info: host.ioBroker-RasPi Restart adapter system.adapter.javascript.1 because enabled 2019-02-03 14:12:40.276 - info: fritzbox.0 starting. Version 0.2.1 in /opt/iobroker/node_modules/iobroker.fritzbox, node: v8.11.1 2019-02-03 14:12:40.279 - info: pushover.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.pushover, node: v8.11.1 2019-02-03 14:12:40.282 - info: harmony.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.harmony, node: v8.11.1 2019-02-03 14:12:40.279 - info: smartmeter.0 starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.smartmeter, node: v8.11.1 2019-02-03 14:12:40.292 - info: cloud.0 starting. Version 2.6.2 in /opt/iobroker/node_modules/iobroker.cloud, node: v8.11.1 2019-02-03 14:12:40.303 - warn: history.0 Reconnection to DB. 2019-02-03 14:12:40.301 - info: hm-rega.0 starting. Version 2.1.7 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v8.11.1 2019-02-03 14:12:40.280 - info: fritzbox.0 try to connect: 192.168.1.1 2019-02-03 14:12:40.299 - info: alexa2.0 starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.alexa2, node: v8.11.1 2019-02-03 14:12:40.313 - info: fritzbox.0 adapter connected to fritzbox: 192.168.1.1 2019-02-03 14:12:40.324 - info: backitup.0 starting. Version 1.0.8 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.11.1 2019-02-03 14:12:40.299 - info: cloud.0 Connecting with https://iobroker.net:10555 with "Chemieka_0d01b110-dfb8-11e6-a107-8fb94d042cff" 2019-02-03 14:12:40.309 - warn: history.0 Reconnection to DB. 2019-02-03 14:12:40.311 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT 2019-02-03 14:12:40.376 - info: hm-rega.0 ReGaHSS 192.168.1.25 up 2019-02-03 14:12:40.347 - info: backitup.0 [minimal] backup was activated at 02:00 every 30 day(s) 2019-02-03 14:12:40.355 - info: backitup.0 [ccu] backup was activated at 01:30 every 30 day(s) 2019-02-03 14:12:40.366 - info: backitup.0 [total] backup was activated at 03:00 every 30 day(s) 2019-02-03 14:12:40.385 - info: hm-rega.0 time difference local-ccu 0s 2019-02-03 14:12:40.416 - info: hm-rega.0 added/updated 1 favorites to enum.favorites 2019-02-03 14:12:40.444 - info: hm-rega.0 added/updated functions to enum.functions 2019-02-03 14:12:40.464 - info: hm-rega.0 added/updated rooms to enum.rooms 2019-02-03 14:12:40.475 - info: tr-064.0 starting. Version 0.4.18 in /opt/iobroker/node_modules/iobroker.tr-064, node: v8.11.1 2019-02-03 14:12:40.481 - info: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v8.11.1
-
Wenn Du magst, dann wechsele doch auf Node 8.15. In Versionen <8.12 war ggf. noch ein Fehler, der im Laufe der Zeit RAM belegt hat.
-
Oh gern aber wie mache ich das?
-
Abschnitt „Upgrade von nodejs und npm“
-
Bei 2. Befehl schon ein Fehler
pi@ioBroker-RasPi:~ $ iobroker stop iobroker controller daemon is not running pi@ioBroker-RasPi:~ $ apt-get --purge remove node nodejs E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: Keine Berechtigung) E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, sin d Sie root? pi@ioBroker-RasPi:~ $
-
Hast Du die dritte Zeile der Anleitung gelesen? Sudo?
-
Ah ja
Sollte geklappt haben.
Steht jetzt
Plattform: linux
RAM: 927.2 MB
Node.js: v8.15.0
NPM: v6.4.1
Ich werde beobachten ob es nun ruhiger wird.
<size size="150">:D Herzlichen Dank zunächst hoffe das war die Lösung. :D</size>
-
Ich drücke Dir die Daumen.
Es kann gut sein, dass Linux weg zu wenig RAM verschiedene Prozesse killed. Schaue, wenn das wieder passiert nach „oom-killer“ im syslog von Linux.
-
Das kann gut möglich sein. Aber so viele Adapter nutze ich garnicht aber der RAM ist immer fast voll.
Was könnte man dann machen?
-
-
Bis jetzt ist alles ruhig.
Ich finde diese Information gehört irgendwie mit zur Installation Anweisung.
-
Also mein Link ging zu Installationsanleitung. [emoji847]
-
Das stimmt. Ich hatte allerdings ein fertiges Image genommen und war da nicht drüber gestolpert.