Nach Nodejs Update kein Adapter mehr updatebar
-
-
@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 -
zwave gelöscht und alexa2 erneut versucht zu installieren
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 ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src npm ERR! dest /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src' -> '/opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-22T11_15_10_431Z-debug-0.log host.iobroker-ubuntu Cannot install iobroker.alexa2@3.18.6: 217open Request’s Past, Present and Future #3142
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
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
@tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:
ENOTEMPTY: directory not empty, rename /opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src' -> '/opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src
Das Spiel ist immer das gleiche...
rm -rf /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src -
Habe ich gelöscht und wollte Alexa2 installieren, da sagt er mir ist up to date, komisch.
Als ich dann cloud aktualisieren wollte:
user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade cloud --debug This upgrade of "cloud" will introduce the following changes: ========================================================================== -> 4.2.1: Used new version of socket library. ========================================================================== Would you like to upgrade cloud from @4.2.0 to @4.2.1 now? [(y)es, (n)o]: y Update cloud from @4.2.0 to @4.2.1 NPM version: 8.11.0 Installing iobroker.cloud@4.2.1... (System call) npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/abbrev npm ERR! dest /opt/iobroker/node_modules/.abbrev-5eNud0FY npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abbrev' -> '/opt/iobroker/node_modules/.abbrev-5eNud0FY' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-07-22T11_25_03_406Z-debug-0.log host.iobroker-ubuntu Cannot install iobroker.cloud@4.2.1: 217und die ganzen Verzeichnisse mit.xyz sind auf einmal alle wieder da, obwohl iobroker die ganze zeit aus ist.
-
