Beim Update von Adaptern stürzt der ioBroker ab
-
Ist jetzt nur noch gerate von mir.
npm uninstall iobroker.mihome-vacuumIch glaube der war in dem anderen Fall der Verursacher. Bzw. eine der Dependencies.
-
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
npm ls zlib -
@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:
npm uninstall iobroker.mihome-vacuum
Das hat leider nicht geklappt.
Bevor die Deinstallation startet habe ich wieder ein Haufen an Hinweisen erhalten...flo@ioBrokerdebian:/opt/iobroker$ npm uninstall iobroker.mihome-vacuum [sudo] Passwort für flo: 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/ioBroker/ioBroker.vis-2.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@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 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 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 json3@3.3.2: Please use the native JSON object instead of JSON 3 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@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 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 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@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 1 npm error path /opt/iobroker/node_modules/node-libcurl npm error command failed npm error command sh -c node-pre-gyp install --fallback-to-build npm error Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node --module_name=node_libcurl --module_path=/opt/iobroker/node_modules/node-libcurl/lib/binding --napi_version=9 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v115' (1) npm error node-pre-gyp info it worked if it ends with ok npm error node-pre-gyp info using node-pre-gyp@1.0.10 npm error node-pre-gyp info using node@20.16.0 | linux | x64 npm error node-pre-gyp info check checked for "/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node" (not found) npm error node-pre-gyp http GET https://github.com/JCMais/node-libcurl/releases/download/v3.0.0/node_libcurl-v3.0.0-node-v115-linux-x64-glibc.tar.gz npm error node-pre-gyp ERR! install response status 404 Not Found on https://github.com/JCMais/node-libcurl/releases/download/v3.0.0/node_libcurl-v3.0.0-node-v115-linux-x64-glibc.tar.gz npm error node-pre-gyp WARN Pre-built binaries not installable for node-libcurl@3.0.0 and node@20.16.0 (node-v115 ABI, glibc) (falling back to source compile with node-gyp) npm error node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/JCMais/node-libcurl/releases/download/v3.0.0/node_libcurl-v3.0.0-node-v115-linux-x64-glibc.tar.gz npm error gyp info it worked if it ends with ok npm error gyp info using node-gyp@10.1.0 npm error gyp info using node@20.16.0 | linux | x64 npm error gyp info ok npm error gyp info it worked if it ends with ok npm error gyp info using node-gyp@10.1.0 npm error gyp info using node@20.16.0 | linux | x64 npm error gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3" npm error gyp http GET https://nodejs.org/download/release/v20.16.0/node-v20.16.0-headers.tar.gz npm error gyp http 200 https://nodejs.org/download/release/v20.16.0/node-v20.16.0-headers.tar.gz npm error gyp http GET https://nodejs.org/download/release/v20.16.0/SHASUMS256.txt npm error gyp http 200 https://nodejs.org/download/release/v20.16.0/SHASUMS256.txt npm error gyp info spawn /usr/bin/python3 npm error gyp info spawn args [ npm error gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py', npm error gyp info spawn args 'binding.gyp', npm error gyp info spawn args '-f', npm error gyp info spawn args 'make', npm error gyp info spawn args '-I', npm error gyp info spawn args '/opt/iobroker/node_modules/node-libcurl/build/config.gypi', npm error gyp info spawn args '-I', npm error gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi', npm error gyp info spawn args '-I', npm error gyp info spawn args '/home/iobroker/.cache/node-gyp/20.16.0/include/node/common.gypi', npm error gyp info spawn args '-Dlibrary=shared_library', npm error gyp info spawn args '-Dvisibility=default', npm error gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/20.16.0', npm error gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp', npm error gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/20.16.0/<(target_arch)/node.lib', npm error gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/node-libcurl', npm error gyp info spawn args '-Dnode_engine=v8', npm error gyp info spawn args '--depth=.', npm error gyp info spawn args '--no-parallel', npm error gyp info spawn args '--generator-output', npm error gyp info spawn args 'build', npm error gyp info spawn args '-Goutput_dir=.' npm error gyp info spawn args ] npm error Could not run curl-config, please make sure libcurl dev package is installed. npm error Output: /bin/sh: 1: curl-config: not found npm error npm error gyp: Call to 'node /opt/iobroker/node_modules/node-libcurl/scripts/curl-config.js --prefix' returned exit status 1 while in binding.gyp. while trying to load binding.gyp npm error gyp ERR! configure error npm error gyp ERR! stack Error: `gyp` failed with exit code: 1 npm error gyp ERR! stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:297:18) npm error gyp ERR! stack at ChildProcess.emit (node:events:519:28) npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:294:12) npm error gyp ERR! System Linux 6.1.0-23-amd64 npm error gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node" "--module_name=node_libcurl" "--module_path=/opt/iobroker/node_modules/node-libcurl/lib/binding" "--napi_version=9" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v115" npm error gyp ERR! cwd /opt/iobroker/node_modules/node-libcurl npm error gyp ERR! node -v v20.16.0 npm error gyp ERR! node-gyp -v v10.1.0 npm error gyp ERR! not ok npm error node-pre-gyp ERR! build error npm error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node --module_name=node_libcurl --module_path=/opt/iobroker/node_modules/node-libcurl/lib/binding --napi_version=9 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v115' (1) npm error node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-libcurl/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23) npm error node-pre-gyp ERR! stack at ChildProcess.emit (node:events:519:28) npm error node-pre-gyp ERR! stack at maybeClose (node:internal/child_process:1105:16) npm error node-pre-gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:305:5) npm error node-pre-gyp ERR! System Linux 6.1.0-23-amd64 npm error node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-libcurl/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" npm error node-pre-gyp ERR! cwd /opt/iobroker/node_modules/node-libcurl npm error node-pre-gyp ERR! node -v v20.16.0 npm error node-pre-gyp ERR! node-pre-gyp -v v1.0.10 npm error node-pre-gyp ERR! not ok npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-08-20T13_59_25_128Z-debug-0.log flo@ioBrokerdebian:/opt/iobroker$open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:
npm ls zlib
Hier ist noch das Ergebnis von npm ls zlib
flo@ioBrokerdebian:/opt/iobroker$ npm ls zlib [sudo] Passwort für flo: iobroker.inst@2.0.3 /opt/iobroker └─┬ iobroker.mihome-vacuum@3.11.0 └── zlib@1.0.5 flo@ioBrokerdebian:/opt/iobroker$ -
Du hast da nicht nur eine oder zwei Baustellen, das ist eine ausgewachsene Großbaustelle da bei dir...
apt policy libcurl* apt policy libcurl*devEs muss das entsprechende -dev-Paket zu der bei dir installierten Version von libcurl installiert werden.
Zu mihome-vacuum versuch mal ein
iob update iob upgrade iobroker.mihome-vacuum@4.2.0 -
@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:
apt policy libcurl*
apt policy libcurl*devflo@ioBrokerdebian:/opt/iobroker$ apt policy libcurl* apt policy libcurl*dev 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 libcurl3: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: 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 libcurl3-gnutls: 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 libcurl-ocaml: Installiert: (keine) Installationskandidat: 0.9.2-3 Versionstabelle: 0.9.2-3 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages libcurl3-openssl-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl3-gnutls-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: 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 libcurl-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurlpp0: Installiert: (keine) Installationskandidat: 0.8.1-5.1 Versionstabelle: 0.8.1-5.1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages libcurl-ocaml-dev: Installiert: (keine) Installationskandidat: 0.9.2-3 Versionstabelle: 0.9.2-3 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages libcurl-ocaml-80io7: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurlpp-dev: Installiert: (keine) Installationskandidat: 0.8.1-5.1 Versionstabelle: 0.8.1-5.1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages libcurl-ssl-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl3-nss-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl3-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl-ocaml-dev-80io7: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: 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 libcurl3-nss: 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 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 libcurl3-openssl-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl3-gnutls-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: 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 libcurl-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl-ocaml-dev: Installiert: (keine) Installationskandidat: 0.9.2-3 Versionstabelle: 0.9.2-3 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages libcurlpp-dev: Installiert: (keine) Installationskandidat: 0.8.1-5.1 Versionstabelle: 0.8.1-5.1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages libcurl-ssl-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl3-nss-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl3-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: libcurl4-dev: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: 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 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$ -
-
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
apt policy libcurl*
Also libcurl4...
apt policy libcurl4* -
@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:
iob update iob upgrade iobroker.mihome-vacuum@4.2.0zeilenweise 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.0iob 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$ -
@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$ -
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
Installier das mal:
libcurl4-openssl-dev
sudo apt install libcurl4-openssl-dev -
@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$ -
sudo apt autoremoveJetzt die Holzhammermethode:
cd /opt/iobroker npm install iobroker.js-controller@6.0.9 --force -
@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:
sudo apt autoremoveJetzt die Holzhammermethode:
cd /opt/iobroker npm install iobroker.js-controller@6.0.9 --forceDas 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$open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
Du kannst die Kiste mal neuinstallieren.
-
@thomas-braun sagte in Beim Update von Adaptern stürzt der ioBroker ab:
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?
-
@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 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
