Beim Update von Adaptern stürzt der ioBroker ab

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

iob update iob upgrade iobroker.mihome-vacuum@4.2.0

flo@ioBrokerdebian:/opt/iobroker$ iob update
iob upgrade iobroker.mihome-vacuum@4.2.0
node:internal/modules/esm/resolve:215
  const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
                         ^

Error: Cannot find package '/opt/iobroker/node_modules/@iobroker/js-controller-cli/package.json' imported from /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js
    at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
    at packageResolve (node:internal/modules/esm/resolve:841:14)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:315:34)
    at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.16.0
node:internal/modules/esm/resolve:215
  const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
                         ^

Error: Cannot find package '/opt/iobroker/node_modules/@iobroker/js-controller-cli/package.json' imported from /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js
    at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
    at packageResolve (node:internal/modules/esm/resolve:841:14)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:315:34)
    at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.16.0
flo@ioBrokerdebian:/opt/iobroker$

Thomas Braun

@flommaster

iob update
iob upgrade iobroker.mihome-vacuum@4.2.0

zeilenweise einzeln eingeben.

Thomas Braun

@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:

apt policy libcurl*

Also libcurl4...

apt policy libcurl4*

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

@flommaster
iob update
iob upgrade iobroker.mihome-vacuum@4.2.0
zeilenweise einzeln eingeben.

iob update

flo@ioBrokerdebian:/opt/iobroker$ iob update
node:internal/modules/esm/resolve:215
  const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
                         ^

Error: Cannot find package '/opt/iobroker/node_modules/@iobroker/js-controller-cli/package.json' imported from /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js
    at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
    at packageResolve (node:internal/modules/esm/resolve:841:14)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:315:34)
    at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.16.0

iob upgrade iobroker.mihome-vacuum@4.2.0

flo@ioBrokerdebian:/opt/iobroker$ iob upgrade iobroker.mihome-vacuum@4.2.0
node:internal/modules/esm/resolve:215
  const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
                         ^

Error: Cannot find package '/opt/iobroker/node_modules/@iobroker/js-controller-cli/package.json' imported from /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js
    at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
    at packageResolve (node:internal/modules/esm/resolve:841:14)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:315:34)
    at defaultImportModuleDynamically (node:internal/modules/esm/utils:194:31)
    at importModuleDynamicallyCallback (node:internal/modules/esm/utils:216:12) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.16.0
flo@ioBrokerdebian:/opt/iobroker$

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

apt policy libcurl4*

flo@ioBrokerdebian:/opt/iobroker$ apt policy libcurl4*
libcurl4-openssl-dev:
  Installiert:           (keine)
  Installationskandidat: 7.88.1-10+deb12u6
  Versionstabelle:
     7.88.1-10+deb12u6 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     7.88.1-10+deb12u5 500
        500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages
libcurl4:
  Installiert:           7.88.1-10+deb12u6
  Installationskandidat: 7.88.1-10+deb12u6
  Versionstabelle:
 *** 7.88.1-10+deb12u6 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        100 /var/lib/dpkg/status
     7.88.1-10+deb12u5 500
        500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages
libcurl4-gnutls-dev:
  Installiert:           (keine)
  Installationskandidat: 7.88.1-10+deb12u6
  Versionstabelle:
     7.88.1-10+deb12u6 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     7.88.1-10+deb12u5 500
        500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages
libcurl4-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl4-doc:
  Installiert:           (keine)
  Installationskandidat: 7.88.1-10+deb12u6
  Versionstabelle:
     7.88.1-10+deb12u6 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     7.88.1-10+deb12u5 500
        500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages
libcurl4-nss-dev:
  Installiert:           (keine)
  Installationskandidat: 7.88.1-10+deb12u6
  Versionstabelle:
     7.88.1-10+deb12u6 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
     7.88.1-10+deb12u5 500
        500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages
flo@ioBrokerdebian:/opt/iobroker$

Thomas Braun

@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:

Installier das mal:

libcurl4-openssl-dev

sudo apt install libcurl4-openssl-dev

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

sudo apt install libcurl4-openssl-dev

