@J-A-R-V-I-S sagte in ioBroker startet in Endlosschleife:
Probier mal den Fixer aus. Wenn du den ioBroker vor über einem Jahr installiert hast, dann kann dir der Beitrag vielleicht helfen. Aber bitte vorher sichern!!
DAS WAR'S!
System läuft wieder... Vielen Dank an Euch. 
Bei der Gelegenheit gleich eine andere Frage. Ich habe noch ein MultihostSystem mit 3 RPi. Kann ich das da auch gefahrlos drüberlaufen lassen - quasi vorbeugend, oder sollte das bei Multihost nicht gemacht werden?
Ich habe jetzt mal in das letzte Log geschaut und da kommt folgender Block immer wiederkehrend, bis um 14:16:17 Ende war (hab mal 3 Blöcke drin gelassen):
2019-11-03 14:01:07.438 - [32minfo[39m: iobroker _restart
2019-11-03 14:01:07.574 - [32minfo[39m: admin.0 https server listening on port 8081
2019-11-03 14:01:07.575 - [32minfo[39m: admin.0 Use link "https://localhost:8081" to configure.
2019-11-03 14:01:07.808 - [32minfo[39m: admin.0 Repository received successfully.
2019-11-03 14:01:07.819 - [32minfo[39m: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
2019-11-03 14:01:07.836 - [32minfo[39m: mihome-vacuum.0 Expert mode disabled, states deleded
2019-11-03 14:01:07.838 - [32minfo[39m: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
2019-11-03 14:01:08.082 - [32minfo[39m: iobroker Starting node restart.js
2019-11-03 14:01:08.103 - [32minfo[39m: iobroker exit 0
2019-11-03 14:01:08.429 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:13.435 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:19.701 - [32minfo[39m: host.io_broker iobroker.js-controller version 1.4.2 js-controller starting
2019-11-03 14:01:19.708 - [32minfo[39m: host.io_broker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-11-03 14:01:19.709 - [32minfo[39m: host.io_broker hostname: io_broker, node: v8.15.0
2019-11-03 14:01:19.713 - [32minfo[39m: host.io_broker ip addresses: 192.168.0.XXX XXXXXXX
2019-11-03 14:01:19.857 - [32minfo[39m: host.io_broker inMem-states listening on port 9000
2019-11-03 14:01:20.113 - [32minfo[39m: host.io_broker inMem-objects listening on port 9001
2019-11-03 14:01:20.131 - [32minfo[39m: host.io_broker InMemoryDB connected
2019-11-03 14:01:20.160 - [32minfo[39m: host.io_broker 28 instances found
2019-11-03 14:01:20.189 - [32minfo[39m: host.io_broker starting 18 instances
2019-11-03 14:01:20.241 - [32minfo[39m: host.io_broker instance system.adapter.admin.0 started with pid 4704
2019-11-03 14:01:22.432 - [31merror[39m: admin.0 setObject id missing!!
2019-11-03 14:01:22.454 - [32minfo[39m: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
2019-11-03 14:01:22.509 - [32minfo[39m: admin.0 Request actual repository...
2019-11-03 14:01:22.518 - [32minfo[39m: admin.0 requesting all states
2019-11-03 14:01:22.521 - [32minfo[39m: admin.0 requesting all objects
2019-11-03 14:01:23.068 - [32minfo[39m: host.io_broker Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2019-11-03 14:01:24.152 - [32minfo[39m: admin.0 received all states
2019-11-03 14:01:24.206 - [32minfo[39m: host.io_broker instance system.adapter.mihome-vacuum.0 started with pid 4714
2019-11-03 14:01:24.954 - [32minfo[39m: admin.0 received all objects
2019-11-03 14:01:25.156 - [31merror[39m: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
2019-11-03 14:01:25.161 - [31merror[39m: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.writeFileSync (fs.js:1299:33)
at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
2019-11-03 14:01:25.163 - [32minfo[39m: iobroker _restart
2019-11-03 14:01:25.269 - [32minfo[39m: admin.0 https server listening on port 8081
2019-11-03 14:01:25.269 - [32minfo[39m: admin.0 Use link "https://localhost:8081" to configure.
2019-11-03 14:01:25.522 - [32minfo[39m: admin.0 Repository received successfully.
2019-11-03 14:01:25.639 - [32minfo[39m: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
2019-11-03 14:01:25.657 - [32minfo[39m: mihome-vacuum.0 Expert mode disabled, states deleded
2019-11-03 14:01:25.659 - [32minfo[39m: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
2019-11-03 14:01:25.860 - [32minfo[39m: iobroker Starting node restart.js
2019-11-03 14:01:25.884 - [32minfo[39m: iobroker exit 0
2019-11-03 14:01:26.217 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:31.227 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:37.445 - [32minfo[39m: host.io_broker iobroker.js-controller version 1.4.2 js-controller starting
2019-11-03 14:01:37.452 - [32minfo[39m: host.io_broker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-11-03 14:01:37.452 - [32minfo[39m: host.io_broker hostname: io_broker, node: v8.15.0
2019-11-03 14:01:37.456 - [32minfo[39m: host.io_broker ip addresses: 192.168.0.XXX XXXXXXXX
2019-11-03 14:01:37.599 - [32minfo[39m: host.io_broker inMem-states listening on port 9000
2019-11-03 14:01:37.855 - [32minfo[39m: host.io_broker inMem-objects listening on port 9001
2019-11-03 14:01:37.872 - [32minfo[39m: host.io_broker InMemoryDB connected
2019-11-03 14:01:37.901 - [32minfo[39m: host.io_broker 28 instances found
2019-11-03 14:01:37.931 - [32minfo[39m: host.io_broker starting 18 instances
2019-11-03 14:01:37.983 - [32minfo[39m: host.io_broker instance system.adapter.admin.0 started with pid 4780
2019-11-03 14:01:40.165 - [31merror[39m: admin.0 setObject id missing!!
2019-11-03 14:01:40.187 - [32minfo[39m: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
2019-11-03 14:01:40.242 - [32minfo[39m: admin.0 Request actual repository...
2019-11-03 14:01:40.250 - [32minfo[39m: admin.0 requesting all states
2019-11-03 14:01:40.253 - [32minfo[39m: admin.0 requesting all objects
2019-11-03 14:01:40.792 - [32minfo[39m: host.io_broker Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2019-11-03 14:01:41.893 - [32minfo[39m: admin.0 received all states
2019-11-03 14:01:41.946 - [32minfo[39m: host.io_broker instance system.adapter.mihome-vacuum.0 started with pid 4790
2019-11-03 14:01:42.656 - [32minfo[39m: admin.0 received all objects
2019-11-03 14:01:42.896 - [31merror[39m: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
2019-11-03 14:01:42.901 - [31merror[39m: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.writeFileSync (fs.js:1299:33)
at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
2019-11-03 14:01:42.903 - [32minfo[39m: iobroker _restart
2019-11-03 14:01:42.965 - [32minfo[39m: admin.0 https server listening on port 8081
2019-11-03 14:01:42.965 - [32minfo[39m: admin.0 Use link "https://localhost:8081" to configure.
2019-11-03 14:01:43.203 - [32minfo[39m: admin.0 Repository received successfully.
2019-11-03 14:01:43.344 - [32minfo[39m: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
2019-11-03 14:01:43.362 - [32minfo[39m: mihome-vacuum.0 Expert mode disabled, states deleded
2019-11-03 14:01:43.364 - [32minfo[39m: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
2019-11-03 14:01:43.552 - [32minfo[39m: iobroker Starting node restart.js
2019-11-03 14:01:43.575 - [32minfo[39m: iobroker exit 0
2019-11-03 14:01:43.908 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:46.152 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:48.918 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:52.163 - [32minfo[39m: host.io_broker received SIGTERM
2019-11-03 14:01:55.136 - [32minfo[39m: host.io_broker iobroker.js-controller version 1.4.2 js-controller starting
2019-11-03 14:01:55.142 - [32minfo[39m: host.io_broker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2019-11-03 14:01:55.143 - [32minfo[39m: host.io_broker hostname: io_broker, node: v8.15.0
2019-11-03 14:01:55.147 - [32minfo[39m: host.io_broker ip addresses: 192.168.0.XXX XXXXXXXXXX
2019-11-03 14:01:55.289 - [32minfo[39m: host.io_broker inMem-states listening on port 9000
2019-11-03 14:01:55.542 - [32minfo[39m: host.io_broker inMem-objects listening on port 9001
2019-11-03 14:01:55.559 - [32minfo[39m: host.io_broker InMemoryDB connected
2019-11-03 14:01:55.588 - [32minfo[39m: host.io_broker 28 instances found
2019-11-03 14:01:55.617 - [32minfo[39m: host.io_broker starting 18 instances
2019-11-03 14:01:55.669 - [32minfo[39m: host.io_broker instance system.adapter.admin.0 started with pid 4863
2019-11-03 14:01:57.884 - [31merror[39m: admin.0 setObject id missing!!
2019-11-03 14:01:57.906 - [32minfo[39m: admin.0 starting. Version 3.6.7 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0
2019-11-03 14:01:57.961 - [32minfo[39m: admin.0 Request actual repository...
2019-11-03 14:01:57.968 - [32minfo[39m: admin.0 requesting all states
2019-11-03 14:01:57.971 - [32minfo[39m: admin.0 requesting all objects
2019-11-03 14:01:58.535 - [32minfo[39m: host.io_broker Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2019-11-03 14:01:59.599 - [32minfo[39m: admin.0 received all states
2019-11-03 14:01:59.634 - [32minfo[39m: host.io_broker instance system.adapter.mihome-vacuum.0 started with pid 4879
2019-11-03 14:02:00.427 - [32minfo[39m: admin.0 received all objects
2019-11-03 14:02:00.584 - [31merror[39m: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
2019-11-03 14:02:00.589 - [31merror[39m: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak'
at Object.fs.openSync (fs.js:646:18)
at Object.fs.writeFileSync (fs.js:1299:33)
at Timeout.saveConfig [as _onTimeout] (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1897:16)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
2019-11-03 14:02:00.591 - [32minfo[39m: iobroker _restart
2019-11-03 14:02:00.753 - [32minfo[39m: admin.0 https server listening on port 8081
2019-11-03 14:02:00.754 - [32minfo[39m: admin.0 Use link "https://localhost:8081" to configure.
2019-11-03 14:02:01.005 - [32minfo[39m: admin.0 Repository received successfully.
2019-11-03 14:02:00.996 - [32minfo[39m: mihome-vacuum.0 starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v8.15.0
2019-11-03 14:02:01.016 - [32minfo[39m: mihome-vacuum.0 Expert mode disabled, states deleded
2019-11-03 14:02:01.018 - [32minfo[39m: mihome-vacuum.0 Create state clean_home for controlling by cloud adapter
2019-11-03 14:02:01.245 - [32minfo[39m: iobroker Starting node restart.js
2019-11-03 14:02:01.265 - [32minfo[39m: iobroker exit 0
2019-11-03 14:02:51.260 - [32minfo[39m: mihome-vacuum.0 New generation or new fw detected, create new states
2019-11-03 14:06:17.625 - [32minfo[39m: admin.0 terminating https server on port 8081
@Homoran sagte in ioBroker startet in Endlosschleife:
@Kaldi /opt/iobroker/log/Datum _des_Tages
Danke. Problem ist, dass ioBroker nicht startet und somit nur das "restart.log" existiert. Das andere sind alte logs bis zum 03.11.2019. Das ist das Datum seitdem er nicht mehr läuft... ich schau nochmal in das letzte Log - vielleicht finde ich noch was
@J-A-R-V-I-S sagte in ioBroker startet in Endlosschleife:
@Kaldi hast du schon versucht, den Loop zu unterbrechen und den ioBroker manuell zu starten?
Ja. ioBroker mit "iobroker stop" angehalten und mit "iobroker start" und alternativ auch mit "iobroker restart" wieder versucht zu starten.
Gibt es noch ein Log, welches mir evtl. Detailinformationen geben könnte?
@Homoran sagte in ioBroker startet in Endlosschleife:
@Kaldi sagte in ioBroker startet in Endlosschleife:
nach einem Neustart
Der Neustart wurde nicht etwa gemacht, weil etwas upgedatet wurde?
Nicht, dass ich wüsste. Also nicht aktiv - wobei mich die Versionsnummer des "admin" etwas verwundert. Installiert wurde der ioBroker vor etwas über einem Jahr.
Hallo,
ich bräuchte mal Hilfe von Experten...
Der ioBroker lief eigentlich ziemlich stabil, doch nach einem Neustart verfängt er sich in einer Endlosschleife und so ist auch kein Zugriff auf den Admin möglich.
per Tail -f habe ich mir die Aktivitäten angeschaut und folgendes wird ins Log geschrieben:
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19446": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "kill -KILL 19456": 1
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Exit code for "killall.sh": 123
Mon Dec 02 2019 10:16:22 GMT+0100 (CET)Starting daemon iobroker...
Mon Dec 02 2019 10:16:23 GMT+0100 (CET)Daemon iobroker started
Mon Dec 02 2019 10:16:24 GMT+0100 (CET)Restarting iobroker...
Mon Dec 02 2019 10:16:24 GMT+0100 (CET)Stopping daemon iobroker...
Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:29 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19511": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "kill -KILL 19521": 1
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Exit code for "killall.sh": 123
Mon Dec 02 2019 10:16:30 GMT+0100 (CET)Starting daemon iobroker...
Mon Dec 02 2019 10:16:31 GMT+0100 (CET)Daemon iobroker started
Mon Dec 02 2019 10:16:32 GMT+0100 (CET)Restarting iobroker...
Mon Dec 02 2019 10:16:32 GMT+0100 (CET)Stopping daemon iobroker...
list instances zeigt folgendes an:
pi@io_broker:/opt/iobroker $ iobroker list instances
system.adapter.admin.0 : admin - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
system.adapter.alexa2.0 : alexa2 - enabled
system.adapter.amazon-dash.0 : amazon-dash - enabled
system.adapter.backitup.0 : backitup - enabled
system.adapter.cloud.0 : cloud - enabled
system.adapter.discovery.0 : discovery - disabled
system.adapter.flot.0 : flot - enabled
system.adapter.fritzdect.0 : fritzdect - enabled
system.adapter.harmony.0 : harmony - disabled
system.adapter.hue.0 : hue - disabled, port: 80
system.adapter.icons-mfd-png.0 : icons-mfd-png - enabled
system.adapter.icons-mfd-svg.0 : icons-mfd-svg - enabled
system.adapter.info.0 : info - enabled
system.adapter.javascript.0 : javascript - enabled
system.adapter.mihome-vacuum.0 : mihome-vacuum - enabled, port: 54321
system.adapter.mqtt.0 : mqtt - disabled, port: 1883
system.adapter.node-red.0 : node-red - disabled, port: 1880, bind: 0.0.0.0
system.adapter.parser.0 : parser - enabled
system.adapter.scenes.0 : scenes - enabled
system.adapter.sql.0 : sql - enabled, port: 0
system.adapter.telegram.0 : telegram - disabled, port: 8443, bind: 0.0.0.0
system.adapter.text2command.0 : text2command - enabled
system.adapter.tr-064.0 : tr-064 - disabled
system.adapter.vis-colorpicker.0 : vis-colorpicker - enabled
system.adapter.vis-hqwidgets.0 : vis-hqwidgets - enabled
system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd - enabled
system.adapter.vis.0 : vis - enabled
system.adapter.web.0 : web - enabled, port: 8082, bind: 0.0.0.0, run as: admin
Wo kann ich ansetzen?
Info zu Versionen:
pi@io_broker:/opt/iobroker $ npm -v
6.4.1
pi@io_broker:/opt/iobroker $ node -v
v8.15.0
pi@io_broker:/opt/iobroker $ nodejs -v
v8.15.0
Adapter Versionen:
pi@io_broker:/opt/iobroker $ iobroker list adapters
system.adapter.admin : admin - 3.6.2
system.adapter.discovery : discovery - 1.2.1
system.adapter.mihome-vacuum : mihome-vacuum - 1.1.5
system.adapter.cloud : cloud - 2.6.2
system.adapter.web : web - 2.4.1
system.adapter.sql : sql - 1.9.2
system.adapter.flot : flot - 1.9.2
system.adapter.node-red : node-red - 1.7.1
system.adapter.harmony : harmony - 1.0.0
system.adapter.hue : hue - 1.1.0
system.adapter.tr-064 : tr-064 - 0.4.18
system.adapter.backitup : backitup - 0.4.2
system.adapter.mqtt : mqtt - 2.0.4
system.adapter.telegram : telegram - 1.3.6
system.adapter.text2command : text2command - 1.2.4
system.adapter.scenes : scenes - 1.1.0
system.adapter.alexa2 : alexa2 - 2.6.4
system.adapter.parser : parser - 1.0.7
system.adapter.javascript : javascript - 4.0.5
system.adapter.fritzdect : fritzdect - 0.1.4
system.adapter.vis : vis - 1.1.10
system.adapter.yahka : yahka - 0.8.2
system.adapter.vis-hqwidgets : vis-hqwidgets - 1.1.2
system.adapter.vis-colorpicker : vis-colorpicker - 1.1.1
system.adapter.vis-jqui-mfd : vis-jqui-mfd - 1.0.12
system.adapter.icons-mfd-svg : icons-mfd-svg - 1.0.2
system.adapter.icons-mfd-png : icons-mfd-png - 1.0.2
system.adapter.amazon-dash : amazon-dash - 0.3.1
system.adapter.info : info - 1.4.1
Vielen Dank!
Hallo,
ich habe meinen V1 auch im IOBroker intagriert und Zonen erstellt das funktioniert auch einwandfrei. Wie habt ihr das mit der gesamte Wohnung reinigen Realisiert? `
Ich habe das mit dem "Szenen" Adapter gemacht. Dort kann man ja mehrere Aktionen miteinander verknüpfen…
Seit 2 Tagen macht mein Parser Adapter Probleme.
Ich nutze ihn, um einen Kostal Wechselrichter auszulesen. Bislang hat das auch tadellos funktioniert, bis vorgestern. Nach einiger Zeit (zwischen 30 Minuten und 2 Stunden) werden keine Daten mehr aktualisiert.
Starte ich den Adapter neu, funktioniert er wieder einige Zeit und bleibt dann wieder stehen.
Ein Blick ins Log zeigt beim Starten des Adapters folgende Fehlermeldung:
parser.0 2019-01-26 12:16:21.903 error Cannot read file "/opt/iobroker/": Error: EISDIR: illegal operation on a directory, read
Ich habe ein Multihost System, der Parser läuft auf dem Slave.
Wo setze ich mit der Fehleranalyse an?
Danke.
Wir kommen der Sache näher!
sudo chown -R iobroker:iobroker /home/iobroker ```` `
falsch - wir haben es geschafft!
$ ./iobroker add smartmeter --host ioBroker-Strom
NPM version: 6.4.1
npm install iobroker.smartmeter --production --save --prefix "/opt/iobroker" (System call)
host.ioBroker-Strom install adapter smartmeter
got /opt/iobroker/node_modules/iobroker.smartmeter/admin
upload [5] smartmeter.admin /opt/iobroker/node_modules/iobroker.smartmeter/admin/words.js words.js application/javascript
upload [4] smartmeter.admin /opt/iobroker/node_modules/iobroker.smartmeter/admin/tooltip.css tooltip.css text/css
upload [3] smartmeter.admin /opt/iobroker/node_modules/iobroker.smartmeter/admin/smartmeter.png smartmeter.png image/png
upload [2] smartmeter.admin /opt/iobroker/node_modules/iobroker.smartmeter/admin/smartmeter.jpg smartmeter.jpg image/jpeg
upload [1] smartmeter.admin /opt/iobroker/node_modules/iobroker.smartmeter/admin/questionmark.png questionmark.png image/png
upload [0] smartmeter.admin /opt/iobroker/node_modules/iobroker.smartmeter/admin/index.html index.html text/html
host.ioBroker-Strom object system.adapter.smartmeter created
host.ioBroker-Strom create instance smartmeter
host.ioBroker-Strom object system.adapter.smartmeter.0.outputCount created
host.ioBroker-Strom object system.adapter.smartmeter.0.inputCount created
host.ioBroker-Strom object system.adapter.smartmeter.0.uptime created
host.ioBroker-Strom object system.adapter.smartmeter.0.memRss created
host.ioBroker-Strom object system.adapter.smartmeter.0.memHeapTotal created
host.ioBroker-Strom object system.adapter.smartmeter.0.memHeapUsed created
host.ioBroker-Strom object system.adapter.smartmeter.0.connected created
host.ioBroker-Strom object system.adapter.smartmeter.0.alive created
host.ioBroker-Strom object system.adapter.smartmeter.0 created
process exited with code 0
Vielen,vielen Dank! Die Hilfestellungen haben mir geholfen, das System besser zu verstehen.
