NEWS
Test js-controller v2.0.x (GitHub)
-
file/file - die Umstellung auf redis wollte ich schon länger mal angehen, aber jetzt erst mal das Testen mit dem neuen Controller :)
Auch läuft der iobroker-master noch unter Node 8, da im latest des Docker-Containers eben diese noch die aktuellste ist.In den Syslogs von gestern 18:00 ist mir nichts aufgefallen.
Heute Morgen, wir haben einen Bewegungsmelder im Flur, durch den immer schnell auffällt ob der ioBroker sauber läuft, blieb es dunkel. Um 23 Uhr ging das Licht im Flur noch an. Den Grund dafür hab ich auch direkt gefunden, die Variable Tageszeit (wird immer beim Wechsel einer Tageszeit aktualisiert) wurde nicht aktualisiert (d.h. das Skript lief wohl nicht zu diesem Zeitpunkt):
2019-10-01 05:26:49.287 - [32minfo[39m: javascript.0 (442) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur erkannt: Aktuelle Tageszeit: Nachmittag | Skript wird ausgelöst bei: Abend,Abenddämmerung,Nacht,MorgendämmerungDes weiteren ist mir aufgefallen das um 2:33 alle Prozesse neu gestartet wurden
┬─[root@iobroker-master:/opt/iobroker]─[05:30:59] ╰─># ps -ef | grep ^io iobroker 321 32704 5 02:33 ? 00:09:12 io.sql.0 iobroker 338 32704 0 02:33 ? 00:00:10 io.hm-rpc.1 iobroker 358 32704 0 02:33 ? 00:00:34 io.hm-rpc.2 iobroker 375 32704 0 02:33 ? 00:00:25 io.hm-rega.0 iobroker 442 32704 10 02:34 ? 00:18:34 io.javascript.0 iobroker 458 32704 5 02:34 ? 00:10:02 io.javascript.1 iobroker 475 32704 0 02:34 ? 00:00:07 io.simple-api.0 iobroker 580 32704 0 02:34 ? 00:01:21 io.stiebel-isg.0 iobroker 597 32704 0 02:34 ? 00:00:10 io.backitup.0 iobroker 616 32704 9 02:34 ? 00:16:16 io.unifi.0 iobroker 632 32704 0 02:34 ? 00:00:07 io.fritzbox.0 iobroker 667 32704 5 02:35 ? 00:10:08 io.javascript.2 iobroker 691 32704 0 02:35 ? 00:00:45 io.synology.0 iobroker 791 32704 0 02:35 ? 00:00:07 io.text2command.0 iobroker 808 32704 1 02:35 ? 00:02:32 io.info.0 iobroker 820 32704 0 02:35 ? 00:00:37 io.tr-064-community.0 iobroker 1103 32704 4 02:35 ? 00:07:52 io.moma.0 iobroker 1125 32704 1 02:35 ? 00:02:24 io.pi-hole.0 iobroker 1393 32704 0 02:35 ? 00:00:16 io.hs100.0 iobroker 1531 32704 0 02:36 ? 00:00:12 io.linkeddevices.0 iobroker 1726 32704 0 02:36 ? 00:00:14 io.bring.0 iobroker 1917 32704 2 02:36 ? 00:04:58 io.mercedesme.0 iobroker 2148 32704 0 02:36 ? 00:00:07 io.countdown.0 iobroker 30821 32704 0 05:04 ? 00:00:03 io.telegram.0 iobroker 32704 32703 31 02:33 ? 00:56:08 iobroker.js-controller iobroker 32721 32704 0 02:33 ? 00:00:27 io.admin.0 iobroker 32731 32704 0 02:33 ? 00:00:08 io.web.0 iobroker 32745 32704 0 02:33 ? 00:00:39 io.ping.0 iobroker 32755 32704 0 02:33 ? 00:00:56 io.hue.0 iobroker 32765 32704 0 02:33 ? 00:00:11 io.tankerkoenig.0Im Log hab ich dann im zweiten Anlauf das hier entdeckt (zweiter Anlauf da dies nur eine 'warn' Meldung ist, hab auf error gegreppt ... :)). Die InMemDB Meldungung mit dem unbekannten Skript hab ich auch gestern schonmal gesehen.
┬─[root@iobroker-master:/opt/iobroker]─[06:20:19] ╰─># cat /opt/iobroker/log/iobroker.2019-10-01.log | grep "2019-10-01 02" | grep warn 2019-10-01 02:33:29.177 - warn: host.iobroker-master Multihost discovery server: service started on 0.0.0.0:50005 2019-10-01 02:33:29.234 - warn: Error from InMemDB: Error: Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.239 - warn: Error from InMemDB: Error: Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868fAuf dem iobroker-hwr sagt er mir das alles Läuft, aber kein Prozess ist aktiv. Interessanterweise sagt auch der ioBroker.Admin das iobroker-hwr aktiv ist (= Grüner Status unter Hosts).
┬─[darkiop@iobroker-hwr:~]─[05:33:53] ╰─>$ iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: file States type: file ┬─[darkiop@iobroker-hwr:~]─[05:33:59] ╰─>$ ps -ef | grep ^ioVielleicht könnte man in einem Multihostbetrieb die Infos über alle eingebundenen Instanzen ausgeben?
Hier mal noch ein paar error-Fragmanente von Heute Nacht:
Um 0:02 meldete sich sql.0 auf dem iobroker-master:
2019-10-01 00:02:00.083 - info: javascript.0 (2012) script.js.PRODUKTIV.Beschattung.Automatik.01_Automatik: +++ Minuten vor Sonnenuntergang != VIS Parameter Minuten vor Sonnenuntergang | Es gibt noch nicht zu schalten +++ 2019-10-01 00:02:00.086 - info: javascript.0 (2012) script.js.PRODUKTIV.Beschattung.Automatik.04_Berechnung_Minuten_bis_zum_Schalten: Richtung Sonnenaufgang 2019-10-01 00:02:58.962 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:02:58.974 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:00.128 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:00.133 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:00.170 - info: javascript.0 (2012) script.js.PRODUKTIV.Beschattung.Automatik.01_Automatik: +++ Minuten vor Sonnenuntergang != VIS Parameter Minuten vor Sonnenuntergang | Es gibt noch nicht zu schalten +++ 2019-10-01 00:03:00.171 - info: javascript.0 (2012) script.js.PRODUKTIV.Beschattung.Automatik.04_Berechnung_Minuten_bis_zum_Schalten: Richtung Sonnenaufgang 2019-10-01 00:03:00.182 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:01.337 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:06.968 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:09.970 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:12.627 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:12.665 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:12.738 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:15.025 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:15.765 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:15.776 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:15.799 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:16.023 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:21.742 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:21.745 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:21.751 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:22.127 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:23.739 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:23.747 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:23.750 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:34.752 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:34.789 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:34.795 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:41.892 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:42.629 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:42.757 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:43.080 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:43.085 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:49.095 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:49.724 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:49.729 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:49.736 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:52.135 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:57.880 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:57.901 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:58.474 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:58.876 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:58.888 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:58.895 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0 2019-10-01 00:03:58.902 - error: sql.0 (1898) Error: Packets out of order. Got: 1 Expected: 0Um 2:05 das hier. Mit dem kann ich gerade gar nichts anfangen - aber um 2:05 läuft bei mir Synology Hyper Backup und sichert diverse Applikationen (DNS, HyperBackup, Oauth, ApplicationService, VPN). Hab das aber eben nochmal manuell angestoßen und keine Fehler bekommen.
2019-10-01 02:05:00.429 - error: host.iobroker-master Caught by controller[1]: (node:2012) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'enabled' of undefined 2019-10-01 02:05:00.430 - error: host.iobroker-master Caught by controller[2]: (node:2012) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1393) 2019-10-01 02:05:00.430 - error: host.iobroker-master Caught by controller[3]: (node:2012) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'enabled' of undefined 2019-10-01 02:05:00.431 - error: host.iobroker-master Caught by controller[3]: (node:2012) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1394) 2019-10-01 02:05:00.431 - error: host.iobroker-master instance system.adapter.javascript.0 terminated with code 156 (156) -
@apollon77 Sorry, viel Text heute Morgen - hier noch die Aktualisierung auf 2.0.16:
Alle Prozesse gestoppt, beide aktualisiert:
┬─[root@iobroker-master:/opt/iobroker]─[06:31:25] ╰─># sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller > iobroker.js-controller@2.0.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.4.1 > iobroker.js-controller@2.0.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/iobroker.pushbullet/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.0 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) + iobroker.js-controller@2.0.16 added 1 package from 3 contributors, removed 1 package, updated 8 packages and audited 40363 packages in 147.811s found 87 vulnerabilities (32 low, 10 moderate, 45 high) run `npm audit fix` to fix them, or `npm audit` for details┬─[darkiop@iobroker-hwr:/opt/iobroker]─[06:31:49] ╰─>$ sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller [sudo] Passwort für darkiop: > iobroker.js-controller@2.0.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.9.0 > iobroker.js-controller@2.0.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.0 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@2.0.16 removed 1 package, updated 8 packages and audited 1867 packages in 62.052s found 12 vulnerabilities (9 low, 3 high) run `npm audit fix` to fix them, or `npm audit` for detailsDann
- iobroker-master Container neu gestartet
- iobroker-hwr reboot
Nach reboot auf iobroker-hwr:
┬─[darkiop@iobroker-hwr:~]─[06:40:21] ╰─>$ iobroker status iobroker is not running on this host. At least one iobroker host is running. Objects type: file States type: file ┬─[darkiop@iobroker-hwr:~]─[06:40:26] ╰─>$ ps -ef | grep ^io ┬─[darkiop@iobroker-hwr:~]─[06:40:31] ╰─>$ tail -n 50 /opt/iobroker/log/iobroker.2019-10-01.log 2019-10-01 02:33:27.294 - warn: host.iobroker-hwr Slave controller detected disconnection. Stop all instances. 2019-10-01 02:33:27.301 - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.0 2019-10-01 02:33:27.302 - error: host.iobroker-hwr result is not defined 2019-10-01 02:33:29.315 - warn: host.iobroker-hwr Cannot get view: ReplyError: Error Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.319 - info: host.iobroker-hwr instance system.adapter.smartmeter.1 terminated with code 0 (NO_ERROR) 2019-10-01 02:33:29.320 - info: host.iobroker-hwr Do not restart adapter system.adapter.smartmeter.1 because disabled or deleted 2019-10-01 02:33:29.360 - warn: host.iobroker-hwr Cannot get view: ReplyError: Error Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.361 - info: host.iobroker-hwr instance system.adapter.smartmeter.0 terminated with code 0 (NO_ERROR) 2019-10-01 02:33:29.362 - info: host.iobroker-hwr Do not restart adapter system.adapter.smartmeter.0 because disabled or deleted 2019-10-01 02:33:42.303 - info: host.iobroker-hwr iobroker _restart 2019-10-01 02:33:42.816 - info: host.iobroker-hwr iobroker Starting node restart.js 2019-10-01 06:37:53.718 - info: host.iobroker-hwr iobroker.js-controller version 2.0.16 js-controller starting 2019-10-01 06:37:53.726 - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker 2019-10-01 06:37:53.726 - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3 2019-10-01 06:37:53.728 - info: host.iobroker-hwr ip addresses: 2019-10-01 06:37:53.749 - error: host.iobroker-hwr uncaught exception: connect ENETUNREACH 192.168.1.82:9001 - Local (0.0.0.0:0) 2019-10-01 06:37:53.750 - error: host.iobroker-hwr Error: connect ENETUNREACH 192.168.1.82:9001 - Local (0.0.0.0:0) at internalConnect (net.js:881:16) at defaultTriggerAsyncIdScope (internal/async_hooks.js:294:19) at defaultTriggerAsyncIdScope (net.js:971:9) at process._tickCallback (internal/process/next_tick.js:61:11) 2019-10-01 06:37:53.752 - info: host.iobroker-hwr terminated. Could not reset alive status for instances 2019-10-01 06:37:53.756 - info: host.iobroker-hwr iobroker _restart ┬─[darkiop@iobroker-hwr:~]─[06:41:17] ╰─>$ iobroker start Starting iobroker controller daemon... iobroker controller daemon started. PID: 1448Dann startet der iobroker-hwr sauber:
2019-10-01 06:42:00.051 - info: host.iobroker-hwr iobroker.js-controller version 2.0.16 js-controller starting 2019-10-01 06:42:00.059 - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker 2019-10-01 06:42:00.059 - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3 2019-10-01 06:42:00.061 - info: host.iobroker-hwr ip addresses: 10.3.1.22 fe80::dea6:32ff:fe17:78f5 2019-10-01 06:42:00.585 - info: host.iobroker-hwr connected to Objects and States 2019-10-01 06:42:00.628 - warn: host.iobroker-hwr Multihost discovery server: service started on 0.0.0.0:50005 2019-10-01 06:42:01.523 - info: host.iobroker-hwr Delete state "system.host.iobroker-hwr.compactModeEnabled" 2019-10-01 06:42:01.755 - info: host.iobroker-hwr 85 instances found 2019-10-01 06:42:01.773 - info: host.iobroker-hwr starting 2 instances 2019-10-01 06:42:01.793 - info: host.iobroker-hwr instance system.adapter.smartmeter.0 started with pid 1474 2019-10-01 06:42:02.063 - info: host.iobroker-hwr Some obsolete host states deleted. 2019-10-01 06:42:05.790 - info: host.iobroker-hwr instance system.adapter.smartmeter.1 started with pid 1489Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung
-
Starte ich nur den iobroker-master durch, schafft es der iobroker-hwr auch nicht mehr sich zu verbinden und alle io* Prozesse auf dem -hwr beenden sich.
Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung
-
@lobomau Prüf mal mit
ps -ef | grep ^ioOb noch ein Prozess vom ioBroker läuft, und wenn ja kannst du diesen per
kill -9 PROCESS-IDoder
pgrep -f '^io.*' | xargs kill -9auf die sanfte Art beenden :)
@darkiop sagte in [Aufruf] js-controller 2.0 Beta Test:
@lobomau Prüf mal mit
ps -ef | grep ^ioOb noch ein Prozess vom ioBroker läuft, und wenn ja kannst du diesen per
kill -9 PROCESS-IDoder
pgrep -f '^io.*' | xargs kill -9auf die sanfte Art beenden :)
Es werden keine laufenden io Prozesse gefunden. Der host wird auch korrekt in rot dargestellt unter dem Master Admin. Nur die Antwort auf "sudo iobroker status" scheint falsch zu sein mit "iobroker is running". Aber vielleicht steckt da schon irgendwo das Problem, dass es dann nicht dem Upgrade klappt?
-
iobroker status geht ja jetzt, es kommt aber noch ein Fehler:
root@MSNUC-IOB:~# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed. root@MSNUC-IOB:~#UPDATE: Wenn ich ins /opt/iobroker wechsel, dann kommt die Fehlermeldung nicht
root@MSNUC-IOB:~# cd /opt/iobroker/ root@MSNUC-IOB:/opt/iobroker# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis root@MSNUC-IOB:/opt/iobroker#Proxmox 3 Node HA-Cluster TRIGKEY Mini-PC N100 mit 32 GB RAM und 3x1TB shared SSDs. VM- iobroker ,Raspberrymatic. LXC - Adguard, , Traccar, iSpy, Fileserver (emby, MiniDLNA)...usw
-
iobroker status geht ja jetzt, es kommt aber noch ein Fehler:
root@MSNUC-IOB:~# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed. root@MSNUC-IOB:~#UPDATE: Wenn ich ins /opt/iobroker wechsel, dann kommt die Fehlermeldung nicht
root@MSNUC-IOB:~# cd /opt/iobroker/ root@MSNUC-IOB:/opt/iobroker# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis root@MSNUC-IOB:/opt/iobroker# -
Habe heute Zeit gefunden den neuen js-controller zu installieren, funktioniert auch soweit alles ohne Fehler.
Jetzt wollte ich noch auf redis/redis umstellen, dass will aber irgendwie nicht, bräuchte da mal Hilfe.
Hier der Konsole Mitschnitt:root@debian:/opt/iobroker# iobroker setup custom Current configuration: - Objects database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9001 - States database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9000 - Data Directory: ../../iobroker-data/ Type of objects DB [(f)ile, (r)edis], default [file]: r When Objects and Files are stored in a Redis database please consider the following: 1. All data will be stored in RAM, make sure to have enough free RAM available! 2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss! 3. The Redis persistence files can get big, make sure not to use an SD card to store them. Host / Unix Socket of objects DB(redis), default[127.0.0.1]: Port of objects DB(redis), default[6379]: Type of states DB [(f)file, (r)edis], default [redis]: r Host / Unix Socket of states DB (redis), default[127.0.0.1]: Port of states DB (redis), default[6379]: Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: n Important: Using Redis for the Objects database is only supported with js-controller 2.0 or higher! When your system consists of multiple hosts please make sure to have js-controller 2.0 or higher installed on ALL hosts *before* continuing! Important #2: If you already did the migration on an other host please *do not* migrate again! This can destroy your system! Important #3: The process will migrate all files that were officially uploaded into the ioBroker system. If you have manually copied files into iobroker-data/files/... into own directories then these files will NOT be migrated! Make sure all files are in adapter directories inside the files directory! Do you want to migrate objects and states from "file/file" to "redis/redis" [y/N]: y Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y Connecting to previous DB "file"... Creating backup ... This can take some time ... please be patient! host.debian 38585 states saved host.debian 44464 objects saved Backup created: /opt/iobroker/backups/2019_10_01-11_46_17_backupiobroker-migration.tar.gz Connecting to new DB "redis" ... /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:28 if (!options.states) throw 'Invalid arguments: states is missing'; ^ Invalid arguments: states is missing root@debian:/opt/iobroker# -
@arteck said in [Aufruf] js-controller 2.0 Beta Test:
@msauer machmal
service redis-server statusroot@MSNUC-IOB:/opt/iobroker# service redis-server status ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-10-01 08:44:47 CEST; 3h 31min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 408 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 462 (redis-server) Tasks: 4 (limit: 4701) Memory: 232.3M CGroup: /system.slice/redis-server.service └─462 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 08:44:46 MSNUC-IOB systemd[1]: Starting Advanced key-value store... Okt 01 08:44:47 MSNUC-IOB systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Okt 01 08:44:47 MSNUC-IOB systemd[1]: Started Advanced key-value store. root@MSNUC-IOB:/opt/iobroker#Proxmox 3 Node HA-Cluster TRIGKEY Mini-PC N100 mit 32 GB RAM und 3x1TB shared SSDs. VM- iobroker ,Raspberrymatic. LXC - Adguard, , Traccar, iSpy, Fileserver (emby, MiniDLNA)...usw
-
@arteck said in [Aufruf] js-controller 2.0 Beta Test:
@msauer machmal
service redis-server statusroot@MSNUC-IOB:/opt/iobroker# service redis-server status ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2019-10-01 08:44:47 CEST; 3h 31min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 408 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 462 (redis-server) Tasks: 4 (limit: 4701) Memory: 232.3M CGroup: /system.slice/redis-server.service └─462 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 08:44:46 MSNUC-IOB systemd[1]: Starting Advanced key-value store... Okt 01 08:44:47 MSNUC-IOB systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Okt 01 08:44:47 MSNUC-IOB systemd[1]: Started Advanced key-value store. root@MSNUC-IOB:/opt/iobroker# -
Habe heute Zeit gefunden den neuen js-controller zu installieren, funktioniert auch soweit alles ohne Fehler.
Jetzt wollte ich noch auf redis/redis umstellen, dass will aber irgendwie nicht, bräuchte da mal Hilfe.
Hier der Konsole Mitschnitt:root@debian:/opt/iobroker# iobroker setup custom Current configuration: - Objects database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9001 - States database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9000 - Data Directory: ../../iobroker-data/ Type of objects DB [(f)ile, (r)edis], default [file]: r When Objects and Files are stored in a Redis database please consider the following: 1. All data will be stored in RAM, make sure to have enough free RAM available! 2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss! 3. The Redis persistence files can get big, make sure not to use an SD card to store them. Host / Unix Socket of objects DB(redis), default[127.0.0.1]: Port of objects DB(redis), default[6379]: Type of states DB [(f)file, (r)edis], default [redis]: r Host / Unix Socket of states DB (redis), default[127.0.0.1]: Port of states DB (redis), default[6379]: Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: n Important: Using Redis for the Objects database is only supported with js-controller 2.0 or higher! When your system consists of multiple hosts please make sure to have js-controller 2.0 or higher installed on ALL hosts *before* continuing! Important #2: If you already did the migration on an other host please *do not* migrate again! This can destroy your system! Important #3: The process will migrate all files that were officially uploaded into the ioBroker system. If you have manually copied files into iobroker-data/files/... into own directories then these files will NOT be migrated! Make sure all files are in adapter directories inside the files directory! Do you want to migrate objects and states from "file/file" to "redis/redis" [y/N]: y Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y Connecting to previous DB "file"... Creating backup ... This can take some time ... please be patient! host.debian 38585 states saved host.debian 44464 objects saved Backup created: /opt/iobroker/backups/2019_10_01-11_46_17_backupiobroker-migration.tar.gz Connecting to new DB "redis" ... /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:28 if (!options.states) throw 'Invalid arguments: states is missing'; ^ Invalid arguments: states is missing root@debian:/opt/iobroker#@coyote du weisst aber schon dass du dafür einen RedisServer brauchst.. ??
zigbee hab ich, zwave auch, nuc's genauso und HA auch
-
Habe heute Zeit gefunden den neuen js-controller zu installieren, funktioniert auch soweit alles ohne Fehler.
Jetzt wollte ich noch auf redis/redis umstellen, dass will aber irgendwie nicht, bräuchte da mal Hilfe.
Hier der Konsole Mitschnitt:root@debian:/opt/iobroker# iobroker setup custom Current configuration: - Objects database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9001 - States database: - Type: file - Host/Unix Socket: 0.0.0.0 - Port: 9000 - Data Directory: ../../iobroker-data/ Type of objects DB [(f)ile, (r)edis], default [file]: r When Objects and Files are stored in a Redis database please consider the following: 1. All data will be stored in RAM, make sure to have enough free RAM available! 2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss! 3. The Redis persistence files can get big, make sure not to use an SD card to store them. Host / Unix Socket of objects DB(redis), default[127.0.0.1]: Port of objects DB(redis), default[6379]: Type of states DB [(f)file, (r)edis], default [redis]: r Host / Unix Socket of states DB (redis), default[127.0.0.1]: Port of states DB (redis), default[6379]: Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: n Important: Using Redis for the Objects database is only supported with js-controller 2.0 or higher! When your system consists of multiple hosts please make sure to have js-controller 2.0 or higher installed on ALL hosts *before* continuing! Important #2: If you already did the migration on an other host please *do not* migrate again! This can destroy your system! Important #3: The process will migrate all files that were officially uploaded into the ioBroker system. If you have manually copied files into iobroker-data/files/... into own directories then these files will NOT be migrated! Make sure all files are in adapter directories inside the files directory! Do you want to migrate objects and states from "file/file" to "redis/redis" [y/N]: y Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y Connecting to previous DB "file"... Creating backup ... This can take some time ... please be patient! host.debian 38585 states saved host.debian 44464 objects saved Backup created: /opt/iobroker/backups/2019_10_01-11_46_17_backupiobroker-migration.tar.gz Connecting to new DB "redis" ... /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupBackup.js:28 if (!options.states) throw 'Invalid arguments: states is missing'; ^ Invalid arguments: states is missing root@debian:/opt/iobroker# -
@arteck Ich hab im Code kaputt gemacht mit letzter Version :-(
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
@apollon77 waaaaaaaaaaatttttttttt...
-
@arteck na klar, der läuft auch.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Oct 1 12:02:55 2019 from 192.168.66.55 root@debian:~# systemctl status redis-server ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor pre Active: active (running) since Tue 2019-10-01 12:02:46 CEST; 42min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 327 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exite Main PID: 380 (redis-server) Tasks: 4 (limit: 3482) Memory: 10.4M CGroup: /system.slice/redis-server.service └─380 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 12:02:45 debian systemd[1]: Starting Advanced key-value store... Okt 01 12:02:46 debian systemd[1]: redis-server.service: Can't open PID file /ru Okt 01 12:02:46 debian systemd[1]: Started Advanced key-value store.@apollon77 ah ok, dann bin ich ja beruhigt, dachte ich mache was falsch :smirk:
-
@arteck na klar, der läuft auch.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Oct 1 12:02:55 2019 from 192.168.66.55 root@debian:~# systemctl status redis-server ● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor pre Active: active (running) since Tue 2019-10-01 12:02:46 CEST; 42min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 327 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exite Main PID: 380 (redis-server) Tasks: 4 (limit: 3482) Memory: 10.4M CGroup: /system.slice/redis-server.service └─380 /usr/bin/redis-server 127.0.0.1:6379 Okt 01 12:02:45 debian systemd[1]: Starting Advanced key-value store... Okt 01 12:02:46 debian systemd[1]: redis-server.service: Can't open PID file /ru Okt 01 12:02:46 debian systemd[1]: Started Advanced key-value store.@apollon77 ah ok, dann bin ich ja beruhigt, dachte ich mache was falsch :smirk:
-
Starte ich nur den iobroker-master durch, schafft es der iobroker-hwr auch nicht mehr sich zu verbinden und alle io* Prozesse auf dem -hwr beenden sich.
-
iobroker status geht ja jetzt, es kommt aber noch ein Fehler:
root@MSNUC-IOB:~# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Unable to subscribe to evicted Keyspace events from Redis Server: Error: Connection is closed. root@MSNUC-IOB:~#UPDATE: Wenn ich ins /opt/iobroker wechsel, dann kommt die Fehlermeldung nicht
root@MSNUC-IOB:~# cd /opt/iobroker/ root@MSNUC-IOB:/opt/iobroker# iobroker status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis root@MSNUC-IOB:/opt/iobroker# -
@apollon77 Sorry, viel Text heute Morgen - hier noch die Aktualisierung auf 2.0.16:
Alle Prozesse gestoppt, beide aktualisiert:
┬─[root@iobroker-master:/opt/iobroker]─[06:31:25] ╰─># sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller > iobroker.js-controller@2.0.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.4.1 > iobroker.js-controller@2.0.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/iobroker.pushbullet/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.0 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) + iobroker.js-controller@2.0.16 added 1 package from 3 contributors, removed 1 package, updated 8 packages and audited 40363 packages in 147.811s found 87 vulnerabilities (32 low, 10 moderate, 45 high) run `npm audit fix` to fix them, or `npm audit` for details┬─[darkiop@iobroker-hwr:/opt/iobroker]─[06:31:49] ╰─>$ sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller [sudo] Passwort für darkiop: > iobroker.js-controller@2.0.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.9.0 > iobroker.js-controller@2.0.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.0 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@2.0.16 removed 1 package, updated 8 packages and audited 1867 packages in 62.052s found 12 vulnerabilities (9 low, 3 high) run `npm audit fix` to fix them, or `npm audit` for detailsDann
- iobroker-master Container neu gestartet
- iobroker-hwr reboot
Nach reboot auf iobroker-hwr:
┬─[darkiop@iobroker-hwr:~]─[06:40:21] ╰─>$ iobroker status iobroker is not running on this host. At least one iobroker host is running. Objects type: file States type: file ┬─[darkiop@iobroker-hwr:~]─[06:40:26] ╰─>$ ps -ef | grep ^io ┬─[darkiop@iobroker-hwr:~]─[06:40:31] ╰─>$ tail -n 50 /opt/iobroker/log/iobroker.2019-10-01.log 2019-10-01 02:33:27.294 - warn: host.iobroker-hwr Slave controller detected disconnection. Stop all instances. 2019-10-01 02:33:27.301 - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.0 2019-10-01 02:33:27.302 - error: host.iobroker-hwr result is not defined 2019-10-01 02:33:29.315 - warn: host.iobroker-hwr Cannot get view: ReplyError: Error Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.319 - info: host.iobroker-hwr instance system.adapter.smartmeter.1 terminated with code 0 (NO_ERROR) 2019-10-01 02:33:29.320 - info: host.iobroker-hwr Do not restart adapter system.adapter.smartmeter.1 because disabled or deleted 2019-10-01 02:33:29.360 - warn: host.iobroker-hwr Cannot get view: ReplyError: Error Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f 2019-10-01 02:33:29.361 - info: host.iobroker-hwr instance system.adapter.smartmeter.0 terminated with code 0 (NO_ERROR) 2019-10-01 02:33:29.362 - info: host.iobroker-hwr Do not restart adapter system.adapter.smartmeter.0 because disabled or deleted 2019-10-01 02:33:42.303 - info: host.iobroker-hwr iobroker _restart 2019-10-01 02:33:42.816 - info: host.iobroker-hwr iobroker Starting node restart.js 2019-10-01 06:37:53.718 - info: host.iobroker-hwr iobroker.js-controller version 2.0.16 js-controller starting 2019-10-01 06:37:53.726 - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker 2019-10-01 06:37:53.726 - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3 2019-10-01 06:37:53.728 - info: host.iobroker-hwr ip addresses: 2019-10-01 06:37:53.749 - error: host.iobroker-hwr uncaught exception: connect ENETUNREACH 192.168.1.82:9001 - Local (0.0.0.0:0) 2019-10-01 06:37:53.750 - error: host.iobroker-hwr Error: connect ENETUNREACH 192.168.1.82:9001 - Local (0.0.0.0:0) at internalConnect (net.js:881:16) at defaultTriggerAsyncIdScope (internal/async_hooks.js:294:19) at defaultTriggerAsyncIdScope (net.js:971:9) at process._tickCallback (internal/process/next_tick.js:61:11) 2019-10-01 06:37:53.752 - info: host.iobroker-hwr terminated. Could not reset alive status for instances 2019-10-01 06:37:53.756 - info: host.iobroker-hwr iobroker _restart ┬─[darkiop@iobroker-hwr:~]─[06:41:17] ╰─>$ iobroker start Starting iobroker controller daemon... iobroker controller daemon started. PID: 1448Dann startet der iobroker-hwr sauber:
2019-10-01 06:42:00.051 - info: host.iobroker-hwr iobroker.js-controller version 2.0.16 js-controller starting 2019-10-01 06:42:00.059 - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker 2019-10-01 06:42:00.059 - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3 2019-10-01 06:42:00.061 - info: host.iobroker-hwr ip addresses: 10.3.1.22 fe80::dea6:32ff:fe17:78f5 2019-10-01 06:42:00.585 - info: host.iobroker-hwr connected to Objects and States 2019-10-01 06:42:00.628 - warn: host.iobroker-hwr Multihost discovery server: service started on 0.0.0.0:50005 2019-10-01 06:42:01.523 - info: host.iobroker-hwr Delete state "system.host.iobroker-hwr.compactModeEnabled" 2019-10-01 06:42:01.755 - info: host.iobroker-hwr 85 instances found 2019-10-01 06:42:01.773 - info: host.iobroker-hwr starting 2 instances 2019-10-01 06:42:01.793 - info: host.iobroker-hwr instance system.adapter.smartmeter.0 started with pid 1474 2019-10-01 06:42:02.063 - info: host.iobroker-hwr Some obsolete host states deleted. 2019-10-01 06:42:05.790 - info: host.iobroker-hwr instance system.adapter.smartmeter.1 started with pid 1489 -
Außer dem Node-RED Dashboard habe ich dann noch zwei Adapter die wohl ein Upgrade brauchen:
host.Ubuntu 2019-10-01 08:58:03.795 error instance system.adapter.daswetter.0 terminated with code 15 (15) daswetter.0 2019-10-01 08:58:03.774 error (32174) force terminate, objects still in list: 1571läuft unter 1.15.14 problemlos, und
broadlink2.0 2019-10-01 09:12:24.100 warn (865) sendState could not find command or scene named 'LG_TV-Power'als Beispiel. Den state gibt es definitiv und läuft ebenfalls unter 1.15.14 klaglos.
LG SBorg ( SBorg auf GitHub)
Projekte: Lebensmittelwarnung.de | WLAN-Wetterstation | PimpMyStation -
@SBorg den Fehler von daswetter hatte ich aber auch vor dem Update schon
@apollon77 @arteck ist es normal, dass mir das angezeigt wird bei der Umstellung auf redis/redis?
Host name of this machine [debian]: It appears that this host should be connected to an existing ioBroker System as Slave. Data Migration will be skipped. Is this correct? [Y/n]: nIch hab kein Master/Slave System
Support us
407
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge