Nach Nodejs Update kein Adapter mehr updatebar
-
Lief der iobroker eigentlich die ganze Zeit? Knips den aus, wenn du am npm tree bastelst.
-
nein der war die ganze Zeit aus, wollte den nur bis morgen wieder an machen wenn ich weiter mache.
-
Beim iobroker Start werden Module neukompiliert.
Ich vermute stark, da ist in der Vergangenheit mal mit sudo oder gar vollem root was installiert worden und jetzt ist da einiges verbogen.
Edit: Gerade nochmal hochgescrollt... Du warst ja tatsächlich als root unterwegs. Würde meine Vermutung stützen.
-
so habe iobroker gestoppt, alle Dateien mit kryptischen Endungen gelöscht und versucht alexa2 upzudaten.
user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade alexa2 --debug This upgrade of "alexa2" will introduce the following changes: ========================================================================== -> 3.18.6: Fix deviceStop sequence command -> 3.18.5: Fix crash case reported by Sentry Add image for Fire Cube -> 3.18.3: Fix doNotDisturb and doNotDisturb for All devices Update do not disturb status after set for all devices preserve a changed name for a "This device" device object -> 3.18.2: Enable commands again for Apps with type A2TF17PFR55MTB - will only work sometimes as it seems ========================================================================== Would you like to upgrade alexa2 from @3.18.1 to @3.18.6 now? [(y)es, (n)o]: y Update alexa2 from @3.18.1 to @3.18.6 NPM version: 8.11.0 Installing iobroker.alexa2@3.18.6... (System call) 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 crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in. npm WARN deprecated node-xmpp-tls-connect@1.0.1: this package is deprecated please use https://github.com/xmppjs/xmpp.js 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 har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated node-xmpp-core@5.0.9: this package is deprecated please use https://github.com/xmppjs/xmpp.js npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API 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 multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. 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 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 querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. 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 uuid@3.3.2: 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated appium-logger@2.1.0: Moved into appium-support npm WARN deprecated node-xmpp-client@3.2.0: this package is deprecated please use https://www.npmjs.com/package/@xmpp/client npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! code 1 npm ERR! path /opt/iobroker/node_modules/openzwave-shared npm ERR! command failed npm ERR! command sh -c node-gyp rebuild npm ERR! make: Entering directory '/opt/iobroker/node_modules/openzwave-shared/build' npm ERR! CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o npm ERR! openzwave_shared.target.mk:150: recipe for target 'Release/obj.target/openzwave_shared/src/callbacks.o' failed npm ERR! make: Leaving directory '/opt/iobroker/node_modules/openzwave-shared/build' npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@8.4.1 npm ERR! gyp info using node@16.16.0 | linux | x64 npm ERR! gyp info find Python using Python version 3.6.9 found at "/usr/bin/python3" npm ERR! gyp info spawn /usr/bin/python3 npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py', npm ERR! gyp info spawn args 'binding.gyp', npm ERR! gyp info spawn args '-f', npm ERR! gyp info spawn args 'make', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/opt/iobroker/node_modules/openzwave-shared/build/config.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/opt/iobroker/node_modules/node-gyp/addon.gypi', npm ERR! gyp info spawn args '-I', npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/16.16.0/include/node/common.gypi', npm ERR! gyp info spawn args '-Dlibrary=shared_library', npm ERR! gyp info spawn args '-Dvisibility=default', npm ERR! gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/16.16.0', npm ERR! gyp info spawn args '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp', npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.16.0/<(target_arch)/node.lib', npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/openzwave-shared', npm ERR! gyp info spawn args '-Dnode_engine=v8', npm ERR! gyp info spawn args '--depth=.', npm ERR! gyp info spawn args '--no-parallel', npm ERR! gyp info spawn args '--generator-output', npm ERR! gyp info spawn args 'build', npm ERR! gyp info spawn args '-Goutput_dir=.' npm ERR! gyp info spawn args ] npm ERR! gyp info spawn make npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] npm ERR! In file included from /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8.h:30:0, npm ERR! from ../src/openzwave.hpp:27, npm ERR! from ../src/callbacks.cc:18: npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’: npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’ npm ERR! !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data); npm ERR! ^~~~~~~~~~~ npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: note: suggested alternative: ‘remove_cv’ npm ERR! !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data); npm ERR! ^~~~~~~~~~~ npm ERR! remove_cv npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’ npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: note: suggested alternative: ‘remove_cv’ npm ERR! !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data); npm ERR! ^~~~~~~~~~~ npm ERR! remove_cv npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:50: error: template argument 2 is invalid npm ERR! !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data); npm ERR! ^ npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:63: error: ‘::Perform’ has not been declared npm ERR! !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data); npm ERR! ^~~~~~~ npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:63: note: suggested alternative: ‘perror’ npm ERR! !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data); npm ERR! ^~~~~~~ npm ERR! perror npm ERR! make: *** [Release/obj.target/openzwave_shared/src/callbacks.o] Error 1 npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2 npm ERR! gyp ERR! stack at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:527:28) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) npm ERR! gyp ERR! System Linux 4.15.0-189-generic npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild" npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared npm ERR! gyp ERR! node -v v16.16.0 npm ERR! gyp ERR! node-gyp -v v8.4.1 npm ERR! gyp ERR! not ok npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-22T08_24_18_272Z-debug-0.log upload [27] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/alexa.png alexa.png image/png upload [20] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_dot3.png icons/echo_dot3.png image/png upload [19] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_dot4.png icons/echo_dot4.png image/png upload [18] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_flex.png icons/echo_flex.png image/png upload [17] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_plus2.png icons/echo_plus2.png image/png upload [16] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show.png icons/echo_show.png image/png upload [15] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show2.png icons/echo_show2.png image/png upload [14] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show5.png icons/echo_show5.png image/png upload [13] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_studio.png icons/echo_studio.png image/png upload [12] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_sub.png icons/echo_sub.png image/png upload [11] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/firetab.png icons/firetab.png image/png upload [10] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/firetv.png icons/firetv.png image/png upload [9] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/microphone.png icons/microphone.png image/png upload [8] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/multiroom.png icons/multiroom.png image/png upload [7] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/raspi.png icons/raspi.png image/png upload [6] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/reverb.png icons/reverb.png image/png upload [5] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/sonos.png icons/sonos.png image/png upload [4] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/spot.png icons/spot.png image/png upload [3] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/index_m.html index_m.html text/html upload [2] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/info.png info.png image/png upload [1] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/warning.png warning.png image/png upload [0] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/words.js words.js application/javascript^[Sorry, try again.open Request’s Past, Present and Future #3142
open Request’s Past, Present and Future #3142
open Request’s Past, Present and Future #3142
-
-
@thomas-braun said in Nach Nodejs Update kein Adapter mehr updatebar:
apt policy build-essential
ja
user@iobroker-ubuntu:/opt/iobroker$ apt policy build-essential build-essential: Installiert: 12.4ubuntu1 Installationskandidat: 12.4ubuntu1 Versionstabelle: *** 12.4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status -
Dann lösch den cache mal.
-
-
-
@thomas-braun said in Nach Nodejs Update kein Adapter mehr updatebar:
sudo -u iobroker npm cache clear --force
user@iobroker-ubuntu:/opt/iobroker$ sudo -u iobroker npm cache clear --force npm WARN logfile could not be created: Error: EACCES: permission denied, open '/home/user/.npm/_logs/2022-07-22T09_05_23_231Z-debug-0.log' npm WARN using --force Recommended protections disabled. -
sudo -H -u iobroker npm cache clear --force -
user@iobroker-ubuntu:/opt/iobroker$ sudo -H -u iobroker npm cache clear --force npm WARN using --force Recommended protections disabled.und jetzt nochmal versuchen alexa2 upzudaten?
-
Nein, der Show Stopper liegt bei openzwave-shared.
Das Modul bzw. den zugehörigen Adapter nochmal sauber installieren/rebuilden. -
möchte jetzt iobroker nicht starten, daher würde ich den Adapter(wird nicht mehr benötigt) über die Konsole löschen.
So?iobroker del openzwave-shared -
Ich vermute der kommt als Dependency aus einem Adapter. Ich würde den ganzen Adapter rauswerfen.
Schau wo openzwave-shared hängt:cd /opt/iobroker npm ls openzwave-shared -
Ich hätte ja das ganze node-modules Verzeichnis gelöscht, inkl. package-lock.json und dann mit npm install neu aufbauen lassen. Wenn du eh eine Datensicherung hast, solltest du ja auch auf den Stand zurückkehren können. Bei mir hat diese Radikalkur jedenfalls geholfen, einen fehlerfreien Baum zu bekommen.
-
der kommt vom zwave adapter. Den lösche ich dann mit: iobroker del zwave2?
user@iobroker-ubuntu:/opt/iobroker$ npm ls openzwave-shared [sudo] password for user: iobroker.inst@2.0.2 /opt/iobroker └─┬ iobroker.zwave@2.0.1 └── openzwave-shared@1.7.2 -
wie würde ich da vorgehen?
-
@tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:
wie würde ich da vorgehen?
also in das /opt/iobroker Verzeichnis wechseln.
IOB stoppen natürlich:iob stopcd /opt/iobrokerkomplettes node_modules Verzeichnis löschen oder das Verzeichnis umbenennen
sudo rm -rf node_modulesbzw.
sudo mv node_modules node_modules.baketwaige package-lock.json löschen
sudo rm package-lock.jsonDen cache sicherheitshalber noch leeren:
npm cache clean --forceDann das node_modules neu aufbauen lassen:
npm installDie ganzen Informationen über die Adapter und deren Abhängigkeiten stehen in der package.json.
Eine datensicherung oder ein Image würde ich aber in jedem Fall machen, falls was nicht geht. Ist aber noch schneller, als das ganze System neu aufzubauen.
zum Schluss in dem Verzeichnis /opt/iobroker noch den Befehl
npm listund schauen, ob Du einen sauberen Baum hast. npm cache hast ja soweit ich sehe schon gelöscht.
-
iobroker del zwave
