NEWS
js-controller 4.0 jetzt im BETA/LATEST!
-
Das behebt das Problem nicht:
2022-02-21 10:40:38.147 - [32minfo[39m: host.iobroker "system.adapter.vis.0" enabled 2022-02-21 10:40:39.910 - [32minfo[39m: vis.0 (2892) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.vis, node: v14.19.0, js-controller: 4.0.12 2022-02-21 10:40:40.184 - [32minfo[39m: vis.0 (2892) vis license is OK. 2022-02-21 10:40:40.242 - [31merror[39m: vis.0 (2892) uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/fritzdect/css/style.css' 2022-02-21 10:40:40.245 - [31merror[39m: vis.0 (2892) Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/fritzdect/css/style.css' at Object.openSync (fs.js:497:3) at Object.writeFileSync (fs.js:1528:35) at copyFileSync (/opt/iobroker/node_modules/iobroker.vis/lib/install.js:16:8) at /opt/iobroker/node_modules/iobroker.vis/lib/install.js:36:17 at Array.forEach (<anonymous>) at copyFolderRecursiveSync (/opt/iobroker/node_modules/iobroker.vis/lib/install.js:31:15) at /opt/iobroker/node_modules/iobroker.vis/lib/install.js:34:17 at Array.forEach (<anonymous>) at copyFolderRecursiveSync (/opt/iobroker/node_modules/iobroker.vis/lib/install.js:31:15) at /opt/iobroker/node_modules/iobroker.vis/lib/install.js:34:17 2022-02-21 10:40:40.246 - [31merror[39m: vis.0 (2892) Exception-Code: EACCES: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/fritzdect/css/style.css' 2022-02-21 10:40:40.762 - [32minfo[39m: vis.0 (2892) terminating 2022-02-21 10:40:40.764 - [33mwarn[39m: vis.0 (2892) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-02-21 10:40:41.371 - [32minfo[39m: host.iobroker instance system.adapter.vis.0 terminated while should be started onceIch führe mal ein iobroker fix durch.
Nach iobroker fix:
2022-02-21 10:51:21.640 - [32minfo[39m: vis.0 (1348) starting. Version 1.4.5 in /opt/iobroker/node_modules/iobroker.vis, node: v14.19.0, js-controller: 4.0.12 2022-02-21 10:51:21.904 - [32minfo[39m: vis.0 (1348) vis license is OK. 2022-02-21 10:51:23.094 - [32minfo[39m: vis.0 (1348) Terminated (NO_ERROR): Without reason 2022-02-21 10:51:23.691 - [32minfo[39m: host.iobroker instance system.adapter.vis.0 terminated while should be started onceDanach wieder hoch zu 1.4.12. Jetzt läuft vis wieder. Nur hätte ich mir das alles sparen können, weil mein ursprüngliches Problem weiterhin existiert...
@ofbeqnpolkkl6mby5e13 sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Nur hätte ich mir das alles sparen können, weil mein ursprüngliches Problem weiterhin existiert...
??
-
@ofbeqnpolkkl6mby5e13 sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Nur hätte ich mir das alles sparen können, weil mein ursprüngliches Problem weiterhin existiert...
??
Restore mit VIS v1.4.12 geht mindestens bei mir nicht und hat mit JS-Controller nichts zu tun. Das Problem, weshalb ich auf einen älteren Stand wollte, ist aber Off-Topic.
Danke für die Hilfe!
-
Ja so zeigt es proxmox an. Eingestellt habe ich 5GB ich kann der Iobroker VM ohne Probleme noch mehr RAM geben.
Muss ich mir nachher mal anschauen…
Edit:
root@iobroker:~# free -m gesamt benutzt frei gemns. Puffer/Cache verfügbar Speicher: 4812 3954 541 0 316 630 Swap: 974 221 753@saeft_2003 Kannst du mir mal einen gefallen tun?
Mach mal eine Shell auf mit "top", dann drücke "Shift-M" - das sortiert dir die EInträge nach RAM nutzung. Dnan am besten davon nen Screenshot
Jetzt bitte mal zwei Dinge tun:
1.) in einer zweiten Shell ein "iob backup" ausführen
2.) Backup über BackItUp manuell startenUnd bei beiden Dingen bitte mal das "top" beobachten ... Wo steigt der RAM Verbrauch an und wenn ja in welchem prozess?
Vllt kommen wir so ein bissl dahinter
-
@saeft_2003 Kannst du mir mal einen gefallen tun?
Mach mal eine Shell auf mit "top", dann drücke "Shift-M" - das sortiert dir die EInträge nach RAM nutzung. Dnan am besten davon nen Screenshot
Jetzt bitte mal zwei Dinge tun:
1.) in einer zweiten Shell ein "iob backup" ausführen
2.) Backup über BackItUp manuell startenUnd bei beiden Dingen bitte mal das "top" beobachten ... Wo steigt der RAM Verbrauch an und wenn ja in welchem prozess?
Vllt kommen wir so ein bissl dahinter
@apollon77
Ich habe meine zweite iobroker Instanz (Raspberry 3) ohne Probleme umgestellt.
Dort hatte ich früher die States auf redis umgestellt und würde jetzt gern auf JSONL migrieren.iobroker status iobroker is running on this host. Objects type: jsonl States type: redisIst das unproblematisch?
HW:NUC (16 GB Ram)
OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3 -
@apollon77
Ich habe meine zweite iobroker Instanz (Raspberry 3) ohne Probleme umgestellt.
Dort hatte ich früher die States auf redis umgestellt und würde jetzt gern auf JSONL migrieren.iobroker status iobroker is running on this host. Objects type: jsonl States type: redisIst das unproblematisch?
-
@apollon77 Danke. Hat unproblematisch geklappt.
-
Aktualisiere gerade ein Slave von 4.0.10 auf 4.0.15.
Habe es nun bereits mitsudo -H -u iobroker npm install iobroker.js-controllerversucht.Bei den anderen Geräten hatte ich dieses Problem nicht.
Was kann ich tun?pi@raspberrypi-display2:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller > iobroker.js-controller@4.0.10 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > iobroker.js-controller@4.0.10 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first No connection to objects 192.168.3.100:6379[redis] /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at TCP.<anonymous> (net.js:686:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at processTicksAndRejections (internal/process/task_queues.js:95:5) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker.js-controller@4.0.10 install: `node iobroker.js setup first` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.10 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-02-21T20_58_28_730Z-debug.lKeine Ahnung was jetzt los ist.. :astonished:
pi@raspberrypi-display2:~ $ iobroker stop pi@raspberrypi-display2:~ $ iobroker fix library: loaded Library version=2022-02-10 ioBroker is not installed in /opt/iobroker! Cannot fix anything... -
Aktualisiere gerade ein Slave von 4.0.10 auf 4.0.15.
Habe es nun bereits mitsudo -H -u iobroker npm install iobroker.js-controllerversucht.Bei den anderen Geräten hatte ich dieses Problem nicht.
Was kann ich tun?pi@raspberrypi-display2:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller > iobroker.js-controller@4.0.10 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > iobroker.js-controller@4.0.10 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first No connection to objects 192.168.3.100:6379[redis] /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at TCP.<anonymous> (net.js:686:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at processTicksAndRejections (internal/process/task_queues.js:95:5) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker.js-controller@4.0.10 install: `node iobroker.js setup first` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.10 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-02-21T20_58_28_730Z-debug.lKeine Ahnung was jetzt los ist.. :astonished:
pi@raspberrypi-display2:~ $ iobroker stop pi@raspberrypi-display2:~ $ iobroker fix library: loaded Library version=2022-02-10 ioBroker is not installed in /opt/iobroker! Cannot fix anything... -
@e-i-k-e Wie geht es dem Redis? Steht ggf etwas im Redis log? Ich hab das gefühl das sich der beendet mittendrin.
-
Hast du zufällig den Pfad parat?
Ich habe den kompletten Container inkl. Reids mal neu gestartet. Keine Änderung.
-
@AlCalzone @apollon77
Hab eben per CLI admin, web und ws aktualisiert und dann ist der js-controller mal wieder RAM technisch eskaliert mit über 2 GB. Hat sich dann aber ohne mein Zutun wieder stabilisiert. Wahrs. reichten die 6 GB RAM der VM gerade so aus.total used free shared buff/cache available Mem: 5941 4407 131 1 1402 1242 Swap: 0 0 0
..:: So long! Tom ::..
NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB
-
Danke.
Im Log steht immer das gleiche, nichts auffälliges.
11670:C 20 Feb 2022 22:13:49.210 * DB saved on disk 11670:C 20 Feb 2022 22:13:49.228 * RDB: 7 MB of memory used by copy-on-write 139:M 20 Feb 2022 22:13:49.345 * Background saving terminated with success 139:M 20 Feb 2022 22:15:49.680 * 10000 changes in 60 seconds. Saving... 139:M 20 Feb 2022 22:15:49.698 * Background saving started by pid 11703 11703:C 20 Feb 2022 22:16:04.583 * DB saved on disk 11703:C 20 Feb 2022 22:16:04.601 * RDB: 14 MB of memory used by copy-on-write 139:M 20 Feb 2022 22:16:04.688 * Background saving terminated with success 139:M 20 Feb 2022 22:18:21.814 * 10000 changes in 60 seconds. Saving...pi@ioBroker-Rock:~$ systemctl status redis * redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-02-21 22:27:17 CET; 46min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 114 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 135 (redis-server) Tasks: 4 (limit: 18952) Memory: 1.7G CPU: 6min 39.212s CGroup: /system.slice/redis-server.service `-135 /usr/bin/redis-server 0.0.0.0:6379Fünf weitere Slave laufen aber auch problemlos mit dem Master und der Redis DB.
-
Danke.
Im Log steht immer das gleiche, nichts auffälliges.
11670:C 20 Feb 2022 22:13:49.210 * DB saved on disk 11670:C 20 Feb 2022 22:13:49.228 * RDB: 7 MB of memory used by copy-on-write 139:M 20 Feb 2022 22:13:49.345 * Background saving terminated with success 139:M 20 Feb 2022 22:15:49.680 * 10000 changes in 60 seconds. Saving... 139:M 20 Feb 2022 22:15:49.698 * Background saving started by pid 11703 11703:C 20 Feb 2022 22:16:04.583 * DB saved on disk 11703:C 20 Feb 2022 22:16:04.601 * RDB: 14 MB of memory used by copy-on-write 139:M 20 Feb 2022 22:16:04.688 * Background saving terminated with success 139:M 20 Feb 2022 22:18:21.814 * 10000 changes in 60 seconds. Saving...pi@ioBroker-Rock:~$ systemctl status redis * redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-02-21 22:27:17 CET; 46min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 114 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 135 (redis-server) Tasks: 4 (limit: 18952) Memory: 1.7G CPU: 6min 39.212s CGroup: /system.slice/redis-server.service `-135 /usr/bin/redis-server 0.0.0.0:6379Fünf weitere Slave laufen aber auch problemlos mit dem Master und der Redis DB.
Ich beobachte einen seltsamen Effekt, den ich nicht verstehe.
Ich habe iob mit dem Update auf von js-controller 4 von Objects type: jsonl
States type: redis auf Objects type: jsonl States type: jsonl umgestellt, was auch ohne Probleme geklappt hat und einige Stunden stabil lief.Dann hatte ich mir gedacht, dass ich redis ausschalte, um ein bisschen Speicher zu sparen. Diese Änderung führte zu einer dramatischen Instabilität. Iob konnte kein Web Interface mehr anzeigen, die über SSH gestartet Console hat mich nach einigen Sekunden wieder rausgeschmissen und Debmatic ist auch nicht mehr gestartet. Ansonsten habe ich noch NextPVR installiert. Debmatic und NextPVR haben keine Abhängigkeiten von redis.
Es wirkt so, als ob es dennoch Prozesse gibt, die immer noch redis Verfügbarkeit benötigen und wenn sie die nicht bekommen, das System extrem belasten.Gottseidank konnte ich in der kurzen Zeitspanne, in der die Console funktioniert hat, den redis Server wieder via SSH einschalten und jetzt läuft es wieder stabil.
Hat jemand eine Idee? Kann man irgendwie herausbekommen, wer den Redis Server benutzt?
HW:NUC (16 GB Ram)
OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3 -
Ich beobachte einen seltsamen Effekt, den ich nicht verstehe.
Ich habe iob mit dem Update auf von js-controller 4 von Objects type: jsonl
States type: redis auf Objects type: jsonl States type: jsonl umgestellt, was auch ohne Probleme geklappt hat und einige Stunden stabil lief.Dann hatte ich mir gedacht, dass ich redis ausschalte, um ein bisschen Speicher zu sparen. Diese Änderung führte zu einer dramatischen Instabilität. Iob konnte kein Web Interface mehr anzeigen, die über SSH gestartet Console hat mich nach einigen Sekunden wieder rausgeschmissen und Debmatic ist auch nicht mehr gestartet. Ansonsten habe ich noch NextPVR installiert. Debmatic und NextPVR haben keine Abhängigkeiten von redis.
Es wirkt so, als ob es dennoch Prozesse gibt, die immer noch redis Verfügbarkeit benötigen und wenn sie die nicht bekommen, das System extrem belasten.Gottseidank konnte ich in der kurzen Zeitspanne, in der die Console funktioniert hat, den redis Server wieder via SSH einschalten und jetzt läuft es wieder stabil.
Hat jemand eine Idee? Kann man irgendwie herausbekommen, wer den Redis Server benutzt?
-
Node.js: v14.19.0
js-controller: 4.0.15Habe gerade folgendes nach einem Neustart des Shelly Adapters im Log gefunden:
2022-02-22 06:12:00.875 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.876 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:300:10) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.877 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.880 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.880 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at writeVarByteInt (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:804:17) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:302:3) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.880 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.881 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.881 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:303:10) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.881 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.882 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party 2022-02-22 06:12:00.882 - error: shelly.0 (15030) Error: This socket has been ended by the other party at Socket.writeAfterFIN [as write] (net.js:468:14) at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:305:10) at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) at writeOrBuffer (internal/streams/writable.js:358:12) at Writable.write (internal/streams/writable.js:303:10) at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.882 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party 2022-02-22 06:12:00.883 - warn: shelly.0 (15030) Terminated (UNCAUGHT_EXCEPTION): Without reason 2022-02-22 06:12:00.950 - error: host.iobroker Caught by controller[1]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:300:10) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at writeVarByteInt (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:804:17) 2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:302:3) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:303:10) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[3]: Error: This socket has been ended by the other party 2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[3]: at Socket.writeAfterFIN [as write] (net.js:468:14) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:305:10) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at writeOrBuffer (internal/streams/writable.js:358:12) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Writable.write (internal/streams/writable.js:303:10) 2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22) 2022-02-22 06:12:00.961 - error: host.iobroker Caught by controller[3]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64) 2022-02-22 06:12:00.961 - error: host.iobroker Caught by controller[3]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5) 2022-02-22 06:12:00.962 - error: host.iobroker Caught by controller[3]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11) 2022-02-22 06:12:00.962 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 1 (JS_CONTROLLER_STOPPED) -
@AlCalzone @apollon77
Hab eben per CLI admin, web und ws aktualisiert und dann ist der js-controller mal wieder RAM technisch eskaliert mit über 2 GB. Hat sich dann aber ohne mein Zutun wieder stabilisiert. Wahrs. reichten die 6 GB RAM der VM gerade so aus.total used free shared buff/cache available Mem: 5941 4407 131 1 1402 1242 Swap: 0 0 0 -
@AlCalzone @apollon77
Hab eben per CLI admin, web und ws aktualisiert und dann ist der js-controller mal wieder RAM technisch eskaliert mit über 2 GB. Hat sich dann aber ohne mein Zutun wieder stabilisiert. Wahrs. reichten die 6 GB RAM der VM gerade so aus.total used free shared buff/cache available Mem: 5941 4407 131 1 1402 1242 Swap: 0 0 0@diginix hast du bitte mal das log dieser Updates und paar mins davor und danach bitte? Auch: wie genau wurden die Updates ausgeführt? Einzeln? Uplgrade all?
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
-
Danke.
Im Log steht immer das gleiche, nichts auffälliges.
11670:C 20 Feb 2022 22:13:49.210 * DB saved on disk 11670:C 20 Feb 2022 22:13:49.228 * RDB: 7 MB of memory used by copy-on-write 139:M 20 Feb 2022 22:13:49.345 * Background saving terminated with success 139:M 20 Feb 2022 22:15:49.680 * 10000 changes in 60 seconds. Saving... 139:M 20 Feb 2022 22:15:49.698 * Background saving started by pid 11703 11703:C 20 Feb 2022 22:16:04.583 * DB saved on disk 11703:C 20 Feb 2022 22:16:04.601 * RDB: 14 MB of memory used by copy-on-write 139:M 20 Feb 2022 22:16:04.688 * Background saving terminated with success 139:M 20 Feb 2022 22:18:21.814 * 10000 changes in 60 seconds. Saving...pi@ioBroker-Rock:~$ systemctl status redis * redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-02-21 22:27:17 CET; 46min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 114 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 135 (redis-server) Tasks: 4 (limit: 18952) Memory: 1.7G CPU: 6min 39.212s CGroup: /system.slice/redis-server.service `-135 /usr/bin/redis-server 0.0.0.0:6379Fünf weitere Slave laufen aber auch problemlos mit dem Master und der Redis DB.
-
Ich beobachte einen seltsamen Effekt, den ich nicht verstehe.
Ich habe iob mit dem Update auf von js-controller 4 von Objects type: jsonl
States type: redis auf Objects type: jsonl States type: jsonl umgestellt, was auch ohne Probleme geklappt hat und einige Stunden stabil lief.Dann hatte ich mir gedacht, dass ich redis ausschalte, um ein bisschen Speicher zu sparen. Diese Änderung führte zu einer dramatischen Instabilität. Iob konnte kein Web Interface mehr anzeigen, die über SSH gestartet Console hat mich nach einigen Sekunden wieder rausgeschmissen und Debmatic ist auch nicht mehr gestartet. Ansonsten habe ich noch NextPVR installiert. Debmatic und NextPVR haben keine Abhängigkeiten von redis.
Es wirkt so, als ob es dennoch Prozesse gibt, die immer noch redis Verfügbarkeit benötigen und wenn sie die nicht bekommen, das System extrem belasten.Gottseidank konnte ich in der kurzen Zeitspanne, in der die Console funktioniert hat, den redis Server wieder via SSH einschalten und jetzt läuft es wieder stabil.
Hat jemand eine Idee? Kann man irgendwie herausbekommen, wer den Redis Server benutzt?
@marty56 zeigmal
iob setup customwenn alle hosts bei dir auf jsonl laufen dann ist redis überflüssig.. da läuft nix mehr im hintergrund
zigbee hab ich, zwave auch, nuc's genauso und HA auch
-
Aktualisiere gerade ein Slave von 4.0.10 auf 4.0.15.
Habe es nun bereits mitsudo -H -u iobroker npm install iobroker.js-controllerversucht.Bei den anderen Geräten hatte ich dieses Problem nicht.
Was kann ich tun?pi@raspberrypi-display2:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller > iobroker.js-controller@4.0.10 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > iobroker.js-controller@4.0.10 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first No connection to objects 192.168.3.100:6379[redis] /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^ Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at TCP.<anonymous> (net.js:686:12) Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at processTicksAndRejections (internal/process/task_queues.js:95:5) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker.js-controller@4.0.10 install: `node iobroker.js setup first` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.10 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-02-21T20_58_28_730Z-debug.lKeine Ahnung was jetzt los ist.. :astonished:
pi@raspberrypi-display2:~ $ iobroker stop pi@raspberrypi-display2:~ $ iobroker fix library: loaded Library version=2022-02-10 ioBroker is not installed in /opt/iobroker! Cannot fix anything...
852
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge