Neues YouTube-Video: Visualisierung im Devices-Adapter

[peter_pan]

@lessthanmore

Hab ich Probiert, hat leider nichts gebracht. Gibt es noch weitere Hinweise?

Would you like to upgrade admin from @4.2.2 to @5.1.25 now? [(y)es, (n)o]: y
Update admin from @4.2.2 to @5.1.25
host.Server Adapter "system.adapter.admin.0" is stopped.
NPM version: 6.14.15
npm install iobroker.admin@5.1.25 --loglevel error --prefix "/opt/iobroker" (System call)
npm ERR! Cannot read property 'resolve' of undefined

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2021-10-31T10_18_38_439Z-debug.log
upload [13] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript
upload [12] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html
upload [11] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html
upload [10] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [9] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [8] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [7] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [6] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
upload [5] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [4] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/es/translations.json i18n/es/translations.json application/json
upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/i18n/de/translations.json i18n/de/translations.json application/json
upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png
Adapter "admin" updated

Das Log

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   'iobroker.admin@5.1.25',
1 verbose cli   '--loglevel',
1 verbose cli   'error',
1 verbose cli   '--prefix',
1 verbose cli   '/opt/iobroker'
1 verbose cli ]
2 info using npm@6.14.15
3 info using node@v14.18.1
4 verbose npm-session 692ba3ff9c99812d
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData error for iobroker.admin@5.1.25 Cannot read property 'resolve' of undefined
8 timing stage:rollbackFailedOptional Completed in 30ms
9 timing stage:runTopLevelLifecycles Completed in 14664ms
10 verbose stack TypeError: Cannot read property 'resolve' of undefined
10 verbose stack     at regFetch (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/index.js:88:23)
10 verbose stack     at fetchPackument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:42:10)
10 verbose stack     at packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:20:10)
10 verbose stack     at getManifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:22:10)
10 verbose stack     at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:13:10)
10 verbose stack     at Object.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/index.js:17:12)
10 verbose stack     at Object.Fetcher#manifest [as manifest] (/usr/local/lib/node_modules/npm/node_modules/genfun/lib/genfun.js:15:38)
10 verbose stack     at manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetch.js:23:18)
10 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/pacote/manifest.js:24:12
10 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:29:24
10 verbose stack     at Promise._execute (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/debuggability.js:313:9)
10 verbose stack     at Promise._resolveFromExecutor (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:488:18)
10 verbose stack     at new Promise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:79:10)
10 verbose stack     at _inflight (/usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:28:25)
10 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14
10 verbose stack     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
11 verbose cwd /opt/iobroker
12 verbose Linux 5.10.0-9-amd64
13 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker.admin@5.1.25" "--loglevel" "error" "--prefix" "/opt/iobroker"
14 verbose node v14.18.1
15 verbose npm  v6.14.15
16 error Cannot read property 'resolve' of undefined
17 verbose exit [ 1, true ]

[Homoran]

@peter_pan sagte in Probleme beim admin adapter update:

Hab ich Probiert,

wie?

@peter_pan sagte in Probleme beim admin adapter update:

hat leider nichts gebracht. Gibt es noch weitere Hinweise?

was sagt: which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs

[Thomas Braun]

@peter_pan sagte in Probleme beim admin adapter update:

'/usr/local/bin/node

Node (höchstwahrscheinlich) falsch installiert.
Schau in meiner Signatur wie es geht.

[peter_pan]

@thomas-braun

Danke

Das hat geholfen.
Node hab ich komplett runter geworfen und neu installiert. Wohl durch zu viel rum probieren, waren auch 2 verschiedene Node Versionen in unterschiedlichen Ordnern installiert.

Jetzt hat das Update funktioniert.

[Thomas Braun]

@peter_pan
Was sagt denn nun

which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs

[peter_pan]

@thomas-braun

Das ist das Ergebnis

which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v14.18.1
v14.18.1
6.14.15
nodejs:
  Installiert:           14.18.1-deb-1nodesource1
  Installationskandidat: 14.18.1-deb-1nodesource1
  Versionstabelle:
 *** 14.18.1-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     12.22.5~dfsg-2~11u1 500
        500 http://ftp.rrzn.uni-hannover.de/debian/debian stable/main amd64 Packages
        500 http://ftp.de.debian.org/debian stable/main amd64 Packages
     10.24.0~dfsg-1~deb10u1 500
        500 http://security.debian.org stable/updates/main amd64 Packages
        500 http://ftp.at.debian.org/debian buster/main amd64 Packages

[Thomas Braun]

@peter_pan
Es sollten die Releases nicht gemischt werden.
bullseye passt nicht zum buster, was du da wohl eigentlich fährst.

lsb_release -a

und dann die Repositories angleichen.

[peter_pan]

@thomas-braun sagte in Probleme beim admin adapter update:

lsb_release -a

Ich habe das aktuelle Stable Bullseye.

lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

Der unterschied kommt, da ich teilweise mit Namen, teilweise einfach nur stable in der Liste stehen habe. Muss ich noch ändern, aber das System ist aktuell.

[Homoran]

@peter_pan wieso sehe ich keinen Prompt und keine Befehlszeile?

[Thomas Braun]

@peter_pan

500 http://ftp.at.debian.org/debian buster/main amd64 Packages

Also in einer der .list-Dateien aus /etc/apt/sources.list muss noch was von buster drin stehen.