erledigt.

flo@ioBrokerdebian:/opt/iobroker$ sudo apt install libcurl4-openssl-dev
[sudo] Passwort für flo:
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  g++-10 libbpf0 libcbor0 libdns-export1110 libgdk-pixbuf-xlib-2.0-0 libgdk-pixbuf-xlib-2.0-dev libgdk-pixbuf2.0-dev libicu67 libisc-export1105 libjsoncpp24 libldap-2.4-2 liblua5.1-0 libmpdec3 libnspr4 libnss3 libpcre16-3
  libpcre2-posix2 libpcre3-dev libpcre32-3 libpcrecpp0v5 libperl5.32 libprocps8 libpython3.9 libpython3.9-minimal libpython3.9-stdlib libstdc++-10-dev libtiff5 liburing1 libusb-0.1-4 libwebp6 lua-bitop lua-cjson perl-modules-5.32 pigz
  python3.9 python3.9-minimal telnet x11proto-xext-dev
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Vorgeschlagene Pakete:
  libcurl4-doc libidn-dev libkrb5-dev libldap2-dev librtmp-dev libssh2-1-dev libssl-dev
Die folgenden NEUEN Pakete werden installiert:
  libcurl4-openssl-dev
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es müssen 491 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 1.819 kB Plattenplatz zusätzlich benutzt.
Holen:1 http://deb.debian.org/debian bookworm/main amd64 libcurl4-openssl-dev amd64 7.88.1-10+deb12u6 [491 kB]
Es wurden 491 kB in 0 s geholt (2.021 kB/s).
Vormals nicht ausgewähltes Paket libcurl4-openssl-dev:amd64 wird gewählt.
(Lese Datenbank ... 63533 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libcurl4-openssl-dev_7.88.1-10+deb12u6_amd64.deb ...
Entpacken von libcurl4-openssl-dev:amd64 (7.88.1-10+deb12u6) ...
libcurl4-openssl-dev:amd64 (7.88.1-10+deb12u6) wird eingerichtet ...
Trigger für man-db (2.11.2-2) werden verarbeitet ...
flo@ioBrokerdebian:/opt/iobroker$

Thomas Braun

@flommaster

sudo apt autoremove

Jetzt die Holzhammermethode:

cd /opt/iobroker
npm install iobroker.js-controller@6.0.9 --force

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

@flommaster
sudo apt autoremove
Jetzt die Holzhammermethode:
cd /opt/iobroker
npm install iobroker.js-controller@6.0.9 --force

Das klappt leider auch nicht.
Soll ich mal ein downgrade auf die Version 5.x versuchen?


flo@ioBrokerdebian:/opt/iobroker$ cd /opt/iobroker
npm install iobroker.js-controller@6.0.9 --force
npm warn using --force Recommended protections disabled.
npm warn skipping integrity check for git dependency ssh://git@github.com/ioBroker/ioBroker.vis-2.git
npm warn skipping integrity check for git dependency ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.git
npm warn skipping integrity check for git dependency ssh://git@github.com/peterbaumert/ioBroker.vofo-speedtest.git
npm warn skipping integrity check for git dependency ssh://git@github.com/Scrounger/ioBroker.vis-materialdesign.git
npm warn skipping integrity check for git dependency ssh://git@github.com/ioBroker/ioBroker.vis-2-widgets-material.git
npm warn skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.sourceanalytix.git
npm warn skipping integrity check for git dependency ssh://git@github.com/aendue/ioBroker.reolink.git
npm warn skipping integrity check for git dependency ssh://git@github.com/iobroker-community-adapters/ioBroker.ical.git
npm warn skipping integrity check for git dependency ssh://git@github.com/TA2k/ioBroker.gartenbewaesserung.git
npm warn skipping integrity check for git dependency ssh://git@github.com/SKB-CGN/ioBroker.energiefluss.git
npm warn skipping integrity check for git dependency ssh://git@github.com/WLAN-Kabel/ioBroker.calendar.git
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 inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated uid-number@0.0.6: This package is no longer supported.
npm warn deprecated npmlog@5.0.1: This package is no longer supported.
npm warn deprecated npmlog@5.0.1: This package is no longer supported.
npm warn deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated q@1.1.2: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead
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 google-p12-pem@4.0.1: Package is no longer maintained
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 google-p12-pem@3.1.4: Package is no longer maintained
npm warn deprecated gauge@3.0.2: This package is no longer supported.
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 gauge@4.0.4: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated later@1.2.0: Please upgrade to the maintained and new drop-in replacement @breejs/later at https://github.com/breejs/later 🚀 Thanks and happy hacking! 🚀  @niftylettuce
npm error code 127
npm error path /opt/iobroker/node_modules/zlib
npm error command failed
npm error command sh -c node-waf clean || true; node-waf configure build
npm error sh: 1: node-waf: not found
npm error sh: 1: node-waf: not found
npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-08-20T18_16_12_082Z-debug-0.log
flo@ioBrokerdebian:/opt/iobroker$

Thomas Braun

@flommaster

Du kannst die Kiste mal neuinstallieren.

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

@flommaster

Du kannst die Kiste mal neuinstallieren.

Alles klar.
Dann bestelle ich mir gleich nen neuen NUC mit 8GB RAM und setze den komplett neu auf.
Gibt es aktuelle Empfehlungen?

Ein Backup mit meinen Daten kann ich danach aber einspielen?

Thomas Braun

@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:

Ein Backup mit meinen Daten kann ich danach aber einspielen?

Möglich. Vermutlich knallst du dir den Murks aber nur wieder rein.

Shadowhunter23

@flommaster
https://itreturn.at/HP-EliteDesk-800-G4-Tiny-/-Intel-i5-8500-360GHz-/-256-GB-SSD-/-16GB-RAM-/-Windows-11-Home-/-12-Monate-Garantie

Aber kein HDMI für Monitor.

BananaJoe

@shadowhunter23 wer braucht schon einen Monitor da dran ... ja ist beim ersten Installieren ganz nett ...
Und ansonsten noch mal 5 Euro für einen Adapter: https://www.amazon.de/dp/B08XKB7PRP

flommaster

@shadowhunter23 sagte in Beim Update von Adaptern stürzt der ioBroker ab:

@flommaster
https://itreturn.at/HP-EliteDesk-800-G4-Tiny-/-Intel-i5-8500-360GHz-/-256-GB-SSD-/-16GB-RAM-/-Windows-11-Home-/-12-Monate-Garantie

Aber kein HDMI für Monitor.

Danke für den Tipp!

Shadowhunter23

@bananajoe
Für mich ist das schon klar aber jemand der sich nicht direkt auskennt dem hilft es vielleicht. Lieber ein Hinweis zuviel als gar nichts...

flommaster

@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:

@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:

Ein Backup mit meinen Daten kann ich danach aber einspielen?

Möglich. Vermutlich knallst du dir den Murks aber nur wieder rein.

Ich will kein komplettes Backup einspielen, nur die Daten und Einstellungen vom IoBroker.

Thomas Braun

@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:

nur die Daten und Einstellungen vom IoBroker.

Vermutlich ist da aber der vermurkste Kram drin.
Musste ausprobieren, ob das Backup was taugt.

flommaster

@shadowhunter23

Soll ich den neuen NUC dann gleich mit Windows 11 als OS laufen lassen?

@Homoran
Ein Teil Backup wäre schon echt gut.
Ich habe viele historische Daten und ner sehr aufwändige VIS gebaut… 😩

Thomas Braun

@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:

@shadowhunter23

Soll ich den neuen NUC dann gleich mit Windows 11 als OS laufen lassen?

Natürlich nicht...

@Homoran
Ein Teil Backup wäre schon echt gut.
Ich habe viele historische Daten und ner sehr aufwändige VIS gebaut… 😩

Probier erst mal aus das vorhandene Backup einzuspielen. Wenn das zu Murks führt kann man da immer noch ggfls. einzelne Bereiche rauspuhlen.

Community Forum

NEWS

Beim Update von Adaptern stürzt der ioBroker ab

Support us

667

32.5k

81.8k

1.3m