Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄

[Bastel2021]

@thomas-braun
sorry das ich mich so blöd anstelle aber wie muss ich das genau im Terminal eingeben?

[Thomas Braun]

@bastel2021

So wie es da steht.
Am besten kopieren und einfügen.

[Bastel2021]

sorry!

Spoiler

pi@raspberrypi:~ $

sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null

uname -m && type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && pwd && sudo apt-get update &> /dev/null && sudo apt-get update && apt-cache policy nodejs
armv7l
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
v14.21.2
v14.21.2
6.14.17
6.14.17
internal/modules/cjs/loader.js:905
throw err;
^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
at Function.Module._load (internal/modules/cjs/loader.js:746:27)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
pi@raspberrypi:~ $

[Thomas Braun]

@bastel2021

Zuerstmal auf nodeJS@16 gehen.
Siehe meine Signatur.

[Bastel2021]

@thomas-braun
du schreibst dort ja von einem sauberen "npm tree"
der sieht bei mir aber nicht sauber aus!

Spoiler

pi@raspberrypi:~ $ cd /opt/iobroker
pi@raspberrypi:/opt/iobroker $ npm ls | grep -E 'github|ERR'
npm ERR! missing: iobroker.js-controller@4.0.21, required by iobroker.inst@3.0.0
npm ERR! extraneous: iobroker.js-controller@4.0.21 /opt/iobroker/node_modules/iobroker.js-controller
│ │ │ ├── github-from-package@0.0.0
pi@raspberrypi:/opt/iobroker $

kann ich damit dann weitermachen?

[Thomas Braun]

@bastel2021

Ja. Oder direkt in die /etc/apt/sources.list.d/nodesource.list die 16 eintragen.

[Bastel2021]

@thomas-braun
okay das hat glaube ich geklappt!
Und jetzt?

[Thomas Braun]

@bastel2021

Nicht glauben, prüfen.

uname -m && type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v && whoami && groups && echo $XDG_SESSION_TYPE && pwd && sudo apt-get update &> /dev/null && sudo apt-get update && apt-cache policy nodejs

[Bastel2021]

das wird ausgegeben

Spoiler

pi@raspberrypi:~ $ uname -m && type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v && whoami && groups && echo $XDG_SESSION_TYPE && pwd && sudo apt-get update &> /dev/null && sudo apt-get update && apt-cache policy nodejs
armv7l
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
v16.19.0
v16.19.0
8.19.3
8.19.3
pi
pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker
tty
/home/pi
OK:1 http://archive.raspberrypi.org/debian bullseye InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
OK:3 https://deb.nodesource.com/node_16.x bullseye InRelease
OK:4 https://phoscon.de/apt/deconz bullseye InRelease
Paketlisten werden gelesen… Fertig
nodejs:
Installiert: 16.19.0-deb-1nodesource1
Installationskandidat: 16.19.0-deb-1nodesource1
Versionstabelle:
*** 16.19.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 Packages
pi@raspberrypi:~ $

[Thomas Braun]

@bastel2021

sudo -H -u iobroker npm cache clear
cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controller

[Bastel2021]

ich glaube das sieht nicht so gut aus

Spoiler

pi@raspberrypi:~ $ sudo -H -u iobroker npm cache clear

cd /opt/iobroker

sudo -H -u iobroker npm install iobroker.js-controller
npm ERR! As of npm@5, the npm cache self-heals from corruption issues
npm ERR! by treating integrity mismatches as cache misses. As a result,
npm ERR! data extracted from the cache is guaranteed to be valid. If you
npm ERR! want to make sure everything is consistent, use npm cache verify
npm ERR! instead. Deleting the cache can only make npm go slower, and is
npm ERR! not likely to correct any problems you may be encountering!
npm ERR!
npm ERR! On the other hand, if you're debugging an issue with the installer,
npm ERR! or race conditions that depend on the timing of writing to an empty
npm ERR! cache, you can use npm install --cache /tmp/empty-cache to use a
npm ERR! temporary cache instead of nuking the actual one.
npm ERR!
npm ERR! If you're sure you want to delete the entire cache, rerun this command
npm ERR! with --force.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/iobroker/.npm/_logs/2023-01-15T15_51_24_403Z-debug-0.log
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code 22
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c -- node iobroker.js setup first
npm ERR! No connection to databases possible ...

npm ERR! A complete log of this run can be found in:
npm ERR! /home/iobroker/.npm/_logs/2023-01-15T15_51_26_424Z-debug-0.log
pi@raspberrypi:/opt/iobroker $

[Thomas Braun]

@bastel2021

Sorry, muss

sudo -H -u iobroker npm cache clear --force

lauten.

[Bastel2021]

@thomas-braun

Spoiler

pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm cache clear --forcecd /opt/iobroker

sudo -H -u iobroker npm install iobroker.js-controller
npm WARN Not Found: /opt/iobroker
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code 22
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c -- node iobroker.js setup first
npm ERR! No connection to databases possible ...

npm ERR! A complete log of this run can be found in:
npm ERR! /home/iobroker/.npm/_logs/2023-01-15T15_59_37_585Z-debug-0.log
pi@raspberrypi:/opt/iobroker $

[Thomas Braun]

@bastel2021

iobroker fix

[Bastel2021]

@thomas-braun sagte in IoBroker ist nicht mehr über Browser erreichbar:

iobroker fix

[Bastel2021]

@thomas-braun

Spoiler

pi@raspberrypi:~ $ iobroker fix
library: loaded
Library version=2022-12-09
ioBroker is not installed in /opt/iobroker! Cannot fix anything...
pi@raspberrypi:~ $

[Thomas Braun]

@bastel2021

Bitte statt der Spoiler lieber CodeTags verwenden. Danke.

[Bastel2021]

@thomas-braun

pi@raspberrypi:~ $ iobroker fix
library: loaded
Library version=2022-12-09
ioBroker is not installed in /opt/iobroker! Cannot fix anything...
pi@raspberrypi:~ $

[Thomas Braun]

@bastel2021

cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controller

[Bastel2021]

@thomas-braun

pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code 22
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c -- node iobroker.js setup first
npm ERR! No connection to databases possible ...

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2023-01-15T16_15_40_711Z-debug-0.log
pi@raspberrypi:/opt/iobroker $