Kein Update mehr möglich mit Node.js 16
-
@negalein sagte in Kein Update mehr möglich mit Node.js 16:
Ist ja fast wie ein ....vergleich!
seltsame Einstellung.
wenn du so gut damit führest bräuchtest du hier nicht um Hilfe zu rufen.
-
@homoran sagte in Kein Update mehr möglich mit Node.js 16:
wenn du so gut damit führest bräuchtest du hier nicht um Hilfe zu rufen.
wegen den einem Fehler??
Komm, lassen wir es gut sein! -
Darf ich mich hier mal ranhängen? Irgendwo habe ich wieder was verbockt und scheitere nun daran, Adapter zu aktualisieren. Nachdem alles zunächst im Updateprozess zu funktionieren scheint bricht der Vorgang dann mit "exited with code 0" ab.
Hier ein paar Details aus dem Terminal:
pi@raspberrypi:/opt/iobroker $ npm -v 8.11.0 pi@raspberrypi:/opt/iobroker $ node -v v16.15.1 pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ npm ls | grep ERR npm ERR! code ELSPROBLEMS npm ERR! invalid: iobroker.admin@5.3.8 /opt/iobroker/node_modules/iobroker.admin npm ERR! invalid: iobroker.alexa2@3.11.2 /opt/iobroker/node_modules/iobroker.alexa2 npm ERR! invalid: iobroker.alias-manager@1.2.4 /opt/iobroker/node_modules/iobroker.alias-manager npm ERR! invalid: iobroker.backitup@2.4.9 /opt/iobroker/node_modules/iobroker.backitup npm ERR! invalid: iobroker.daswetter@3.1.2 /opt/iobroker/node_modules/iobroker.daswetter npm ERR! invalid: iobroker.deconz@1.3.21 /opt/iobroker/node_modules/iobroker.deconz npm ERR! invalid: iobroker.device-reminder@1.2.9 /opt/iobroker/node_modules/iobroker.device-reminder npm ERR! invalid: iobroker.discovery@3.0.3 /opt/iobroker/node_modules/iobroker.discovery npm ERR! invalid: iobroker.fritzdect@2.2.3 /opt/iobroker/node_modules/iobroker.fritzdect npm ERR! invalid: iobroker.heos@1.10.0 /opt/iobroker/node_modules/iobroker.heos npm ERR! invalid: iobroker.history@1.11.1 /opt/iobroker/node_modules/iobroker.history npm ERR! invalid: iobroker.ical@1.12.1 /opt/iobroker/node_modules/iobroker.ical npm ERR! invalid: iobroker.icons-material-png@0.1.0 /opt/iobroker/node_modules/iobroker.icons-material-png npm ERR! invalid: iobroker.icons-material-svg@0.1.0 /opt/iobroker/node_modules/iobroker.icons-material-svg npm ERR! invalid: iobroker.icons-mfd-svg@1.1.0 /opt/iobroker/node_modules/iobroker.icons-mfd-svg npm ERR! invalid: iobroker.icons-open-icon-library-png@0.1.2 /opt/iobroker/node_modules/iobroker.icons-open-icon-library-png npm ERR! invalid: iobroker.icons-ultimate-png@1.0.1 /opt/iobroker/node_modules/iobroker.icons-ultimate-png npm ERR! invalid: iobroker.influxdb@2.6.3 /opt/iobroker/node_modules/iobroker.influxdb npm ERR! invalid: iobroker.javascript@5.7.0 /opt/iobroker/node_modules/iobroker.javascript npm ERR! invalid: iobroker.js-controller@4.0.23 /opt/iobroker/node_modules/iobroker.js-controller npm ERR! invalid: iobroker.km200@2.0.3 /opt/iobroker/node_modules/iobroker.km200 npm ERR! invalid: iobroker.lupusec@1.3.6 /opt/iobroker/node_modules/iobroker.lupusec npm ERR! invalid: iobroker.netatmo@1.7.1 /opt/iobroker/node_modules/iobroker.netatmo npm ERR! invalid: iobroker.nuki-extended@2.4.0 /opt/iobroker/node_modules/iobroker.nuki-extended npm ERR! invalid: iobroker.onvif@0.4.4 /opt/iobroker/node_modules/iobroker.onvif npm ERR! invalid: iobroker.parcel@0.0.15 /opt/iobroker/node_modules/iobroker.parcel npm ERR! invalid: iobroker.pushover@2.1.0 /opt/iobroker/node_modules/iobroker.pushover npm ERR! invalid: iobroker.shelly@5.3.2 /opt/iobroker/node_modules/iobroker.shelly npm ERR! invalid: iobroker.simple-api@2.7.0 /opt/iobroker/node_modules/iobroker.simple-api npm ERR! invalid: iobroker.smartcontrol@1.2.1 /opt/iobroker/node_modules/iobroker.smartcontrol npm ERR! invalid: iobroker.smartgarden@2.0.0 /opt/iobroker/node_modules/iobroker.smartgarden npm ERR! invalid: iobroker.socketio@4.2.0 /opt/iobroker/node_modules/iobroker.socketio npm ERR! invalid: iobroker.sonos@2.1.7 /opt/iobroker/node_modules/iobroker.sonos npm ERR! invalid: iobroker.sony-bravia@1.0.3 /opt/iobroker/node_modules/iobroker.sony-bravia npm ERR! invalid: iobroker.synology@2.1.7 /opt/iobroker/node_modules/iobroker.synology npm ERR! invalid: iobroker.telegram@1.13.0 /opt/iobroker/node_modules/iobroker.telegram npm ERR! invalid: iobroker.text2command@2.2.1 /opt/iobroker/node_modules/iobroker.text2command npm ERR! invalid: iobroker.tr-064@4.2.16 /opt/iobroker/node_modules/iobroker.tr-064 npm ERR! invalid: iobroker.trashschedule@2.0.2 /opt/iobroker/node_modules/iobroker.trashschedule npm ERR! invalid: iobroker.uv-protect@0.3.5 /opt/iobroker/node_modules/iobroker.uv-protect npm ERR! invalid: iobroker.vis-fancyswitch@1.1.0 /opt/iobroker/node_modules/iobroker.vis-fancyswitch npm ERR! invalid: iobroker.vis-hqwidgets@1.2.0 /opt/iobroker/node_modules/iobroker.vis-hqwidgets npm ERR! invalid: iobroker.vis-icontwo@0.87.0 /opt/iobroker/node_modules/iobroker.vis-icontwo npm ERR! invalid: iobroker.vis-inventwo@3.3.1 /opt/iobroker/node_modules/iobroker.vis-inventwo npm ERR! invalid: iobroker.vis-material-advanced@1.7.2 /opt/iobroker/node_modules/iobroker.vis-material-advanced npm ERR! invalid: iobroker.vis-timeandweather@1.1.7 /opt/iobroker/node_modules/iobroker.vis-timeandweather npm ERR! invalid: iobroker.vis-weather@2.5.5 /opt/iobroker/node_modules/iobroker.vis-weather npm ERR! invalid: iobroker.vis@1.4.15 /opt/iobroker/node_modules/iobroker.vis npm ERR! invalid: iobroker.vw-connect@0.0.50 /opt/iobroker/node_modules/iobroker.vw-connect npm ERR! invalid: iobroker.web@4.3.0 /opt/iobroker/node_modules/iobroker.web npm ERR! invalid: iobroker.whatsapp-cmb@0.2.2 /opt/iobroker/node_modules/iobroker.whatsapp-cmb npm ERR! invalid: iobroker.yahka@0.13.1 /opt/iobroker/node_modules/iobroker.yahka npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-04T17_35_04_806Z-debug-0.logKann mir jemand helfen, wie ich die Installation wieder auf die richtige Spur setzen kann? Ich hoffe, an einer Neuinstallation des iobrokers vorbeizukommen...
-
Wie bist du da jetzt unterwegs?
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejsnodejs16 schon mal sauber auf die letzte Version bringen.
Dann
iobroker upgrade admin --debug -
@thomas-braun said in Kein Update mehr möglich mit Node.js 16:
Wie bist du da jetzt unterwegs?
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejspi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs ln: die symbolische Verknüpfung '/usr/bin/nodejs' konnte nicht angelegt werden: Die Datei existiert bereits armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.15.1 v16.15.1 8.11.0 pi /home/pi OK:1 http://archive.raspberrypi.org/debian bullseye InRelease OK:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease OK:3 https://repos.influxdata.com/debian bullseye InRelease OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease OK:5 https://packages.grafana.com/oss/deb stable InRelease OK:6 https://phoscon.de/apt/deconz bullseye InRelease Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Aktualisierung für 96 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen. nodejs: Installiert: 16.15.1-deb-1nodesource1 Installationskandidat: 16.17.0-deb-1nodesource1 Versionstabelle: 16.17.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages *** 16.15.1-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages -
@kimukao sagte in Kein Update mehr möglich mit Node.js 16:
Aktualisierung für 96 Pakete verfügbar.
Updaten.
iobroker stop sudo apt update sudo apt full-upgrade sudo rebootDas Ganze regelmäßig machen.
-
@thomas-braun Danke. Hat ein paar Minuten gedauert bis das Update durchgelaufen war. Hab auch den reboot gemacht. Jetzt sieht's folgendermaßen aus:
pi@raspberrypi:~ $ npm -v 8.15.0 pi@raspberrypi:~ $ node -v v16.17.0 pi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs ln: die symbolische Verknüpfung '/usr/bin/nodejs' konnte nicht angelegt werden: Die Datei existiert bereits armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.17.0 v16.17.0 8.15.0 pi /home/pi OK:1 http://archive.raspberrypi.org/debian bullseye InRelease OK:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease OK:3 https://packages.grafana.com/oss/deb stable InRelease OK:4 https://repos.influxdata.com/debian bullseye InRelease OK:5 https://phoscon.de/apt/deconz bullseye InRelease OK:6 https://deb.nodesource.com/node_16.x bullseye InRelease Paketlisten werden gelesen… Fertig Abhängigkeitsbaum wird aufgebaut… Fertig Statusinformationen werden eingelesen… Fertig Alle Pakete sind aktuell. nodejs: Installiert: 16.17.0-deb-1nodesource1 Installationskandidat: 16.17.0-deb-1nodesource1 Versionstabelle: *** 16.17.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packagesund:
pi@raspberrypi:~ $ iobroker upgrade admin --debug Connection is closed. Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:632:23) at processTicksAndRejections (node:internal/process/task_queues:96:5) Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed. Unable to subscribe to meta namespace "meta." changes: Connection is closed.Das Problem beim Adapter-Update "exited with code 0" besteht weiterhin
-
@kimukao sagte in Kein Update mehr möglich mit Node.js 16:
Uncaught Rejection: Error: Objects DB is not allowed to start in the current Multihost environment
Ist das ein Multihost?
iobroker statusliefert?
-
@thomas-braun said in Kein Update mehr möglich mit Node.js 16:
Ist das ein Multihost?
Nicht dass ich wüsste. Wenn, dann ist es meiner Unkenntnis geschuldet.
pi@raspberrypi:~ $ iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonl -
Hat noch jemand einen Tip für mich? Komme echt nicht weiter grade... Hab auch schon den iobroker fix durchlaufen lassen
iobroker stop iobroker fix pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker library: loaded Library version=2022-06-15 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2022-06-03 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/3) ========================================================================== Holen:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15,0 kB] OK:2 http://archive.raspberrypi.org/debian bullseye InRelease OK:3 https://repos.influxdata.com/debian bullseye InRelease OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease Holen:5 https://packages.grafana.com/oss/deb stable InRelease [12,1 kB] OK:6 https://phoscon.de/apt/deconz bullseye InRelease Holen:7 https://packages.grafana.com/oss/deb stable/main armhf Packages [37,6 kB] Es wurden 64,7 kB in 2 s geholt (36,9 kB/s). Paketlisten werden gelesen… Fertig Installed gcc-c++ ========================================================================== Checking ioBroker user and directory permissions (2/3) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Checking autostart (3/3) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi:~ $ iobroker startUnd trotzdem immer noch "exited with code 0" beim Versuch, Adapter upzudaten
-
@thomas-braun Die Status Meldung scheint doch in Ordnung zu sein, oder?
-
Code 0
heißt eigentich 'alles I.O.' -
@thomas-braun Leider wird das Update der Adapter aber mit dem Hinweis immer abgebrochen. Das sieht dann zB so aus:
$ iobroker upgrade backitup@2.4.10 Update backitup from @2.4.9 to @2.4.10 host.raspberrypi Adapter "system.adapter.backitup.0" is stopped. NPM version: 8.15.0 Installing iobroker.backitup@2.4.10... (System call) upload [10] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.js index_m.js application/javascript upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.css tab_m.css text/css upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript host.raspberrypi Adapter "system.adapter.backitup.0" is started Process exited with code 0 -
@kimukao sagte in Kein Update mehr möglich mit Node.js 16:
iobroker upgrade backitup@2.4.10
Mach es mit --debug-Option in der Konsole:
iobroker upgrade backitup@2.4.10 --debug -
@thomas-braun Hat leider auch nicht funktioniert:
iobroker upgrade backitup@2.4.10 --debug This upgrade of "backitup" will introduce the following changes: ========================================================================== -> 2.4.10: Code cleaning dependencies updated Disclaimer added Travis Support removed Fix backup-download with ssl ========================================================================== Would you like to upgrade backitup from @2.4.9 to @2.4.10 now? [(y)es, (n)o]: y Update backitup from @2.4.9 to @2.4.10 host.raspberrypi Adapter "system.adapter.backitup.0" is stopped. NPM version: 8.15.0 Installing iobroker.backitup@2.4.10... (System call) npm ERR! builtins is not a function npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-06T11_28_01_889Z-debug-0.log upload [10] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.js index_m.js application/javascript upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.css tab_m.css text/css upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript host.raspberrypi Adapter "system.adapter.backitup.0" is started -
@kimukao sagte in Kein Update mehr möglich mit Node.js 16:
Hat leider auch nicht funktioniert:
Da war auch nicht zu erwarten. Immerhin gibt es mehr Meldungen:
npm ERR! builtins is not a function npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-06T11_28_01_889Z-debug-0.logWas steht denn in dem genannten log drin?
-
@thomas-braun said in Kein Update mehr möglich mit Node.js 16:
/home/iobroker/.npm/_logs/2022-09-06T11_28_01_889Z-debug-0.log
Kenne mich zu wenig aus. Wie liest man das denn aus?
-
@kimukao sagte in Kein Update mehr möglich mit Node.js 16:
/home/iobroker/.npm/_logs/2022-09-06T11_28_01_889Z-debug-0.log
Mit einem pager z. B.
less -R /home/iobroker/.npm/_logs/2022-09-06T11_28_01_889Z-debug-0.log -
0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@8.15.0 2 info using node@v16.17.0 3 timing npm:load:whichnode Completed in 1ms 4 timing config:load:defaults Completed in 4ms 5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 2ms 6 timing config:load:builtin Completed in 4ms 7 timing config:load:cli Completed in 6ms 8 timing config:load:env Completed in 1ms 9 timing config:load:file:/opt/iobroker/.npmrc Completed in 1ms 10 timing config:load:project Completed in 4ms 11 timing config:load:file:/home/iobroker/.npmrc Completed in 0ms 12 timing config:load:user Completed in 1ms 13 timing config:load:file:/usr/etc/npmrc Completed in 0ms 14 timing config:load:global Completed in 1ms 15 timing config:load:validate Completed in 0ms 16 timing config:load:credentials Completed in 3ms 17 timing config:load:setEnvs Completed in 3ms 18 timing config:load Completed in 28ms 19 timing npm:load:configload Completed in 29ms 20 timing npm:load:mkdirpcache Completed in 2ms 21 timing npm:load:mkdirplogs Completed in 1ms 22 verbose title npm install iobroker.backitup@2.4.10 23 verbose argv "install" "--save-exact" "iobroker.backitup@2.4.10" 24 timing npm:load:setTitle Completed in 4ms 25 timing config:load:flatten Completed in 9ms 26 timing npm:load:display Completed in 11ms 27 verbose logfile logs-max:10 dir:/home/iobroker/.npm/_logs 28 verbose logfile /home/iobroker/.npm/_logs/2022-09-06T11_28_01_889Z-debug-0.log 29 timing npm:load:logFile Completed in 13ms 30 timing npm:load:timers Completed in 1ms 31 timing npm:load:configScope Completed in 0ms 32 timing npm:load Completed in 63ms 33 timing arborist:ctor Completed in 2ms 34 silly logfile start cleaning logs, removing 2 files 35 silly logfile done cleaning log files 36 timing idealTree:init Completed in 3489ms 37 timing idealTree Completed in 3494ms 38 timing command:install Completed in 3530ms 39 verbose stack TypeError: builtins is not a function 39 verbose stack at validate (/usr/lib/node_modules/npm/node_modules/validate-npm-package-name/lib/index.js:55:3) 39 verbose stack at Result.setName (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:129:17) 39 verbose stack at new Result (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:120:10) 39 verbose stack at resolve (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:57:15) 39 verbose stack at npa (/usr/lib/node_modules/npm/node_modules/npm-package-arg/lib/npa.js:51:10) 39 verbose stack at /usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:542:50 : -
Das geht noch weiter.
'Bild Runter'-Taste
