JS-Controller update, was jetzt
-
Konsolentext immer in CodeTags eingebettet posten, nicht als Bildchen aus Terminalistan.
-
ok, wusste nicht mehr wie ich den Text aus der Konsole kopiere.
wenn ich io
iobroker fix
kommt meldung ioBroker is not installed in /opt/iobroker! Cannnot fix anything..
was kann ich machen?
Gruss
Silbroker
-
-
pi@raspberrypi:/opt/iobroker $ iobroker fix library: loaded Library version=2022-06-15 ioBroker is not installed in /opt/iobroker! Cannot fix anything...der ander Text kann ich nicht mehr kopieren
Wie bist du da sonst unterwegs?
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs -
Wie bist du da sonst unterwegs?
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs -
@silbroker sagte in JS-Controller update, was jetzt:
bekomme ich keine Antwort vom Raspberry
Das ist Linuxisch für: 'Alles i.O., Kommando erfolgreich ausgeführt'.
-
pi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs ln: failed to create symbolic link '/usr/bin/nodejs': File exists pi@raspberrypi:~ $ pi@raspberrypi:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.19.0 v12.19.0 6.14.8 internal/modules/cjs/loader.js:834 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:831:15) at Function.Module._load (internal/modules/cjs/loader.js:687:27) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) at internal/main/run_main_module.js:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } pi@raspberrypi:~ $ -
pi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs ln: failed to create symbolic link '/usr/bin/nodejs': File exists pi@raspberrypi:~ $ pi@raspberrypi:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.19.0 v12.19.0 6.14.8 internal/modules/cjs/loader.js:834 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:831:15) at Function.Module._load (internal/modules/cjs/loader.js:687:27) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12) at internal/main/run_main_module.js:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } pi@raspberrypi:~ $Zuerst mal die angegammelte, tote nodejs@12 Installation in die Gegenwart holen. Node@16 ist angesagt.
Also seit November 2020 das System nicht mehr angepackt?
Ist der Rest auch so verfallen? -
Zuerst mal die angegammelte, tote nodejs@12 Installation in die Gegenwart holen. Node@16 ist angesagt.
Also seit November 2020 das System nicht mehr angepackt?
Ist der Rest auch so verfallen?pi@raspberrypi:~ $ curl -sL https:deb.nodesource.com/setup_16.x | sudo -E bash - pi@raspberrypi:~ $ sudo apt install -y nodejs Reading package lists... Done Building dependency tree Reading state information... Done nodejs is already the newest version (12.19.0-1nodesource1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.wiso sagt er 12.19 sei due neueste?
-
pi@raspberrypi:~ $ curl -sL https:deb.nodesource.com/setup_16.x | sudo -E bash - pi@raspberrypi:~ $ sudo apt install -y nodejs Reading package lists... Done Building dependency tree Reading state information... Done nodejs is already the newest version (12.19.0-1nodesource1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.wiso sagt er 12.19 sei due neueste?
sudo apt update apt policy nodejs -
sudo apt update apt policy nodejspi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done 191 packages can be upgraded. Run 'apt list --upgradable' to see them. pi@raspberrypi:~ $ apt policy nodejs nodejs: Installed: 12.19.0-1nodesource1 Candidate: 12.22.12-deb-1nodesource1 Version table: 12.22.12-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages *** 12.19.0-1nodesource1 100 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packagesdas heist?
-
pi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done 191 packages can be upgraded. Run 'apt list --upgradable' to see them. pi@raspberrypi:~ $ apt policy nodejs nodejs: Installed: 12.19.0-1nodesource1 Candidate: 12.22.12-deb-1nodesource1 Version table: 12.22.12-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages *** 12.19.0-1nodesource1 100 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packagesdas heist?
@silbroker sagte in JS-Controller update, was jetzt:
191 packages can be upgraded.
Das heißt, dass du zunächst mal den Stau da auflösen wirst.
sudo apt update sudo apt full-upgrade sudo rebootDann nodejs@16 installieren und dann schauen wir mal weiter nach dem ioBroker.
-
@silbroker sagte in JS-Controller update, was jetzt:
191 packages can be upgraded.
Das heißt, dass du zunächst mal den Stau da auflösen wirst.
sudo apt update sudo apt full-upgrade sudo rebootDann nodejs@16 installieren und dann schauen wir mal weiter nach dem ioBroker.
pi@raspberrypi:~ $ curl -sL https:deb.nodesource.com/setup_16.x | sudo -E bash - pi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. pi@raspberrypi:~ $ apt policy nodejs nodejs: Installed: 12.22.12-deb-1nodesource1 Candidate: 12.22.12-deb-1nodesource1 Version table: *** 12.22.12-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@raspberrypi:~ $jetzt habe ich 12.22.12
-
pi@raspberrypi:~ $ curl -sL https:deb.nodesource.com/setup_16.x | sudo -E bash - pi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. pi@raspberrypi:~ $ apt policy nodejs nodejs: Installed: 12.22.12-deb-1nodesource1 Candidate: 12.22.12-deb-1nodesource1 Version table: *** 12.22.12-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@raspberrypi:~ $jetzt habe ich 12.22.12
sudo apt update apt policy nodejs -
pi@raspberrypi:~ $ curl -sL https:deb.nodesource.com/setup_16.x | sudo -E bash - pi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 http://archive.raspberrypi.org/debian buster InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. pi@raspberrypi:~ $ apt policy nodejs nodejs: Installed: 12.22.12-deb-1nodesource1 Candidate: 12.22.12-deb-1nodesource1 Version table: *** 12.22.12-deb-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@raspberrypi:~ $jetzt habe ich 12.22.12
-
-
pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/nodesource.list deb https://deb.nodesource.com/node_12.x buster main deb-src https://deb.nodesource.com/node_12.x buster mainso?
Nach dem Installationsskript für nodejs16 sollte die eigentlich so aussehen:
deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye mainWas sagt denn:
curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bashso?
-
Nach dem Installationsskript für nodejs16 sollte die eigentlich so aussehen:
deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x bullseye mainWas sagt denn:
curl -sL https://deb.nodesource.com/setup_16.x | sudo -E bashso?
pi@raspberrypi:~ $ sudo apt install -y nodejs Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: nodejs 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 24.2 MB of archives. After this operation, 2,727 kB of additional disk space will be used. Get:1 https://deb.nodesource.com/node_16.x buster/main armhf nodejs armhf 16.18.0-deb-1nodesource1 [24.2 MB] Fetched 24.2 MB in 2s (10.3 MB/s) apt-listchanges: Reading changelogs... (Reading database ... 57436 files and directories currently installed.) Preparing to unpack .../nodejs_16.18.0-deb-1nodesource1_armhf.deb ... Unpacking nodejs (16.18.0-deb-1nodesource1) over (14.20.1-deb-1nodesource1) ... Setting up nodejs (16.18.0-deb-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/nodesource.list deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main pi@raspberrypi:~ $jetzt ist gegangen.
-
pi@raspberrypi:~ $ sudo apt install -y nodejs Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: nodejs 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 24.2 MB of archives. After this operation, 2,727 kB of additional disk space will be used. Get:1 https://deb.nodesource.com/node_16.x buster/main armhf nodejs armhf 16.18.0-deb-1nodesource1 [24.2 MB] Fetched 24.2 MB in 2s (10.3 MB/s) apt-listchanges: Reading changelogs... (Reading database ... 57436 files and directories currently installed.) Preparing to unpack .../nodejs_16.18.0-deb-1nodesource1_armhf.deb ... Unpacking nodejs (16.18.0-deb-1nodesource1) over (14.20.1-deb-1nodesource1) ... Setting up nodejs (16.18.0-deb-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/nodesource.list deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main pi@raspberrypi:~ $jetzt ist gegangen.
@silbroker sagte in JS-Controller update, was jetzt:
Unpacking nodejs (16.18.0-deb-1nodesource1) over (14.20.1-deb-1nodesource1)
Wo kam denn die 14.20.1 nun her?
-
@silbroker sagte in JS-Controller update, was jetzt:
Unpacking nodejs (16.18.0-deb-1nodesource1) over (14.20.1-deb-1nodesource1)
Wo kam denn die 14.20.1 nun her?
@thomas-braun
habe zuerst die 14er kopiert und ausgeführt
und dann gemerkt das es geht.
Danach noch die 16er
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
601
Online32.9k
Benutzer83.2k
Themen1.3m
Beiträge