IOBroker hat sich beendet
-
Hi
Heute habe ich festestellt, dass aus mir unbekannten Gründen IObroker sich wohl um 16:46 beendet hat.
Iobroker status lieferte jedenfalls, dass er nicht läuft und das Webinterface war auch nicht da.Ich habe hier einen Auszug aus dem IObroker Log und eine Leerzeile zwischen dem Beenden und dem Neustart gemacht. Kann da jemand erkennen was der Grund gewesen sein könnte?
2019-02-24 16:44:31.087 - [32minfo[39m: mqtt-client.0 trying to reconnect to broker 2019-02-24 16:44:31.399 - [32minfo[39m: mqtt-client.0 connected to broker 2019-02-24 16:44:31.526 - [33mwarn[39m: mqtt-client.0 client offline 2019-02-24 16:45:00.042 - [32minfo[39m: host.ioBroker-Rock64 instance system.adapter.tvspielfilm.0 started with pid 25470 2019-02-24 16:45:01.527 - [32minfo[39m: mqtt-client.0 trying to reconnect to broker 2019-02-24 16:45:01.939 - [32minfo[39m: mqtt-client.0 connected to broker 2019-02-24 16:45:02.105 - [33mwarn[39m: mqtt-client.0 client offline 2019-02-24 16:45:02.137 - [32minfo[39m: tvspielfilm.0 States connected to redis: 127.0.0.1:6379 2019-02-24 16:45:02.237 - [32minfo[39m: tvspielfilm.0 starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tvspielfilm, node: v8.15.0 2019-02-24 16:45:02.310 - [32minfo[39m: tvspielfilm.0 objects written 2019-02-24 16:45:32.107 - [32minfo[39m: mqtt-client.0 trying to reconnect to broker 2019-02-24 16:45:32.568 - [32minfo[39m: mqtt-client.0 connected to broker 2019-02-24 16:45:32.758 - [33mwarn[39m: mqtt-client.0 client offline 2019-02-24 16:46:02.311 - [32minfo[39m: tvspielfilm.0 force terminating adapter after 1 minute 2019-02-24 16:46:02.760 - [32minfo[39m: mqtt-client.0 trying to reconnect to broker 2019-02-24 16:46:02.845 - [32minfo[39m: host.ioBroker-Rock64 instance system.adapter.tvspielfilm.0 terminated with code 0 (OK) 2019-02-24 16:46:03.131 - [32minfo[39m: mqtt-client.0 connected to broker 2019-02-24 16:46:03.290 - [33mwarn[39m: mqtt-client.0 client offline 2019-02-24 16:46:08.651 - [32minfo[39m: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"] 2019-02-24 16:46:08.699 - [32minfo[39m: hm-rpc.2 xmlrpc -> 0 devices 2019-02-24 16:46:08.807 - [32minfo[39m: hm-rpc.2 xmlrpc <- newDevices 6 2019-02-24 16:46:08.861 - [32minfo[39m: hm-rpc.2 new HmIP devices/channels after filter: 0 2019-02-24 20:34:07.733 - [32minfo[39m: host.ioBroker-Rock64 iobroker.js-controller version 1.4.2 js-controller starting 2019-02-24 20:34:07.744 - [32minfo[39m: host.ioBroker-Rock64 Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker 2019-02-24 20:34:07.745 - [32minfo[39m: host.ioBroker-Rock64 hostname: ioBroker-Rock64, node: v8.15.0 2019-02-24 20:34:07.752 - [32minfo[39m: host.ioBroker-Rock64 ip addresses: 192.168.111.176 fd13:235b:7090:0:4f6a:8f2e:213a:f7b7 fd13:235b:7090::cda 2003:f4:4bf5:7300:18ca:ee03:93e4:3ef2 fd13:235b:7090:0:7897:fff:fefc:11b5 fe80::7897:fff:fefc:11b5 2019-02-24 20:34:08.787 - [32minfo[39m: host.ioBroker-Rock64 inMem-objects listening on port 9001 2019-02-24 20:34:08.818 - [32minfo[39m: host.ioBroker-Rock64 InMemoryDB connected 2019-02-24 20:34:08.910 - [32minfo[39m: host.ioBroker-Rock64 57 instances found 2019-02-24 20:34:09.134 - [32minfo[39m: host.ioBroker-Rock64 starting 27 instances 2019-02-24 20:34:09.234 - [32minfo[39m: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 5167 2019-02-24 20:34:09.363 - [32minfo[39m: host.ioBroker-Rock64 States connected to redis: 127.0.0.1:6379 2019-02-24 20:34:12.871 - [32minfo[39m: admin.0 States connected to redis: 127.0.0.1:6379 2019-02-24 20:34:13.111 - [31merror[39m: admin.0 setObject id missing!! 2019-02-24 20:34:13.123 - [32minfo[39m: admin.0 starting. Version 3.5.10 in /opt/iobroker/node_modules/iobroker.admin, node: v8.15.0 2019-02-24 20:34:13.155 - [32minfo[39m: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 5178 2019-02-24 20:34:13.166 - [32minfo[39m: admin.0 requesting all states 2019-02-24 20:34:13.171 - [32minfo[39m: admin.0 requesting all objects 2019-02-24 20:34:13.174 - [32minfo[39m: admin.0 Request actual repository... 2019-02-24 20:34:16.244 - [32minfo[39m: web.0 States connected to redis: 127.0.0.1:6379 2019-02-24 20:34:16.790 - [31merror[39m: web.0 setObject id missing!! 2019-02-24 20:34:16.822 - [32minfo[39m: web.0 starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.web, node: v8.15.0 2019-02-24 20:34:17.331 - [32minfo[39m: web.0 simpleAPI server listening on port 8082 2019-02-24 20:34:17.554 - [32minfo[39m: admin.0 received all states 2019-02-24 20:34:17.332 - [32minfo[39m: web.0 Allow states only when user is owner: false 2019-02-24 20:34:18.094 - [32minfo[39m: web.0 socket.io server listening on port 8082 2019-02-24 20:34:18.101 - [32minfo[39m: web.0 http server listening on port 8082 2019-02-24 20:34:19.019 - [32minfo[39m: vis.0 States connected to redis: 127.0.0.1:6379 2019-02-24 20:34:19.237 - [32minfo[39m: vis.0 starting. Version 1.1.8 in /opt/iobroker/node_modules/iobroker.vis, node: v8.15.0 2019-02-24 20:34:19.545 - [32minfo[39m: vis.0 vis license is OK. 2019-02-24 20:34:20.662 - [32minfo[39m: admin.0 received all objects 2019-02-24 20:34:21.189 - [32minfo[39m: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 5199 2019-02-24 20:34:22.214 - [32minfo[39m: host.ioBroker-Rock64 Update repository "default" under "http://download.iobroker.net/sources-dist.json" 2019-02-24 20:34:22.157 - [32minfo[39m: admin.0 http server listening on port 8081 2019-02-24 20:34:22.158 - [32minfo[39m: admin.0 Use link "http://localhost:8081" to configure. 2019-02-24 20:34:24.857 - [32minfo[39m: history.0 States connected to redis: 127.0.0.1:6379 2019-02-24 20:34:27.709 - [32minfo[39m: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 5213 2019-02-24 20:34:28.054 - [32minfo[39m: history.0 starting. Version 1.8.5 in /opt/iobroker/node_modules/iobroker.history, node: v8.15.0 2019-02-24 20:34:28.307 - [32minfo[39m: history.0 enabled logging of admin.0.info.updatesNumber (Count=1), Alias=false 2019-02-24 20:34:28.309 - [32minfo[39m: history.0 enabled logging of admin.0.info.updatesDas Syslog um diese Zeit sieht so aus
Feb 24 16:17:10 localhost ntpd[1319]: Soliciting pool server 78.46.107.140 Feb 24 16:17:10 localhost ntpd[1319]: Soliciting pool server 2001:1640:3:4::dead:beef Feb 24 16:17:11 localhost ntpd[1319]: Soliciting pool server 2001:638:502:137:21b:78ff:fe32:fe4c Feb 24 16:17:11 localhost ntpd[1319]: Soliciting pool server 94.16.115.123 Feb 24 16:17:11 localhost ntpd[1319]: Soliciting pool server 131.234.137.63 Feb 24 16:17:11 localhost ntpd[1319]: Soliciting pool server 195.201.19.162 Feb 24 16:17:12 localhost ntpd[1319]: Soliciting pool server 46.163.88.246 Feb 24 16:17:12 localhost ntpd[1319]: Soliciting pool server 2a01:238:43f2:8900:dd04:e3a0:ee11:a73d Feb 24 16:17:12 localhost ntpd[1319]: Listen normally on 12 eth0 [fd13:235b:7090::cda]:123 Feb 24 16:17:12 localhost ntpd[1319]: Listen normally on 13 eth0 [fd13:235b:7090:0:4f6a:8f2e:213a:f7b7]:123 Feb 24 16:17:12 localhost ntpd[1319]: Listen normally on 14 eth0 [2003:f4:4bf5:7300:18ca:ee03:93e4:3ef2]:123 Feb 24 16:17:12 localhost ntpd[1319]: 2001:638:502:137:21b:78ff:fe32:fe4c local addr 2003:f4:4bf5:7300:7897:fff:fefc:11b5 -> 2003:f4:4bf5:7300:18ca:ee03:93e4:3ef2 Feb 24 16:17:12 localhost ntpd[1319]: Soliciting pool server 37.58.57.238 Feb 24 16:17:13 localhost ntpd[1319]: Soliciting pool server 131.234.137.64 Feb 24 16:17:13 localhost ntpd[1319]: Soliciting pool server 136.243.177.133 Feb 24 16:17:13 localhost ntpd[1319]: Soliciting pool server 2a01:4f8:190:226e::1 Feb 24 16:17:13 localhost ntpd[1319]: Soliciting pool server 176.9.100.86 Feb 24 16:17:13 localhost ntpd[1319]: Soliciting pool server 138.201.64.208 Feb 24 16:48:12 localhost systemd[1]: Time has been changed Feb 24 16:48:12 localhost systemd[1]: apt-daily.timer: Adding 2min 40.369986s random time. Feb 24 16:48:12 localhost ntpd[1319]: receive: Unexpected origin timestamp 0xe01d33fc.bb8e989b does not match aorg 0000000000.00000000 from server@213.203.202.38 xmt 0xe01d3b3c.002fc159 Feb 24 16:48:12 localhost systemd[1]: apt-daily-upgrade.timer: Adding 50min 6.272109s random time. Feb 24 16:48:12 localhost ntpd[1319]: receive: Unexpected origin timestamp 0xe01d33fc.b98a3016 does not match aorg 0000000000.00000000 from server@176.9.100.86 xmt 0xe01d3b3b.fe8900a0 Feb 24 16:48:12 localhost ntpd[1319]: receive: Unexpected origin timestamp 0xe01d33fc.bb8b71c3 does not match aorg 0000000000.00000000 from server@2a01:238:43f2:8900:dd04:e3a0:ee11:a73d xmt 0xe01d3b3c.00db55a3 Feb 24 16:48:12 localhost ntpd[1319]: receive: Unexpected origin timestamp 0xe01d33fc.bb87b14c does not match aorg 0000000000.00000000 from server@37.58.57.238 xmt 0xe01d3b3c.0091a2c0 Feb 24 16:48:56 localhost CRON[1870]: (root) CMD (/root/get_cputemp.sh) Feb 24 16:48:56 localhost CRON[1869]: (CRON) info (No MTA installed, discarding output) Feb 24 16:50:01 localhost CRON[1951]: (root) CMD (/root/backup_vis_json.sh) Feb 24 16:50:01 localhost CRON[1952]: (root) CMD (/root/get_cputemp.sh) Feb 24 16:50:01 localhost CRON[1953]: (root) CMD (/root/moritz_anwesenheit.php) Feb 24 16:50:01 localhost CRON[1950]: (CRON) info (No MTA installed, discarding output) Feb 24 16:50:02 localhost CRON[1948]: (CRON) info (No MTA installed, discarding output) Feb 24 16:50:02 localhost CRON[1949]: (CRON) info (No MTA installed, discarding output) Feb 24 16:52:01 localhost CRON[2095]: (root) CMD (/root/get_cputemp.sh) Feb 24 16:52:02 localhost CRON[2094]: (CRON) info (No MTA installed, discarding output) Feb 24 16:54:01 localhost CRON[2198]: (root) CMD (/root/get_cputemp.sh) Feb 24 16:54:01 localhost CRON[2197]: (CRON) info (No MTA installed, discarding output) Feb 24 16:55:01 localhost CRON[2214]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Feb 24 16:56:01 localhost CRON[2225]: (root) CMD (/root/get_cputemp.sh) Feb 24 16:56:01 localhost CRON[2224]: (CRON) info (No MTA installed, discarding output) Feb 24 16:58:01 localhost CRON[2269]: (root) CMD (/root/get_cputemp.sh) Feb 24 16:58:01 localhost CRON[2268]: (CRON) info (No MTA installed, discarding output) Feb 24 16:58:21 localhost ntpd[1319]: 2a01:4f8:190:226e::1 local addr 2003:f4:4bf5:7300:18ca:ee03:93e4:3ef2 -> <null> Feb 24 16:58:21 localhost ntpd[1319]: 2001:638:502:137:21b:78ff:fe32:fe4c local addr 2003:f4:4bf5:7300:18ca:ee03:93e4:3ef2 -> <null> Feb 24 16:59:26 localhost ntpd[1319]: 131.234.137.64 local addr 192.168.111.176 -> <null> Feb 24 17:00:01 localhost CRON[2305]: (root) CMD (/root/get_cputemp.sh) Feb 24 17:00:01 localhost CRON[2307]: (root) CMD (/root/backup_vis_json.sh) Feb 24 17:00:01 localhost CRON[2306]: (root) CMD (/root/moritz_anwesenheit.php) Feb 24 17:00:01 localhost CRON[2311]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Feb 24 17:00:01 localhost CRON[2304]: (CRON) info (No MTA installed, discarding output) Feb 24 17:00:01 localhost CRON[2302]: (CRON) info (No MTA installed, discarding output) Feb 24 17:00:02 localhost CRON[2303]: (CRON) info (No MTA installed, discarding output) Feb 24 17:00:41 localhost ntpd[1319]: 131.234.137.63 local addr 192.168.111.176 -> <null> Feb 24 17:02:01 localhost CRON[2368]: (root) CMD (/root/get_cputemp.sh) Feb 24 17:02:01 localhost CRON[2367]: (CRON) info (No MTA installed, discarding output) Feb 24 17:02:50 localhost ntpd[1319]: 138.201.64.208 local addr 192.168.111.176 -> <null> Feb 24 17:02:51 localhost ntpd[1319]: 136.243.177.133 local addr 192.168.111.176 -> <null> Feb 24 17:02:53 localhost ntpd[1319]: 176.9.100.86 local addr 192.168.111.176 -> <null> Feb 24 17:03:36 localhost systemd[1]: Starting Cleanup of Temporary Directories... Feb 24 17:03:36 localhost systemd[1]: Started Cleanup of Temporary Directories. Feb 24 17:04:01 localhost CRON[2388]: (root) CMD (/root/get_cputemp.sh) Feb 24 17:04:01 localhost CRON[2387]: (CRON) info (No MTA installed, discarding output) Feb 24 17:04:08 localhost ntpd[1319]: 195.201.19.162 local addr 192.168.111.176 -> <null> Feb 24 17:04:29 localhost ntpd[1319]: 193.141.27.1 local addr 192.168.111.176 -> <null> Feb 24 17:04:39 localhost ntpd[1319]: 144.76.60.190 local addr 192.168.111.176 -> <null> Feb 24 17:05:01 localhost CRON[2403]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Feb 24 17:05:07 localhost ntpd[1319]: 37.58.57.238 local addr 192.168.111.176 -> <null>Gruss Ralf
-
@derrapf sagte in IOBroker hat sich beendet:
Iobroker status lieferte jedenfalls, dass er nicht läuft
Je nachdem von wann deine Installation ist musst du das abfragen mit
sudo systemctl iobroker statusDie übliche frage, auch beim Rock64
Ist dein netzteil stark genug? -
@Homoran Hallo Rainer
Also das Kommando sudo systemctl iobroker status liefert bei mirroot@ioBroker-Rock64:~# sudo systemctl iobroker status Unknown operation iobroker.Das Netzteil hat 3A
Gruss Ralf
-
Warum setzt Du ein `sudo´ vor Deinen Befehl wenn Du eh schon als root angemeldet bist?
Du solltest Dich mit Linux beschäftigen und Dich einlesen...
-
@derrapf
Hi,kann es sein das dein Gerät da neu gestartet ist?
Schau mal die uptime an, dann siehst du das sofort.uptime 09:17:07 up 18 days, 10:09, 1 user, load average: 0,24, 0,27, 0,21 -
@Homoran sagte in IOBroker hat sich beendet:
@derrapf sagte in IOBroker hat sich beendet:
Iobroker status lieferte jedenfalls, dass er nicht läuft
Je nachdem von wann deine Installation ist musst du das abfragen mit
sudo systemctl iobroker statusDie übliche frage, auch beim Rock64
Ist dein netzteil stark genug?Das geht aber nur mit neuen Installationen, oder?
Wenn ioBroker noch "klassisch" läuft, dann ist die Ausgabesystemctl iobroker status Unknown operation iobroker. -
@sissiwup
Yepp,
Deswegen auch die Frage nach der art der Installation -
Welches System ist denn da auf dem Rock?
Lass mal das systemctl weg und nimm nur den Befehl:
iobroker statusMein Rock mag das nämlich auch nicht...
root@rockpro64 ~ > systemctl iobroker status Unknown operation iobroker. root@rockpro64 ~ > iobroker status iobroker is running -
@Yetiberg
Und in ganz alten Installationen muss das auch noch in /opt/iobroker ausgeführt werden -
Allgemein:
ps -ef | grep -E 'iobroker\.|io\.'Listet dann alle Instanzen, wichtig ist der js-controller läuft.
root 8826 1 1 04:11 ? 00:05:19 iobroker.js-controller root 8844 8826 0 04:11 ? 00:00:07 io.admin.0 root 8866 8826 0 04:11 ? 00:00:07 io.web.0 root 8918 8826 0 04:11 ? 00:00:34 io.hm-rpc.0 root 8933 8826 0 04:11 ? 00:00:12 io.hm-rega.0 root 8960 8826 0 04:11 ? 00:00:25 io.hm-rpc.1 root 9022 8826 0 04:12 ? 00:01:37 io.javascript.0 root 9056 8826 0 04:12 ? 00:00:18 io.ping.0 root 9120 8826 0 04:12 ? 00:02:30 io.sql.0 root 9145 8826 0 04:12 ? 00:00:04 io.geofency.0 root 9165 8826 0 04:12 ? 00:00:06 io.tankerkoenig.0 root 9192 8826 0 04:12 ? 00:00:04 io.pushover.0 root 9230 8826 0 04:13 ? 00:00:06 io.cloud.0 root 9246 8826 0 04:13 ? 00:00:06 io.fritzbox.0 root 9261 8826 0 04:13 ? 00:00:06 io.broadlink2.0 root 9284 8826 0 04:13 ? 00:00:04 io.scenes.0 root 9303 8826 0 04:13 ? 00:00:04 io.simple-api.0 root 9345 8826 0 04:13 ? 00:00:04 io.backitup.0 root 9369 8826 0 04:13 ? 00:00:05 io.alexa2.0 root 9387 8826 0 04:13 ? 00:00:07 io.amazon-dash.0 root 9413 8826 0 04:13 ? 00:01:45 io.mqtt.0 root 9484 8826 0 04:13 ? 00:00:46 io.tr-064.0 root 9512 8826 0 04:13 ? 00:00:30 io.hm-rpc.2 root 9530 8826 0 04:13 ? 00:00:11 io.yahka.0 -
Hallo alle
Also zu den Fragen:
Die Iobroker Installation ist die von Rainer Rock64 Image. Die hab ich nicht selber gemacht. Keine Ahnung ob die nach der "neuen Art" aufgesetzt wurde oder nichtWarum setzt Du ein `sudo´ vor Deinen Befehl wenn Du eh schon als root angemeldet bist?
Du solltest Dich mit Linux beschäftigen und Dich einlesen...Ich habe den String von Rainer einfach kopiert. Der Hinweis mich einzulesen ist leider nicht zielführend. Ob ich jetzt root bin und einen Befehl nochmal extra mit Root Rechten ausführe oder nicht sollte Wurst sein. Wenn es einen Unterschied gibt, dann bitte ich Dich den mir zu erklären. Wie auch immer ob mit oder ohne sudo: Das Ergebnis ist das Gleiche.
kann es sein das dein Gerät da neu gestartet ist?
Ich habe eben grad wieder den Effekt gehabt. Es sieht so aus als ob alles laufen würde bis auf den js-controller.
Uptime liefert 19hroot@ioBroker-Rock64:~# iobroker status iobroker is not running root@ioBroker-Rock64:~# ps -e | grep io 11 ? 00:00:00 migration/0 14 ? 00:00:00 migration/1 19 ? 00:00:00 migration/2 24 ? 00:00:00 migration/3 44 ? 00:00:00 rpciod 46 ? 00:00:00 xprtiod 73 ? 00:00:00 nfsiod 11787 ? 00:11:40 io.javascript.0 11797 ? 00:02:34 io.socketio.0 11819 ? 00:02:35 io.text2command 11829 ? 00:02:35 io.sayit.0 11912 ? 00:03:12 io.admin.0 11928 ? 00:02:48 io.web.0 11943 ? 00:02:41 io.fritzbox.0 11953 ? 00:02:41 io.history.0 11997 ? 00:02:32 io.simple-api.0 12021 ? 00:07:14 io.hm-rpc.0 12031 ? 00:13:18 io.hm-rpc.1 12041 ? 00:02:34 io.samsung.0 12051 ? 00:20:38 io.hm-rega.0 12062 ? 00:02:51 io.cloud.0 12073 ? 00:03:08 io.alexa2.0 12087 ? 00:02:54 io.iot.0 12093 ? 00:02:34 io.scenes.0 12107 ? 00:03:01 io.hm-rpc.2 12125 ? 00:02:36 io.shelly.0 14608 ? 00:03:10 io.telegram.0 root@ioBroker-Rock64:~# sudo systemctl iobroker status Unknown operation iobroker. root@ioBroker-Rock64:~# systemctl iobroker status Unknown operation iobroker. root@ioBroker-Rock64:~# uptime 19:39:53 up 1 day, 2:52, 1 user, load average: 0,20, 0,12, 0,09 root@ioBroker-Rock64:~#Also nein, der Rock64 scheint nicht neu gestartet zu sein.
Wie man oben sieht liefert iobroker status "iobroker is not running"
Der Befehl ps -ef | grep -E 'iobroker.|io.' liefertroot@ioBroker-Rock64:~# ps -ef | grep -E 'iobroker\.|io\.' root 11787 1 1 02:15 ? 00:11:49 io.javascript.0 root 11797 1 0 02:15 ? 00:02:36 io.socketio.0 root 11819 1 0 02:15 ? 00:02:37 io.text2command.0 root 11829 1 0 02:15 ? 00:02:37 io.sayit.0 root 11912 1 0 02:15 ? 00:03:15 io.admin.0 root 11928 1 0 02:15 ? 00:02:50 io.web.0 root 11943 1 0 02:15 ? 00:02:42 io.fritzbox.0 root 11953 1 0 02:16 ? 00:02:44 io.history.0 root 11997 1 0 02:16 ? 00:02:34 io.simple-api.0 root 12021 1 0 02:16 ? 00:07:20 io.hm-rpc.0 root 12031 1 1 02:16 ? 00:13:28 io.hm-rpc.1 root 12041 1 0 02:16 ? 00:02:36 io.samsung.0 root 12051 1 2 02:16 ? 00:21:11 io.hm-rega.0 root 12062 1 0 02:16 ? 00:02:53 io.cloud.0 root 12073 1 0 02:16 ? 00:03:10 io.alexa2.0 root 12087 1 0 02:16 ? 00:02:56 io.iot.0 root 12093 1 0 02:16 ? 00:02:36 io.scenes.0 root 12107 1 0 02:16 ? 00:03:03 io.hm-rpc.2 root 12125 1 0 02:17 ? 00:02:38 io.shelly.0 root 14608 1 0 05:04 ? 00:03:12 io.telegram.0 root 14795 14794 0 05:15 ? 00:01:59 node /opt/iobroker/node_modules/ iobroker.js-controller/iobroker.js backup root@ioBroker-Rock64:~#Auch hier der js-controller ist weg. Frage ist, ich wie finde ich raus warum?
Gruss Ralf
-
@derrapf sagte in IOBroker hat sich beendet:
von Rainer Rock64 Image
Wenn du jetzt noch sagst welches, kann ich das beantworten
-
Hallo Rainer
Äh das von der Iobroker.net Download Seite. Gibts da mehrere?Also das hier:
http://www.iobroker.net/docu/?page_id=2563&lang=deGruss Ralf
-
@derrapf
Netter link
das ist die ganze SeiteEtwas gefiltert sieht das so aus:
-
@Homoran
Ui, da sind ja jetzt ganz viele. Sorry. Als ich damals auf der Seite war gab es nur eines.
Ich habe das hier "ioBroker_Image_Rock64_20180419_stretch.img". Hilft Dir das?Ich habe jetzt mal den js-controller auf der Commandline gestartet
Da kommen viele Fehler.root@ioBroker-Rock64:/opt/iobroker# node node_modules/iobroker.js-controller/controlle r.js --logs 2019-02-25 19:55:43.332 - info: host.ioBroker-Rock64 iobroker.js-controller version 1 .4.2 js-controller starting 2019-02-25 19:55:43.342 - info: host.ioBroker-Rock64 Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker 2019-02-25 19:55:43.343 - info: host.ioBroker-Rock64 hostname: ioBroker-Rock64, node: v8.15.0 2019-02-25 19:55:43.350 - info: host.ioBroker-Rock64 ip addresses: 192.168.111.176 fd 13:235b:7090:0:4f6a:8f2e:213a:f7b7 2003:f4:4bc4:8200:b97a:5558:33ac:531c fd13:235b:709 0::cda fd13:235b:7090:0:7897:fff:fefc:11b5 fe80::7897:fff:fefc:11b5 2019-02-25 19:55:44.492 - info: host.ioBroker-Rock64 inMem-objects listening on port 9001 2019-02-25 19:55:44.666 - info: host.ioBroker-Rock64 States connected to redis: 127.0 .0.1:6379 2019-02-25 19:55:44.671 - info: host.ioBroker-Rock64 InMemoryDB connected 2019-02-25 19:55:44.767 - info: host.ioBroker-Rock64 57 instances found host.ioBroker-Rock64 check instance "system.adapter.admin.0" for host "ioBroker-Rock64 " host.ioBroker-Rock64 check instance "system.adapter.web.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.history.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.javascript.0" for host "ioBroker-R ock64" host.ioBroker-Rock64 check instance "system.adapter.socketio.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.mobile.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.vis-bars.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.vis-metro.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.vis-rgraph.0" for host "ioBroker-R ock64" host.ioBroker-Rock64 check instance "system.adapter.vis-plumb.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.vis-players.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-map.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.vis-keyboard.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-lcars.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.vis-justgage.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-hqwidgets.0" for host "ioBroke r-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-jqui-mfd.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-fancyswitch.0" for host "ioBro ker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-colorpicker.0" for host "ioBro ker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-canvas-gauges.0" for host "ioB roker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-google-fonts.0" for host "ioBr oker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.vis-history.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.ical.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.text2command.0" for host "ioBroker -Rock64" host.ioBroker-Rock64 check instance "system.adapter.sayit.0" for host "ioBroker-Rock64 " host.ioBroker-Rock64 check instance "system.adapter.owntracks.0" for host "ioBroker-Ro ck64" host.ioBroker-Rock64 check instance "system.adapter.js-controller.0" for host "ioBroke r-Rock64" host.ioBroker-Rock64 check instance "system.adapter.fritzbox.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.dwd.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.telegram.0" for host "ioBroker-Roc k64" host.ioBroker-Rock64 check instance "system.adapter.tvspielfilm.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.simple-api.0" for host "ioBroker-R ock64" host.ioBroker-Rock64 check instance "system.adapter.vis-timeandweather.0" for host "io Broker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.mqtt-client.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.hm-rpc.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.hm-rpc.1" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.samsung.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.hm-rega.0" for host "ioBroker-Rock 64" host.ioBroker-Rock64 check instance "system.adapter.cloud.0" for host "ioBroker-Rock64 " host.ioBroker-Rock64 check instance "system.adapter.alexa2.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.iot.0" for host "ioBroker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.scenes.0" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.hm-rpc.2" for host "ioBroker-Rock6 4" host.ioBroker-Rock64 check instance "system.adapter.amazon-dash.0" for host "ioBroker- Rock64" host.ioBroker-Rock64 check instance "system.adapter.weatherunderground.0" for host "io Broker-Rock64" host.ioBroker-Rock64 check instance "system.adapter.shelly.0" for host "ioBroker-Rock6 4" 2019-02-25 19:55:44.841 - info: host.ioBroker-Rock64 starting 26 instances 2019-02-25 19:55:44.903 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25475 2019-02-25 19:55:49.553 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25481 (node:25465) [DEP0013] DeprecationWarning: Calling an asynchronous function without callback is deprecated. 2019-02-25 19:55:51.231 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:55:51.232 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:55:53.226 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:55:53.227 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:55:57.015 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25508 2019-02-25 19:56:02.547 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 25529 Cannot parse "/user/vis-views.json Send diag info: {"uuid":"aec67a1a-f2cf-7abe-98d8-845cd7e36d52","language":"de","country":"","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"linux"}],"node":"v8.15.0","arch":"arm64","adapters":{"admin":{"version":"3.5.10","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.9.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"2.3.0","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"},"vis":{"version":"1.1.8","platform":"Javascript/Node.js"},"history":{"version":"1.8.5","platform":"Javascript/Node.js"},"flot":{"version":"1.9.2","platform":"javascript/Node.js"},"javascript":{"version":"3.6.4","platform":"Javascript/Node.js"},"socketio":{"version":"2.1.1","platform":"Javascript/Node.js"},"mobile":{"version":"0.4.11","platform":"javascript/Node.js"},"vis-bars":{"version":"0.1.4","platform":"Javascript/Node.js"},"vis-metro":{"version":"1.1.2","platform":"Javascript/Node.js"},"vis-rgraph":{"version":"0.0.2","platform":"Javascript/Node.js"},"vis-plumb":{"version":"1.0.1","platform":"Javascript/Node.js"},"vis-players":{"version":"0.1.5","platform":"Javascript/Node.js"},"vis-map":{"version":"1.0.2","platform":"Javascript/Node.js"},"vis-keyboard":{"version":"0.0.2","platform":"Javascript/Node.js"},"vis-lcars":{"version":"1.0.4","platform":"Javascript/Node.js"},"vis-justgage":{"version":"1.0.0","platform":"Javascript/Node.js"},"vis-hqwidgets":{"version":"1.1.2","platform":"Javascript/Node.js"},"vis-jqui-mfd":{"version":"1.0.12","platform":"Javascript/Node.js"},"vis-fancyswitch":{"version":"1.1.0","platform":"Javascript/Node.js"},"vis-colorpicker":{"version":"1.1.1","platform":"Javascript/Node.js"},"vis-canvas-gauges":{"version":"0.1.5","platform":"Javascript/Node.js"},"vis-google-fonts":{"version":"0.1.0","platform":"Javascript/Node.js"},"vis-history":{"version":"0.2.7","platform":"Javascript/Node.js"},"icons-addictive-flavour-png":{"version":"0.1.0","platform":"javascript/Node.js"},"icons-icons8":{"version":"0.0.1","platform":"javascript/Node.js"},"icons-material-png":{"version":"0.1.0","platform":"javascript/Node.js"},"icons-material-svg":{"version":"0.1.0","platform":"javascript/Node.js"},"icons-mfd-png":{"version":"1.0.2","platform":"javascript/Node.js"},"icons-mfd-svg":{"version":"1.0.2","platform":"javascript/Node.js"},"icons-open-icon-library-png":{"version":"0.1.3","platform":"javascript/Node.js"},"icons-ultimate-png":{"version":"1.0.1","platform":"javascript/Node.js"},"ical":{"version":"1.7.0","platform":"Javascript/Node.js"},"text2command":{"version":"1.2.4","platform":"Javascript/Node.js"},"sayit":{"version":"1.7.0","platform":"Javascript/Node.js"},"owntracks":{"version":"0.5.0","platform":"Javascript/Node.js"},"js-controller":{"version":"1.4.2","platform":"Javascript/Node.js"},"fritzbox":{"version":"0.2.1","platform":"Javascript/Node.js"},"dwd":{"version":"2.4.3","platform":"javascript/Node.js"},"telegram":{"version":"1.3.6","platform":"Javascript/Node.js"},"tvspielfilm":{"version":"1.0.4","platform":"javascript/Node.js"},"simple-api":{"version":"2.0.0","platform":"Javascript/Node.js"},"vis-timeandweather":{"version":"1.1.7","platform":"Javascript/Node.js"},"cloud":{"version":"2.6.2","platform":"Javascript/Node.js"},"mqtt-client":{"version":"1.1.1","platform":"Javascript/Node.js"},"rickshaw":{"version":"1.0.0","platform":"javascript/Node.js"},"samsung":{"version":"0.2.9","platform":"Javascript/Node.js"},"alexa2":{"version":"1.1.3","platform":"Javascript/Node.js"},"iot":{"version":"0.2.2","platform":"Javascript/Node.js"},"scenes":{"version":"1.1.0","platform":"Javascript/Node.js"},"amazon-dash":{"version":"0.3.1","platform":"Javascript/Node.js"},"weatherunderground":{"version":"2.0.4","platform":"Javascript/Node.js"},"shelly":{"version":"2.0.8","platform":"Javascript/Node.js"},"plexconnect":{"version":"0.0.7","platform":"Javascript/Node.js"}},"model":"unknown","cpus":4,"mem":4196204544,"ostype":"Linux","city":"","vis":249} 2019-02-25 19:56:04.180 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:04.181 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled 2019-02-25 19:56:04.893 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25539 2019-02-25 19:56:05.870 - info: host.ioBroker-Rock64 instance system.adapter.vis.0 terminated while should be started once 2019-02-25 19:56:07.395 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:07.397 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:56:07.523 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:07.523 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:56:08.890 - info: host.ioBroker-Rock64 instance scheduled system.adapter.ical.0 0,30 * * * * 2019-02-25 19:56:08.924 - info: host.ioBroker-Rock64 instance system.adapter.ical.0 started with pid 25553 2019-02-25 19:56:12.886 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 25563 2019-02-25 19:56:14.378 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:14.379 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:56:16.885 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 25573 2019-02-25 19:56:18.485 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:18.486 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:56:20.851 - error: host.ioBroker-Rock64 startInstance js-controller.0: cannot find start file! 2019-02-25 19:56:21.265 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25587 2019-02-25 19:56:23.265 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25593 2019-02-25 19:56:24.888 - info: host.ioBroker-Rock64 instance system.adapter.fritzbox.0 started with pid 25603 2019-02-25 19:56:25.005 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:25.006 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:56:25.845 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:25.846 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:56:26.451 - info: host.ioBroker-Rock64 instance system.adapter.ical.0 terminated with code 0 (OK) TypeError: Cannot read property 'debug' of undefined at Adapter.<anonymous> (/opt/iobroker/node_modules/iobroker.fritzbox/main.js:130:17) at emitOne (events.js:116:13) at Adapter.emit (events.js:211:7) at process.stop (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5033:18) at Object.onceWrapper (events.js:315:30) at emitOne (events.js:116:13) at process.emit (events.js:211:7) at process.exit (internal/process.js:146:15) at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:780:25 at Command.callback (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:236:17) 2019-02-25 19:56:28.857 - info: host.ioBroker-Rock64 instance scheduled system.adapter.dwd.0 3 * * * * 2019-02-25 19:56:28.905 - info: host.ioBroker-Rock64 instance system.adapter.dwd.0 started with pid 25617 2019-02-25 19:56:32.476 - info: host.ioBroker-Rock64 instance system.adapter.dwd.0 terminated with code 0 (OK) 2019-02-25 19:56:32.880 - info: host.ioBroker-Rock64 instance system.adapter.telegram.0 started with pid 25627 2019-02-25 19:56:34.218 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25633 2019-02-25 19:56:35.925 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:35.926 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled Mon, 25 Feb 2019 18:56:36 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See Link Removed. at module.js:653:30 2019-02-25 19:56:36.860 - info: host.ioBroker-Rock64 instance scheduled system.adapter.tvspielfilm.0 */5 * * * * 2019-02-25 19:56:36.895 - info: host.ioBroker-Rock64 instance system.adapter.tvspielfilm.0 started with pid 25643 2019-02-25 19:56:37.115 - error: Caught by controller[0]: Mon, 25 Feb 2019 18:56:36 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. 2019-02-25 19:56:37.116 - error: Caught by controller[0]: In the future, you will have to enable it yourself. 2019-02-25 19:56:37.117 - error: Caught by controller[0]: See Link Removed. at module.js:653:30 2019-02-25 19:56:37.118 - error: host.ioBroker-Rock64 instance system.adapter.telegram.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:37.120 - info: host.ioBroker-Rock64 Restart adapter system.adapter.telegram.0 because enabled 2019-02-25 19:56:37.432 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25653 2019-02-25 19:56:37.564 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 25659 2019-02-25 19:56:38.163 - info: host.ioBroker-Rock64 instance system.adapter.telegram.0 started with pid 25665 2019-02-25 19:56:39.910 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:39.912 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:56:40.894 - info: host.ioBroker-Rock64 instance system.adapter.simple-api.0 started with pid 25679 Mon, 25 Feb 2019 18:56:42 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See Link Removed. at module.js:653:30 2019-02-25 19:56:42.625 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:42.626 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:56:43.013 - error: host.ioBroker-Rock64 instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:43.014 - info: host.ioBroker-Rock64 Restart adapter system.adapter.simple-api.0 because enabled 2019-02-25 19:56:44.412 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 25697 2019-02-25 19:56:44.887 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 started with pid 25703 2019-02-25 19:56:46.073 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:46.074 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:56:46.651 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:46.652 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-25 19:56:48.518 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 25717 2019-02-25 19:56:48.884 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 started with pid 25723 2019-02-25 19:56:50.138 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:50.139 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:56:50.573 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running) 2019-02-25 19:56:50.574 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.1 because enabled 2019-02-25 19:56:52.884 - info: host.ioBroker-Rock64 instance system.adapter.samsung.0 started with pid 25737 2019-02-25 19:56:54.545 - error: host.ioBroker-Rock64 instance system.adapter.samsung.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:54.546 - info: host.ioBroker-Rock64 Restart adapter system.adapter.samsung.0 because enabled 2019-02-25 19:56:55.039 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25747 2019-02-25 19:56:55.882 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25753 2019-02-25 19:56:56.902 - info: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 started with pid 25759 2019-02-25 19:56:58.354 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:58.355 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:56:58.567 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:58.568 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:56:59.858 - error: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running) 2019-02-25 19:56:59.859 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rega.0 because enabled 2019-02-25 19:57:00.875 - info: host.ioBroker-Rock64 instance system.adapter.cloud.0 started with pid 25777 2019-02-25 19:57:03.241 - error: host.ioBroker-Rock64 instance system.adapter.cloud.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:03.242 - info: host.ioBroker-Rock64 Restart adapter system.adapter.cloud.0 because enabled 2019-02-25 19:57:04.873 - info: host.ioBroker-Rock64 instance system.adapter.alexa2.0 started with pid 25787 2019-02-25 19:57:05.952 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25793 2019-02-25 19:57:06.720 - error: host.ioBroker-Rock64 instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:06.721 - info: host.ioBroker-Rock64 Restart adapter system.adapter.alexa2.0 because enabled 2019-02-25 19:57:07.486 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:07.487 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled 2019-02-25 19:57:08.873 - info: host.ioBroker-Rock64 instance system.adapter.iot.0 started with pid 25807 2019-02-25 19:57:09.937 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25813 2019-02-25 19:57:11.972 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:11.973 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:57:12.264 - error: host.ioBroker-Rock64 instance system.adapter.iot.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:12.265 - info: host.ioBroker-Rock64 Restart adapter system.adapter.iot.0 because enabled 2019-02-25 19:57:12.647 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 25827 2019-02-25 19:57:12.874 - info: host.ioBroker-Rock64 instance system.adapter.scenes.0 started with pid 25833 2019-02-25 19:57:13.042 - info: host.ioBroker-Rock64 instance system.adapter.simple-api.0 started with pid 25839 2019-02-25 19:57:14.840 - error: host.ioBroker-Rock64 instance system.adapter.scenes.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:14.841 - info: host.ioBroker-Rock64 Restart adapter system.adapter.scenes.0 because enabled 2019-02-25 19:57:14.913 - error: host.ioBroker-Rock64 instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:14.914 - info: host.ioBroker-Rock64 Restart adapter system.adapter.simple-api.0 because enabled 2019-02-25 19:57:16.099 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 25853 2019-02-25 19:57:16.678 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 started with pid 25859 2019-02-25 19:57:16.851 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:16.853 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:57:16.879 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 started with pid 25869 2019-02-25 19:57:17.926 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:17.928 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:57:18.584 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:18.585 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-25 19:57:18.738 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 terminated with code 7 (Adapter already running) 2019-02-25 19:57:18.739 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.2 because enabled 2019-02-25 19:57:20.161 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 25887 2019-02-25 19:57:20.598 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 started with pid 25893 2019-02-25 19:57:20.864 - info: host.ioBroker-Rock64 instance scheduled system.adapter.weatherunderground.0 12 * * * * 2019-02-25 19:57:21.772 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:21.773 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:57:22.301 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running) 2019-02-25 19:57:22.302 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.1 because enabled 2019-02-25 19:57:24.568 - info: host.ioBroker-Rock64 instance system.adapter.samsung.0 started with pid 25907 2019-02-25 19:57:24.874 - info: host.ioBroker-Rock64 instance system.adapter.shelly.0 started with pid 25913 2019-02-25 19:57:26.261 - error: host.ioBroker-Rock64 instance system.adapter.samsung.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:26.262 - info: host.ioBroker-Rock64 Restart adapter system.adapter.samsung.0 because enabled 2019-02-25 19:57:26.848 - error: host.ioBroker-Rock64 instance system.adapter.shelly.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:26.849 - info: host.ioBroker-Rock64 Restart adapter system.adapter.shelly.0 because enabled 2019-02-25 19:57:28.377 - info: host.ioBroker-Rock64 instance system.adapter.web.0 started with pid 25931 2019-02-25 19:57:28.592 - info: host.ioBroker-Rock64 instance system.adapter.admin.0 started with pid 25937 2019-02-25 19:57:29.886 - info: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 started with pid 25943 2019-02-25 19:57:30.776 - error: host.ioBroker-Rock64 instance system.adapter.web.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:30.777 - info: host.ioBroker-Rock64 Restart adapter system.adapter.web.0 because enabled 2019-02-25 19:57:32.099 - error: host.ioBroker-Rock64 instance system.adapter.admin.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:32.103 - info: host.ioBroker-Rock64 Restart adapter system.adapter.admin.0 because enabled 2019-02-25 19:57:32.480 - error: host.ioBroker-Rock64 instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:32.481 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rega.0 because enabled 2019-02-25 19:57:33.264 - info: host.ioBroker-Rock64 instance system.adapter.cloud.0 started with pid 25961 2019-02-25 19:57:35.456 - error: host.ioBroker-Rock64 instance system.adapter.cloud.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:35.457 - info: host.ioBroker-Rock64 Restart adapter system.adapter.cloud.0 because enabled 2019-02-25 19:57:36.746 - info: host.ioBroker-Rock64 instance system.adapter.alexa2.0 started with pid 25971 2019-02-25 19:57:37.512 - info: host.ioBroker-Rock64 instance system.adapter.history.0 started with pid 25977 2019-02-25 19:57:38.516 - error: host.ioBroker-Rock64 instance system.adapter.alexa2.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:38.517 - info: host.ioBroker-Rock64 Restart adapter system.adapter.alexa2.0 because enabled 2019-02-25 19:57:39.076 - error: host.ioBroker-Rock64 instance system.adapter.history.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:39.077 - info: host.ioBroker-Rock64 Restart adapter system.adapter.history.0 because enabled 2019-02-25 19:57:40.789 - info: host.ioBroker-Rock64 instance system.adapter.tvspielfilm.0 terminated with code 0 (OK) 2019-02-25 19:57:42.008 - info: host.ioBroker-Rock64 instance system.adapter.socketio.0 started with pid 25991 2019-02-25 19:57:42.289 - info: host.ioBroker-Rock64 instance system.adapter.iot.0 started with pid 25997 2019-02-25 19:57:44.134 - error: host.ioBroker-Rock64 instance system.adapter.socketio.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:44.135 - info: host.ioBroker-Rock64 Restart adapter system.adapter.socketio.0 because enabled 2019-02-25 19:57:44.869 - info: host.ioBroker-Rock64 instance system.adapter.scenes.0 started with pid 26007 2019-02-25 19:57:44.939 - info: host.ioBroker-Rock64 instance system.adapter.simple-api.0 started with pid 26013 2019-02-25 19:57:45.272 - error: host.ioBroker-Rock64 instance system.adapter.iot.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:45.274 - info: host.ioBroker-Rock64 Restart adapter system.adapter.iot.0 because enabled 2019-02-25 19:57:46.560 - error: host.ioBroker-Rock64 instance system.adapter.scenes.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:46.561 - info: host.ioBroker-Rock64 Restart adapter system.adapter.scenes.0 because enabled 2019-02-25 19:57:46.601 - error: host.ioBroker-Rock64 instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:46.602 - info: host.ioBroker-Rock64 Restart adapter system.adapter.simple-api.0 because enabled 2019-02-25 19:57:46.874 - info: host.ioBroker-Rock64 instance system.adapter.javascript.0 started with pid 26031 2019-02-25 19:57:47.951 - info: host.ioBroker-Rock64 instance system.adapter.text2command.0 started with pid 26037 2019-02-25 19:57:48.613 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 started with pid 26043 2019-02-25 19:57:48.768 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 started with pid 26049 2019-02-25 19:57:49.860 - error: host.ioBroker-Rock64 instance system.adapter.text2command.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:49.862 - info: host.ioBroker-Rock64 Restart adapter system.adapter.text2command.0 because enabled 2019-02-25 19:57:50.670 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:50.671 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.0 because enabled 2019-02-25 19:57:50.831 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.2 terminated with code 7 (Adapter already running) 2019-02-25 19:57:50.832 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.2 because enabled 2019-02-25 19:57:51.166 - error: host.ioBroker-Rock64 instance system.adapter.javascript.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:51.166 - info: host.ioBroker-Rock64 Restart adapter system.adapter.javascript.0 because enabled 2019-02-25 19:57:51.795 - info: host.ioBroker-Rock64 instance system.adapter.sayit.0 started with pid 26071 2019-02-25 19:57:52.326 - info: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 started with pid 26077 2019-02-25 19:57:53.366 - error: host.ioBroker-Rock64 instance system.adapter.sayit.0 terminated with code 7 (Adapter already running) 2019-02-25 19:57:53.367 - info: host.ioBroker-Rock64 Restart adapter system.adapter.sayit.0 because enabled 2019-02-25 19:57:53.975 - error: host.ioBroker-Rock64 instance system.adapter.hm-rpc.1 terminated with code 7 (Adapter already running) 2019-02-25 19:57:53.976 - info: host.ioBroker-Rock64 Restart adapter system.adapter.hm-rpc.1 because enabled 2019-02-25 19:57:56.296 - info: host.ioBroker-Rock64 instance system.adapter.samsung.0 started with pid 26091Und dann geht es ewig so weiter.
Dass das VIS Json nicht parsebar ist muss ich noch getrennt untersuchen. VIS läuf eigentlich.
Gruss Ralf
-
@derrapf sagte in IOBroker hat sich beendet:
Ich habe das hier "ioBroker_Image_Rock64_20180419_stretch.img". Hilft Dir das?
Naja, zumindest für die Frage wie zu stoppen/nach dem Status zu fragen ist.
Da geht es immer noch mit (sudo) iobroker status
kann aber da noch gewesen sein, dass das im Veruzeichnis /opt/iobroker ausgeführt werden mussABER:
Das ist ein so genannter "nightly build". Da sind eventuell Features drin, die noch nicht unbedingt stable sein müssen. -
@derrapf
Wo kommen denn diese "created this issue" unter "Gruss Ralf" her? Die hab ich nicht getippt... -
Das Image hat jetzt wochenlang super funktioniert.
Also an Deinem Image kann es nicht gelegen haben.Was ich gemacht habe war:
Ich habe ein paar Scripte zum loggen von offenen Fenstern, Licht und zum Sammeln der IObroker Logs für VIS hinzugefügt. Speziell das Sammeln der IOBroker Logs für VIS hat den javascript Adapter auf 100% CPU gebracht. Deshalb hab ich das wieder disabled.
Ich schmeiss die jetzt alle wieder weg,Ansonsten habe ich hm-rega und alexa.2 upgedatet. Der Absturz vom js-controller ist aber schon vor dem alexa.2 Update passiert.
Beide Adapter haben Probleme beim Update gemacht. Man musste in beiden Adaptern die Dateien in den .../node_modules/.bin Verzeichnissen wegmoven, dann updaten und dann wieder zurückspielen. Ansonsten gab es jedes Mal Fehler vom npn, dass er auf die Dateien nicht zugreifen kann. Neue wurden aber auch nicht installiert. Also hab ich die Alten wieder zurück gemoved.
Gruss Ralf -
@derrapf
Das ist ein Forum-Feature, wo Infos aus einem Beitrag, die nach GitHub-Referenzen aussehen, entsprechende Infoblöcke unter dem Beitrag auslösen.Da braucht es ggf. noch Finetuning.
-
@Stabilostick sagte in IOBroker hat sich beendet:
@derrapf
Das ist ein Forum-Feature, wo Infos aus einem Beitrag, die nach GitHub-Referenzen aussehen, entsprechende Infoblöcke unter dem Beitrag auslösen.Da braucht es ggf. noch Finetuning.
Ah Ok, Ich dachte schon ich seh Gespenster.
