Troubleshooting NodeJS update
-
Hallo, wollte nodejs von 14 auf 18 updaten - wie kann ich das fixen? thx
sudo apt update Ign:1 http://security.debian.org/debian-security stretch/updates InRelease Fehl:2 http://security.debian.org/debian-security stretch/updates Release 404 Not Found [IP: 199.232.18.132 80] Ign:3 http://ftp.de.debian.org/debian stretch InRelease Ign:4 http://ftp.de.debian.org/debian stretch-updates InRelease Fehl:5 http://ftp.de.debian.org/debian stretch Release 404 Not Found Fehl:6 http://ftp.de.debian.org/debian stretch-updates Release 404 Not Found OK:7 https://deb.nodesource.com/node_18.x bullseye InRelease Paketlisten werden gelesen... Fertig E: The repository 'http://security.debian.org/debian-security stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://ftp.de.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://ftp.de.debian.org/debian stretch-updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -
Dein Betriebssystem ist hoffnungslos veraltet.
Bring das zunächst auf das 'Bullseye'-Release.Der Sprung ist aber so groß, installier es neu.
Wieder diese 'never tatsch a ranning süstäm'-Mär geglaubt?
-
mir wird angezeigt, dass es ein Punkt-Update gibt. Wenn ich aber nach Anleitung nodejs erst de- und dann installiere bleibt es bei 18.16.0
das steht in Info beim ioBroker, und wird letztlich auch bei unten stehendem Terminalbefehl angezeigt.
Node.js: v18.16.0(18.16.1)pi@HomeServer01:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null pi@HomeServer01:~ $ type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v /usr/bin/nodejs /usr/bin/node /usr/bin/npm /usr/bin/npx v18.16.0 v18.16.0 9.5.1 9.5.1einfach noch ein paar Tage warten?
das ganze ist kein "Problem", freu mich nur, wenn ich überall immer "Vorne" bin.
Danke Euch schon mal -
@hannnes sagte in Troubleshooting NodeJS update:
einfach noch ein paar Tage warten?
Ja, das ist von nodesource im downstream noch nicht umgepackt worden.
Upstream ist es von nodejs.org natürlich schon released worden, daher auch der Hinweis. -
@thomas-braun sagte in Troubleshooting NodeJS update:
@hannnes sagte in Troubleshooting NodeJS update:
einfach noch ein paar Tage warten?
Ja, das ist von nodesource im downstream noch nicht umgepackt worden.
Upstream ist es von nodejs.org natürlich schon released worden, daher auch der Hinweis.danke Dir!
-
Hey.
Nur ne Verständnisfrage: warum wird bzw wurde das empfohlene Vorgehen zum 'Update' geändert? Die 'alte' Anleitung war im Prinzip doch gar nicht so alt. Einfach, damit die Installation 'sauberer' ist? (alte Anleitung war ja (ggf) sources anpassen, iob stoppen, (Backup), apt Update, Upgrade, fertig).
Danke für die Aufklärung.
Ab nämlich gerade - aus Gewohnheit - so geupdatet und erst parallel dazu gefunden, dass ein neues Vorgehen empfohlen wird.
Ich Frage ausdrücklich NICHT um zu kritisieren, sondern wirklich aus Interesse. Das "hier" beschriebene Vorgehen der kompletten Neuinstallation hätte doch schon immer funktioniert?!. Statt dessen wurde (vor 2? Jahren noch mit 2 Befehlen (curl.....) gearbeitet, dann mit dem von mir "beschriebenen" update->upgrade und jetzt so).
Grüße
Max -
@m-a-x sagte in Troubleshooting NodeJS update:
Ab nämlich gerade - aus Gewohnheit - so geupdatet und erst parallel dazu gefunden, dass ein neues Vorgehen empfohlen wird.
Was meinst du genau?
Es führen mehrere Wege zu einer korrekten Installation. -
@m-a-x sagte in Troubleshooting NodeJS update:
Die 'alte'
link bitte!
@m-a-x sagte in Troubleshooting NodeJS update:
geändert
ebenfalls link bitte, damit wir auch vom gleichen reden!
-
@thomas-braun @Homoran
Ich habe diese Methode angewendet (mit nano zum Beispiel die 18er source hinzugefügt und von 16 auf 18 geupdatet, seitdem immer (ohne nano) mit sudo apt Update - > Upgrade).
(https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian)Die Methode davor finde ich gerade nicht mehr im forum.
Im Prinzip war das ein iobroker stop / Backup mit anschließendem curl Befehl (um die aktuelle source zu bekommen und dann nem 'install nodejs') -
Das ist kein grundlegender Unterschied. Kann man beides machen.
-
@m-a-x sagte in Troubleshooting NodeJS update:
seitdem immer (ohne nano) mit sudo apt Update - > Upgrade).
damit bleibst du immer innerhalb der major Version
um auf eine neue major Version (14, 16, 18) zu kommen musst du eine der beiden Vorgehensweisen durchführen.
-
@homoran hey. Ja, das wusste ich ausnahmsweise mal
ich wollte damit nur beschreiben, wie ich bisher vorgegangen bin.
Danke für die Aufklärung @thomas-braun @Homoran -
Moin moin,
ich habe einmal mein NodeJS aus folgender Anleitung von 16 auf 18 geupdatet.
https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18
Nun bekomme ich solche Fehlermeldungen in meinem System. Habe schon ein wenig gegoogelt, aber nix passendes gefunden. Hat da jemand einen Tipp für mich ?
Gruß André
host.IOBroker-Proxmox 2023-07-01 14:18:03.996 error instance system.adapter.amazon-dash.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.IOBroker-Proxmox 2023-07-01 14:18:03.995 error Caught by controller[0]: Node.js v18.16.1 host.IOBroker-Proxmox 2023-07-01 14:18:03.995 error Caught by controller[0]: } host.IOBroker-Proxmox 2023-07-01 14:18:03.995 error Caught by controller[0]: code: 'ERR_DLOPEN_FAILED' host.IOBroker-Proxmox 2023-07-01 14:18:03.995 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) { host.IOBroker-Proxmox 2023-07-01 14:18:03.995 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.IOBroker-Proxmox 2023-07-01 14:18:03.970 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.IOBroker-Proxmox 2023-07-01 14:18:03.970 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) host.IOBroker-Proxmox 2023-07-01 14:18:03.970 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/pcap/pcap.js:3:21) host.IOBroker-Proxmox 2023-07-01 14:18:03.970 error Caught by controller[0]: at require (node:internal/modules/cjs/helpers:110:18) host.IOBroker-Proxmox 2023-07-01 14:18:03.970 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) host.IOBroker-Proxmox 2023-07-01 14:18:03.970 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.IOBroker-Proxmox 2023-07-01 14:18:03.969 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.IOBroker-Proxmox 2023-07-01 14:18:03.969 error Caught by controller[0]: at Module._extensions..node (node:internal/modules/cjs/loader:1340:18) host.IOBroker-Proxmox 2023-07-01 14:18:03.969 error Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). host.IOBroker-Proxmox 2023-07-01 14:18:03.969 error Caught by controller[0]: NODE_MODULE_VERSION 108. Please try re-compiling or re-installing host.IOBroker-Proxmox 2023-07-01 14:18:03.969 error Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires host.IOBroker-Proxmox 2023-07-01 14:18:03.969 error Caught by controller[0]: was compiled against a different Node.js version using host.IOBroker-Proxmox 2023-07-01 14:18:03.968 error Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/pcap/build/Release/pcap_binding.node' host.IOBroker-Proxmox 2023-07-01 14:18:03.968 error Caught by controller[0]: ^ host.IOBroker-Proxmox 2023-07-01 14:18:03.968 error Caught by controller[0]: return process.dlopen(module, path.toNamespacedPath(filename)); host.IOBroker-Proxmox 2023-07-01 14:18:03.967 error Caught by controller[0]: node:internal/modules/cjs/loader:1340 -
Installier den Adapter nochmal frisch.
-
@thomas-braun sagte in Troubleshooting NodeJS update:
Installier den Adapter nochmal frisch.
Der DashButton Adapter läuft. Auch mein System läuft. Ich frage mich aber, was das für ganze Fehlermeldungen sind ?
-
@gelberlemmy sagte in Troubleshooting NodeJS update:
Ich frage mich aber, was das für ganze Fehlermeldungen sind ?
Welche? Frisch aus dem LogFile.
-
@thomas-braun sagte in Troubleshooting NodeJS update:
@gelberlemmy sagte in Troubleshooting NodeJS update:
Ich frage mich aber, was das für ganze Fehlermeldungen sind ?
Welche? Frisch aus dem LogFile.
aus meinem Post
-
Ein Neustart des Adapters schaut nun wie aus?
Bitte ausiob logs -watch | uniqich mag nicht verkehrt herum lesen.
-
@gelberlemmy sagte in Troubleshooting NodeJS update:
Error: The module '/opt/iobroker/node_modules/pcap/build/Release/pcap_binding.node'
@gelberlemmy sagte in Troubleshooting NodeJS update:
was compiled against a different Node.js version
irgendwelche Systemdateien hin und herkopiert?
-
@thomas-braun sagte in Troubleshooting NodeJS update:
Ein Neustart des Adapters schaut nun wie aus?
Bitte ausiob logs -watch | uniqich mag nicht verkehrt herum lesen.
Habe einmal mein IOBroker neu gestartet. Log ist voller Errors. Aber fährt dann trotzdem normal alle Adapter hoch.
host.IOBroker-Proxmox 2023-07-01 21:23:12.703 info Some obsolete host states deleted. host.IOBroker-Proxmox 2023-07-01 21:23:12.697 info Delete state "system.host.IOBroker-Proxmox.versions.npmNewestNext" host.IOBroker-Proxmox 2023-07-01 21:23:12.690 info Delete state "system.host.IOBroker-Proxmox.versions.npmNewest" host.IOBroker-Proxmox 2023-07-01 21:23:12.684 info Delete state "system.host.IOBroker-Proxmox.versions.npmCurrent" host.IOBroker-Proxmox 2023-07-01 21:23:12.677 info Delete state "system.host.IOBroker-Proxmox.versions.nodeNewestNext" host.IOBroker-Proxmox 2023-07-01 21:23:12.619 info Delete state "system.host.IOBroker-Proxmox.versions.nodeNewest" host.IOBroker-Proxmox 2023-07-01 21:23:12.605 info instance system.adapter.admin.0 started with pid 304 host.IOBroker-Proxmox 2023-07-01 21:23:12.360 info starting 47 instances host.IOBroker-Proxmox 2023-07-01 21:23:12.292 info 52 instances found host.IOBroker-Proxmox 2023-07-01 21:23:12.291 info Delete state "system.host.IOBroker-Proxmox.versions.nodeCurrent" host.IOBroker-Proxmox 2023-07-01 21:23:11.037 info added notifications configuration of host host.IOBroker-Proxmox 2023-07-01 21:23:10.942 info connected to Objects and States host.IOBroker-Proxmox 2023-07-01 21:23:07.788 info ip addresses: 192.168.171.35 fe80::a8d4:caff:fe76:9b25 host.IOBroker-Proxmox 2023-07-01 21:23:07.787 info hostname: IOBroker-Proxmox, node: v18.16.1 host.IOBroker-Proxmox 2023-07-01 21:23:07.787 info Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker host.IOBroker-Proxmox 2023-07-01 21:23:07.781 info iobroker.js-controller version 5.0.5 js-controller starting host.IOBroker-Proxmox 2023-07-01 21:22:54.794 info terminated host.IOBroker-Proxmox 2023-07-01 21:22:54.708 info All instances are stopped. host.IOBroker-Proxmox 2023-07-01 21:22:54.708 info instance system.adapter.ham.0 terminated with code 0 (NO_ERROR) host.IOBroker-Proxmox 2023-07-01 21:22:54.708 info All instances are stopped. host.IOBroker-Proxmox 2023-07-01 21:22:54.707 info instance system.adapter.history.0 terminated with code 0 (NO_ERROR) host.IOBroker-Proxmox 2023-07-01 21:22:54.629 info instance system.adapter.shelly.1 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.629 warn instance system.adapter.shelly.1 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:54.628 error Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) host.IOBroker-Proxmox 2023-07-01 21:22:54.628 error Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) host.IOBroker-Proxmox 2023-07-01 21:22:54.628 error Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) host.IOBroker-Proxmox 2023-07-01 21:22:54.628 error Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) host.IOBroker-Proxmox 2023-07-01 21:22:54.628 error Caught by controller[0]: Error: DB closed host.IOBroker-Proxmox 2023-07-01 21:22:54.628 error Caught by controller[0]: 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(). The promise rejected with the reason: host.IOBroker-Proxmox 2023-07-01 21:22:54.599 info instance system.adapter.shelly.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.599 warn instance system.adapter.shelly.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:54.599 error Caught by controller[0]: at processImmediate (node:internal/timers:447:9) host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5) host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: Error: DB closed host.IOBroker-Proxmox 2023-07-01 21:22:54.598 error Caught by controller[0]: 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(). The promise rejected with the reason: host.IOBroker-Proxmox 2023-07-01 21:22:54.170 info instance system.adapter.hue-extended.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.170 warn instance system.adapter.hue-extended.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:54.170 info instance system.adapter.zigbee.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.170 warn instance system.adapter.zigbee.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:54.103 info instance system.adapter.javascript.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.102 warn instance system.adapter.javascript.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:54.055 info instance system.adapter.jarvis.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.055 warn instance system.adapter.jarvis.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:54.054 info instance system.adapter.zwave2.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:54.054 warn instance system.adapter.zwave2.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.988 info instance system.adapter.alexa2.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.988 warn instance system.adapter.alexa2.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.938 info instance system.adapter.admin.1 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.938 warn instance system.adapter.admin.1 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.896 info instance system.adapter.admin.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.896 warn instance system.adapter.admin.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.895 info instance system.adapter.amazon-dash.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.895 warn instance system.adapter.amazon-dash.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.819 info instance system.adapter.energiefluss.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.819 warn instance system.adapter.energiefluss.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.778 info instance system.adapter.accuweather.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.778 warn instance system.adapter.accuweather.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.745 info instance system.adapter.senec.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.745 warn instance system.adapter.senec.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.745 info instance system.adapter.worx.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.745 warn instance system.adapter.worx.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.650 info instance system.adapter.proxmox.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.650 warn instance system.adapter.proxmox.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.620 info instance system.adapter.web.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.619 warn instance system.adapter.web.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.589 info instance system.adapter.trashschedule.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.589 warn instance system.adapter.trashschedule.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.589 info instance system.adapter.text2command.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.589 warn instance system.adapter.text2command.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.501 info instance system.adapter.sourceanalytix.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.500 warn instance system.adapter.sourceanalytix.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.470 info instance system.adapter.pushsafer.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.470 warn instance system.adapter.pushsafer.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.439 info instance system.adapter.octoprint.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.439 warn instance system.adapter.octoprint.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.439 info instance system.adapter.iot.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.438 warn instance system.adapter.iot.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.356 info instance system.adapter.info.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.356 warn instance system.adapter.info.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.326 info instance system.adapter.homeconnect.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.326 warn instance system.adapter.homeconnect.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.325 info instance system.adapter.fb-checkpresence.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.325 warn instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.149 info instance system.adapter.enocean.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.148 warn instance system.adapter.enocean.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:53.070 info instance system.adapter.discovery.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:53.070 warn instance system.adapter.discovery.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.989 info instance system.adapter.device-reminder.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.988 warn instance system.adapter.device-reminder.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.988 info instance system.adapter.cloud.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.988 warn instance system.adapter.cloud.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.909 info instance system.adapter.backitup.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.909 warn instance system.adapter.backitup.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.869 info instance system.adapter.alarm.2 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.869 warn instance system.adapter.alarm.2 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.839 info instance system.adapter.alarm.1 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.839 warn instance system.adapter.alarm.1 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.839 info instance system.adapter.alarm.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.839 warn instance system.adapter.alarm.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.746 info instance system.adapter.tr-064.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.746 warn instance system.adapter.tr-064.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.716 info instance system.adapter.samsung.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.716 warn instance system.adapter.samsung.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.685 info instance system.adapter.nut.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.685 warn instance system.adapter.nut.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.685 info instance system.adapter.sonoff.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.684 warn instance system.adapter.sonoff.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.595 info instance system.adapter.netatmo.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.595 warn instance system.adapter.netatmo.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.564 info instance system.adapter.mqtt.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.564 warn instance system.adapter.mqtt.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.515 info instance system.adapter.hmip.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.515 warn instance system.adapter.hmip.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.515 info instance system.adapter.telegram.1 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.514 warn instance system.adapter.telegram.1 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.437 info instance system.adapter.telegram.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.437 warn instance system.adapter.telegram.0 terminated due to SIGTERM host.IOBroker-Proxmox 2023-07-01 21:22:52.396 info instance system.adapter.email.0 terminated with code null () host.IOBroker-Proxmox 2023-07-01 21:22:52.395 warn instance system.adapter.email.0 terminated due to SIGTERM shelly.1 2023-07-01 21:22:48.051 error DB closed shelly.0 2023-07-01 21:22:47.944 error DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) hue-extended.0 2023-07-01 21:22:47.658 error unhandled promise rejection: DB 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 (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9) hue-extended.0 2023-07-01 21:22:47.658 error 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(). hue-extended.0 2023-07-01 21:22:47.657 error unhandled promise rejection: DB 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 (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) hue-extended.0 2023-07-01 21:22:47.658 error Error: DB closed hue-extended.0 2023-07-01 21:22:47.658 error DB closed hue-extended.0 2023-07-01 21:22:47.657 error 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(). hue-extended.0 2023-07-01 21:22:47.656 error unhandled promise rejection: DB 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 (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) hue-extended.0 2023-07-01 21:22:47.657 error Error: DB closed hue-extended.0 2023-07-01 21:22:47.657 error DB closed hue-extended.0 2023-07-01 21:22:47.656 error 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(). hue-extended.0 2023-07-01 21:22:47.655 error unhandled promise rejection: DB 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 (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) hue-extended.0 2023-07-01 21:22:47.656 error Error: DB closed hue-extended.0 2023-07-01 21:22:47.656 error DB closed hue-extended.0 2023-07-01 21:22:47.654 error 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(). hue-extended.0 2023-07-01 21:22:47.654 error Error: DB 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 (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) hue-extended.0 2023-07-01 21:22:47.655 error Error: DB closed hue-extended.0 2023-07-01 21:22:47.655 error DB closed hue-extended.0 2023-07-01 21:22:47.654 error unhandled promise rejection: DB closed hue-extended.0 2023-07-01 21:22:47.654 error DB closed shelly.0 2023-07-01 21:22:47.930 error Error: DB closed shelly.0 2023-07-01 21:22:46.742 error unhandled promise rejection: DB closed shelly.0 2023-07-01 21:22:46.741 error 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(). shelly.1 2023-07-01 21:22:48.050 error Error: DB closed shelly.1 2023-07-01 21:22:46.721 error unhandled promise rejection: DB closed shelly.1 2023-07-01 21:22:46.721 error 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().
