Diskussion zum HowTo nodejs-Installation und upgrade
-
-
@thomas-braun
danke für die rückmeldung,
wow das diag kannte ich bisher nicht, hier die komplette info,
sieht irgendwie ziemlich kaputt aus:======================= SUMMARY ======================= v.2023-04-16 Operatingsystem: Raspbian GNU/Linux 11 (bullseye) Kernel: 6.1.21-v7+ Installation: Native Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Uncaught Rejection: Error: Cannot find module '@sentry/integrations' Require stack: - /opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js - /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js - /opt/iobroker/node_modules/@iobroker/plugin-base/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1026:15) at Function.Module._load (node:internal/modules/cjs/loader:871:27) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at SentryPlugin._registerSentry (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:103:36) at SentryPlugin.init (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:96:14) Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v16.20.0 /usr/bin/node v16.20.0 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 Recommended versions are nodejs 18.x.y and npm 9.x.y Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 922M 166M 320M 0.0K 435M 690M Swap: 0B 0B 0B Total: 922M 166M 320M Uncaught Rejection: Error: Cannot find module '@sentry/integrations' Require stack: - /opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js - /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js - /opt/iobroker/node_modules/@iobroker/plugin-base/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1026:15) at Function.Module._load (node:internal/modules/cjs/loader:871:27) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at SentryPlugin._registerSentry (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:103:36) at SentryPlugin.init (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:96:14) Active iob-Instances: 0 Uncaught Rejection: Error: Cannot find module '@sentry/integrations' Require stack: - /opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js - /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js - /opt/iobroker/node_modules/@iobroker/plugin-base/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1026:15) at Function.Module._load (node:internal/modules/cjs/loader:871:27) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at SentryPlugin._registerSentry (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:103:36) at SentryPlugin.init (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:96:14) ioBroker Core: js-controller 4.0.24 admin "admin" not found Uncaught Rejection: Error: Cannot find module '@sentry/integrations' Require stack: - /opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js - /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js - /opt/iobroker/node_modules/@iobroker/plugin-base/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1026:15) at Function.Module._load (node:internal/modules/cjs/loader:871:27) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at SentryPlugin._registerSentry (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:103:36) at SentryPlugin.init (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:96:14) ioBroker Status: Status admin and web instance: Uncaught Rejection: Error: Cannot find module '@sentry/integrations' Require stack: - /opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js - /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginHandler.js - /opt/iobroker/node_modules/@iobroker/plugin-base/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1026:15) at Function.Module._load (node:internal/modules/cjs/loader:871:27) at Module.require (node:internal/modules/cjs/loader:1098:19) at require (node:internal/modules/cjs/helpers:108:18) at SentryPlugin._registerSentry (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:103:36) at SentryPlugin.init (/opt/iobroker/node_modules/@iobroker/plugin-sentry/index.js:96:14) Objects: 0 States: 0 Size of iob-Database: 4.8M /opt/iobroker/iobroker-data/objects.json.migrated 4.8M /opt/iobroker/iobroker-data/objects.json.bak.migrated 4.7M /opt/iobroker/iobroker-data/objects.jsonl 4.0K /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ==================== -
@tschombe sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
hier die komplette info,
New, das ist die Zusammenfassung. Der vollständige Kram steht davor.
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controllerliefert?
1GB ist erfahrungsgemäß mittlerweile aber auch zu wenig für einen sinnvollen Betrieb des iobrokers.
-
ok, dh man sollte direkt auf einen raspi 4 gehen?
dann muss ich mal hardware shopping gehenwie lange läuft dieses script? scheint sich bei mir igendwie hier aufgehangen zu haben,
oder braucht das evtl relativ lange:pi@homematicPI:/opt/iobroker $ cd /opt/iobroker pi@homematicPI:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 (##################) ⠇ reify:iobroker.admin: timing reifyNode:node_modules/iobroker.javascript Completed in 79961mses ist noch nicht vollständig durchgelaufen
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
anscheinend wurde es irgendwie abgebrochen:
Getötet############) ⠇ reify:iobroker.admin: timing reifyNode:node_modules/iobroker.javascript Completed in 79961ms -
Ich möchte von node.js 14 auf 18 updaten.
Laut der Anleitung wird ein sauber npm-tree benötigt.
Überprüfung mit
cd /opt/iobroker npm ls | grep -E 'github|ERR'ergibt bei mir:
│ │ │ ├── github-from-package@0.0.0 npm ERR! peer dep missing: buffer@>=6.0.3, required by crc@4.1.1 npm ERR! peer dep missing: @iobroker/types@^5.0.11, required by @iobroker/adapter-core@3.0.3Und nun?
-
@frank2604 sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
Und nun?
Nichts. Weiter machen.
Ich hab es im HowTo ergänzt.
-
Danke. Ist soweit alles fehlerfrei durchgelaufen.
Alle Instanzen bis auf den Zigbee laufen wieder. Der meldet im Log folgendes:
host.vm-iobroker-02 2023-08-12 11:31:07.119 info Rebuild for adapter system.adapter.zigbee.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually. host.vm-iobroker-02 2023-08-12 11:31:07.119 error instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.vm-iobroker-02 2023-08-12 11:31:07.119 error Caught by controller[0]: Node.js v18.17.1 host.vm-iobroker-02 2023-08-12 11:31:07.119 error Caught by controller[0]: } host.vm-iobroker-02 2023-08-12 11:31:07.119 error Caught by controller[0]: ] host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.zigbee/main.js' host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@iobroker/adapter-core/build/index.js', host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: requireStack: [ host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: code: 'MODULE_NOT_FOUND', host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) { host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@iobroker/adapter-core/build/index.js:21:1) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at require (node:internal/modules/cjs/helpers:121:18) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15) host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.zigbee/main.js host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.zigbee/node_modules/@iobroker/adapter-core/build/index.js host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: Require stack: host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: Error: Cannot find module '@iobroker/types' host.vm-iobroker-02 2023-08-12 11:31:07.118 error Caught by controller[0]: ^ host.vm-iobroker-02 2023-08-12 11:31:07.117 error Caught by controller[0]: throw err; host.vm-iobroker-02 2023-08-12 11:31:07.117 error Caught by controller[0]: node:internal/modules/cjs/loader:1080 host.vm-iobroker-02 2023-08-12 11:31:06.702 info instance system.adapter.zigbee.0 started with pid 14766 host.vm-iobroker-02 2023-08-12 11:31:06.600 info "system.adapter.zigbee.0" enabled -
Hat sich erledigt. Habe im Verzeichnis:
/opt/iobroker/node_modules/iobroker.zigbee/node_modulesdas ausgeführt:
npm install --productionJetzt läuft auch Zigbee wieder.
-
Als Node und Linux dummy habe ich folgende Frage:
Mein ioBroker meldet seit gestern , dass es wohl neue Versionen gibt:
Node.js: v18.17.1(18.18.0)
NPM: 9.6.7(9.8.1)Ich habe mit sudo apt-get Update und Upgrade versucht, die Updates durchzuführen. Es bleibt aber alles beim Alten. Die anschließende Abfrage zeigt:
nodejs:
Installiert: 18.17.1-deb-1nodesource1
Installationskandidat: 18.17.1-deb-1nodesource1
Versionstabelle:
*** 18.17.1-deb-1nodesource1 500
500 https://deb.nodesource.com/node_18.x bullseye/main amd64 Packages
100 /var/lib/dpkg/status
12.22.12~dfsg-1~deb11u4 500
500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
12.22.12~dfsg-1~deb11u3 500
500 http://deb.debian.org/debian bullseye/main amd64 PackagesFrage an die Profis: was mache ich falsch? Wie installiere ich Node.js 18.18.0 bzw. Npm 9.8.1? Bzw. sollte ich das überhaupt updated?
-
@skorpil Schau ein Stück weiter oben in die Signatur von @Thomas-Braun . Da gibt es einen Link zu einem NodeJS Fixer Skript.
Das aktualisiert Dir auf die aktuelle Version 18.18.0 (die Du auch verwenden solltest).Gruss, Jürgen
-
@wildbill Dankeschön, das hatte ich offenbar überlesen. Ich werde es so versuchen.
-
@wildbill feedback is breakfast for champions: hat funktioniert. Danke!
-
Hey so sieht es aus wenn ich die Installation nochmal durchgehe:
Von allein wollte der nicht auf die neuste Version!
System latest offizelles Docker Image...
Ich hoffe das es damit gerade gezogen und aktuell ist.
Vielleicht kann mir jemand das bestätigen??
DANKE
root@iobroker:/opt/iobroker# uname -m && type -P nodejs node npm npx corepack && nodejs -v && node -v && npm -v && npx -v && corepack -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs x86_64 /usr/bin/nodejs /usr/bin/node /usr/bin/npm /usr/bin/npx /usr/bin/corepack v18.18.0 v18.18.0 9.8.1 9.8.1 0.19.0 5.0.12 root root /opt/iobroker Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. nodejs: Installed: 18.18.0-1nodesource1 Candidate: 18.18.0-1nodesource1 Version table: *** 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages root@iobroker:/opt/iobroker#Mod-EDIT: Code in Code-Tags setzen!
-
Beim Docker zieht man sich i. A. einen frischen aus dem Regal.
-
Was meinst du damit genau?
Der Docker Container Manager zieht sich immer das latest Image und migriert diese direkt.
https://registry.hub.docker.com/r/iobroker/iobroker/Aber updaten tut sich da kein Node und npm.... Habe das immer manuell gemacht bisher...
Nur jetzt über die neue Methode von dir, da die alte nicht mehr ging :_) -
@mcreuter sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
Aber updaten tut sich da kein Node und npm.... Habe das immer manuell gemacht bisher...
Ich hab ja keine Aktien in den Dingern, aber die kommen eigentlich immer mit passender Umgebung vorgekocht daher. Ich glaube in der Version 9 des Docker-Images ist dann auch nodejs@18.18.0 eingebacken.
-
@thomas-braun Ok, kein Ding kann man ja buanet mal fragen...
https://github.com/buanet/ioBroker.dockerJA kann sein, die V9 ist als Beta pre Release schon in arbeit mit Debian 12 soweit ich das gesehen habe
https://github.com/buanet/ioBroker.docker/tree/v9.0.0-beta.1-
Änderungen:
remove special settings script and env for zwave (#377)
simplify ci/ reduce gh actions
ignore errors in "silent cleanup" on first start (#369)
cleanup/ restructure repo
update nodejs setup process
update base image to debian 12 (bookworm)
improve security by avoiding root (exept startup script itself)
restrict iobroker commanline commands (start/ stop/ node fix)
integrate maintenance script into iobroker command
move container config files location
-
-
Auch bei mir hat der normale Befehl per update und upgrade nicht zum Erfolg geführt. Ich habe dann den Link von @thomas-braun genutzt und den iob node fix laufen lassen. Das hat geklappt. Verstanden habe ich es aber nicht, da die Pfade ja scheinbar richtig waren und frühere Updates immer funktioniert haben.
Vielen Dank an alle Helfer!ioBroker nodejs fixer 2023-09-24 Recommended nodejs-version is: 18.18.0 Checking your installation now. Please be patient! Your current setup is: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 We found these nodejs versions available for installation: nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Nothing to do - Your installation is using the correct paths. You are running nodejs v18.17.1. Do you want to install recommended version 18.18.0? Press <y> to continue or any other key to quit Trying to fix your installation now. Please be patient. Waiting for ioBroker to shut down - Give me a minute... ############################################################ *** These repos are active on your system: Hit:1 http://deb.debian.org/debian bullseye InRelease Get:2 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB] Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Get:4 http://archive.raspberrypi.org/debian bullseye InRelease [23.6 kB] Hit:5 https://repos.influxdata.com/debian stable InRelease Get:6 http://archive.raspberrypi.org/debian bullseye/main armhf Packages [314 kB] Get:7 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages [308 kB] Fetched 694 kB in 2s (399 kB/s) Reading package lists... Done *** Installing ca-certificates, curl and gnupg, just in case they are missing. *** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main Package: nodejs Pin: origin deb.nodesource.com Pin-Priority: 1001 *** These repos are active after the adjustments: Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://repos.influxdata.com/debian stable InRelease Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease Get:6 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB] Get:7 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages [5267 B] Get:8 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages [5262 B] Fetched 22.7 kB in 2s (9910 B/s) Reading package lists... Done Installing the recommended nodejs version now! (Reading database ... 50588 files and directories currently installed.) Preparing to unpack .../nodejs_18.18.0-1nodesource1_arm64.deb ... Detected old npm client, removing... Unpacking nodejs (18.18.0-1nodesource1) over (18.17.1-deb-1nodesource1) ... Setting up nodejs (18.18.0-1nodesource1) ... Processing triggers for man-db (2.9.4-2) ... We tried our best to fix your nodejs. Please run iob diag again to verify. *** RESTARTING ioBroker NOW! *** Please refresh or restart your browser in a few moments. pi@raspberrypi:/opt/iobroker $ -
@jack01 sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
Verstanden habe ich es aber nicht, da die Pfade ja scheinbar richtig waren und frühere Updates immer funktioniert haben.
Der Aufbau der Paketquelle hat sich geändert und daher muss entsprechend in deinem System auch einiges umgestellt werden. Neue Versionen von nodejs kommen nur noch über das neue Repository.
Das node-fix-Skript nimmt dir das weitgehend ab.
