{Gelöst] Fehler in iobroker Status Anzeige
-
Doch. Reichlich gelesen wo man sudo iobroker setup custom anwendet. Wie ich schon geschrieben habe, hab ich kein Multihost system
-
Ich glaube, wir beenden hier das Thema. Ist für mich ja gelöst. thx… sozusagen..
-
… von sudo iobroker setup custom hast du daher sicher schon etwas gehört.... `
In https://github.com/ioBroker/ioBroker.js-controller#using-redis-as-states-db ist beschrieben was mit/ohne installiertem REDIS für ioBroker konfiguriert werden muss.
Wird REDIS deinstalliert oder deaktiviert, verschwindet zwar die im ersten Post genannte Fehlermeldung, der Fehler im Zusammenspiel mit REDIS ist jedoch nicht beseitigt. Ich kann den Fehler noch auf meinem Testsystem reproduzieren: js-controller 1.4.2, admin 3.4.7
` > iouser@ioBroker-VM:~$ sudo iobroker statusiobroker is running
Ready check failed: Connection forcefully ended and command aborted. It might have been processed.
AbortError: Ready check failed: Connection forcefully ended and command aborted. It might have been processed.
at RedisClient.flush_and_error (/opt/iobroker/node_modules/redis/index.js:362:23)
at RedisClient.end (/opt/iobroker/node_modules/redis/lib/extendedApi.js:52:14)
at StateRedis.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:272:20)
at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2820:44)
at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:312:25
at Object.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3124:70)
at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemClient.js:120:68)
at Socket.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:133:20)
at Socket.emit (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:138:10)
at Socket.onconnect (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:335:8)</anonymous> `
Auffällig ist, dass ich zuvor ein restore von meinem produktiven System gemacht hatte. Auf beiden Systemen ist REDIS installiert und in ioBroker aktiviert. -
Bei mir spukt "iobroker status" genau das Gleiche Zeilen wie bei TS aus..
! ````
root@iobroker2:/opt/iobroker# iobroker status
iobroker is running
Ready check failed: Connection forcefully ended and command aborted. It might have been processed.
AbortError: Ready check failed: Connection forcefully ended and command aborted. It might have been processed.
at RedisClient.flush_and_error (/opt/iobroker/node_modules/redis/index.js:362:23)
at RedisClient.end (/opt/iobroker/node_modules/redis/lib/extendedApi.js:52:14)
at StateRedis.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:272:20)
at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2820:44)
at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:312:25
at Object.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3124:70)
at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemClient.js:120:68)
at Socket.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
at Socket.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:138:10)
at Socket.onconnect (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:332:8)</anonymous>Redis ist installiert und am laufen.. (Redis server v=3.2.6) Admin 3.4.7 Host 1.4.2 Node v8.11.3 NPM v6.1.0 -
Bei mir leider auch das gleiche. Dazu ist der Admin via Browser nicht erreichbar
! AbortError: Ready check failed: Connection forcefully ended and command aborted. It might have been processed.
! at RedisClient.flush_and_error (/opt/iobroker/node_modules/redis/index.js:362:23)
! at RedisClient.end (/opt/iobroker/node_modules/redis/lib/extendedApi.js:52:14)
! at StateRedis.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:275:24)
! at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2854:44)
! at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:314:25
! at Object.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3157:70)
! at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemClient.js:120:68)
! at Socket.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:133:20)
! at Socket.emit (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:138:10)
! at Socket.onconnect (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:335:8)</anonymous>Das komische ist, das es gestern noch ging. Hab mir über das latest Repo den Alexa2 Adapter installiert und dann wieder auf stable umgestellt. Anschließend mit ein paar Blockly Skripten experimentiert.
-
Hallo zusammen,
ich klinke mich hier noch mal ein. Nur um sicher zu gehen nichts falsch zu machen wenn ich etwas mache …
Als ich iobroker status habe laufen lassen kam das:
Ready check failed: Connection forcefully ended and command aborted. It might have been processed. AbortError: Ready check failed: Connection forcefully ended and command aborted. It might have been processed. at RedisClient.flush_and_error (/opt/iobroker/node_modules/redis/index.js:362:23) at RedisClient.end (/opt/iobroker/node_modules/redis/lib/extendedApi.js:52:14) at StateRedis.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:272:20) at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2820:44) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:312:25 at Object.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3124:70) at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemClient.js:120:68) at Socket.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:133:20) at Socket.emit (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:138:10) at Socket.onconnect (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:335:8)</anonymous>Dadurch bin ich auf das Thema hier gekommen.
Bluefox hat geschrieben ist gefixt auf Github - also habe ich gesucht, aber redis nicht gefunden. Redis wird für Multihost verwendet. Da ich von einem Image installiert habe weiß ich natürlich nicht was läuft … also habe ich gesucht und das gefunden:
iobroker multihost status
ergibt:
multihost status Nothing changed. Miltihost: disabled Authentication: enabled Objects: file on 127.0.0.1 States: redis on 127.0.0.1 Ready check failed: Connection forcefully ended and command aborted. It might have been processed. AbortError: Ready check failed: Connection forcefully ended and command aborted. It might have been processed. at RedisClient.flush_and_error (/opt/iobroker/node_modules/redis/index.js:362:23) at RedisClient.end (/opt/iobroker/node_modules/redis/lib/extendedApi.js:52:14) at StateRedis.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:272:20) at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2820:44) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2695:33 at showMHState (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupMultihost.js:84:9) at Multihost.status (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupMultihost.js:160:9) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2694:32 at Object.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3124:70) at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemClient.js:120:68)</anonymous>Kein Multihost, aber redis wird verwendet für states - richtig ?
Also sollte ich mich um den fehler kümmern, oder ?
Das einzige was ich jetzt als mögliche Lösung gefunden habe wäre:
apt-get install redis-server
Aber kommt das dann aus dem Github ? Eher nicht, oder ? Redis ist ja kein Adapter, also auch nicht über den Admin. Was muss ich tun ?
Vielen Dank,
vg
Marc
-
These are the result of a broken connection- e.g. you somehow lost connection with the Redis server. In the code, we're dealing with one of two scenarios (or both) - the connection has timed out or the the reconnect attempts have exceeded the maximum number specified in a config. I would double check your connection information and how your redis server is configured.
-
ok, thx so far … can it be that a lost connection is when the pi was not stable and restarted ? Means If I reboot and check the status again there should be nor error message ... if yes, something else is wrong, correct ? This is a workaround because I have installed from an image and do not know the exact configuration. Only I have seen how to enable/disable multihost but I do not need mh and actually mh is disabled ...
br
Marc
update:iobroker stopped, pi reboot - in the first few seconds there was no error message, ater some seconds the message was back ... so it seems that something else is wrong ...
Ich habe zum Test iobroker angehalten, den raspi neu gestartet und direkt nach dem Status geschaut. Anfangs stand dort nur das iobroker läuft, danach kam wieder die Fehlermeldung.
Wie kann das Problem behoben werden ?
vg
Marc
-
check mal redis `
Hab ich gemacht - Aber was soll ich als nächstes machen ? redis neu installieren bzw. darüber bügeln oder liegt es nicht an redis selber ?
-
Ich muss das Thema hier nochmal hochpushen.
Musste meinen NUC komplett runterfahren (mehr Speicher eingebaut) und danach läuft alles wieder super ABER ich bekomme auch obigen Fehler. Und ja ich benutze redis.
Was muss ich tun dass die Meldung nicht mehr kommt ?
sudo iobroker status iobroker is running Ready check failed: Connection forcefully ended and command aborted. It might have been processed. AbortError: Ready check failed: Connection forcefully ended and command aborted. It might have been processed. at RedisClient.flush_and_error (/opt/iobroker/node_modules/redis/index.js:362:23) at RedisClient.end (/opt/iobroker/node_modules/redis/lib/extendedApi.js:52:14) at StateRedis.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:272:20) at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2820:44) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:312:25 at Object.connected (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3124:70) at Socket. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemClient.js:120:68) at Socket.Emitter.emit (/opt/iobroker/node_modules/component-emitter/index.js:133:20) at Socket.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:138:10) at Socket.onconnect (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:335:8)</anonymous>UPDATE:
Scheint das ein bekannter Fehler für js 1.4.2 zu sein ? –> https://forum.iobroker.net/viewtopic.php?f=17&t=17777&p=186294&hilit=Ready+check+failed%3A+Connection+forcefully+ended+command+aborted#p186557
