NEWS
iobroker startet nicht nach node-js Update 16.18.1
-
Hallo zusammen,
mein iobroker startet leider nicht mehr. Habe node-js upgedatet und jetzt will er nicht mehr.
pi@raspberrypi:/opt/iobroker $ node -v v16.18.1
pi@raspberrypi:/opt/iobroker $ iobroker status node:internal/modules/cjs/loader:988 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15) at Function.Module._load (node:internal/modules/cjs/loader:833:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:22:47 { code: 'MODULE_NOT_FOUND', requireStack: [] }
Hat jemand ne Idee, was das Problem sein könnte und, noch besser, eine Lösung
Vielen Dank!
-
Nodejs richtig aktualisiert?
Was sagt:sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt-get update &> /dev/null && sudo apt-get update && apt-cache policy nodejs
-
Läuft auf nem Raspi...
pi@raspberrypi:/opt/iobroker $ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installa tion" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && group s && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt-get update &> /dev/null && sudo apt-get updat e && apt-cache policy nodejs armv7l Kein Docker /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.18.1 v16.18.1 8.19.2 node:internal/modules/cjs/loader:988 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15) at Function.Module._load (node:internal/modules/cjs/loader:833:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:22:47 { code: 'MODULE_NOT_FOUND', requireStack: [] }
-
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller
Danach nochmal die Befehlskette von davor.
-
@thomas-braun said in iobroker startet nicht nach node-js Update 16.18.1:
sudo -H -u iobroker npm install iobroker.js-controller
hatte ich bereits versucht.
pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/abab npm ERR! dest /opt/iobroker/node_modules/.abab-bvmibCm3 npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abab' -> '/opt/iobroker/node_modules/.abab-bvmibCm3' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-11-11T09_49_23_783Z-debug-0.log
-
-
Beim Ausführen erscheint bei jedem Ordner folgendes...
rm: das Entfernen von '/opt/iobroker/node_modules/.sharp-I3mcBL1h/vendor/8.12.2/linux-armv7/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-loader.h' ist nicht möglich: Keine Berechtigung rm: das Entfernen von '/opt/iobroker/node_modules/.sharp-I3mcBL1h/vendor/8.12.2/linux-armv7/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-transform.h' ist nicht möglich: Keine Berechtigung rm: das Entfernen von '/opt/iobroker/node_modules/.sharp-I3mcBL1h/vendor/8.12.2/linux-armv7/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixdata.h' ist nicht möglich: Keine Berechtigung rm: das Entfernen von '/opt/iobroker/node_modules/.sharp-I3mcBL1h/vendor/8.12.2/linux-armv7/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h' ist nicht möglich: Keine Berechtigung rm: das Entfernen von '/opt/iobroker/node_modules/.sharp-I3mcBL1h/vendor/8.12.2/linux-armv7/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-simple-anim.h' ist nicht möglich: Keine Berechtigung rm: das Entfernen von '/opt/iobroker/node_modules/.sharp-I3mcBL1h/vendor/8.12.2/linux-armv7/include/tiffio.h' ist nicht möglich: Keine Berechtigung
-
Dann hast du da mal mit root-Rechten herumgepflügt...
iobroker fix
funktioniert?
Ich vermute sogar, dass du da versucht hast sharp zu installieren und das komplett daneben gegangen ist.
-
@thomas-braun said in iobroker startet nicht nach node-js Update 16.18.1:
iobroker fix
nicht bewusst. Und den fixer hab ich nach dem node-js Update auch drüber laufen lassen. Mach ich grundsätzlich...
Hab ih aber jetzt nochmal drüber gejagt und jetzt konnte ich den Befehl ausführen
sudo -H -u iobroker npm install iobroker.js-controller
pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller 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 @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed. 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 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 querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin. 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 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 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.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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated tough-cookie@0.12.1: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130 npm WARN deprecated appium-logger@2.1.0: Moved into appium-support 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. added 1 package, and changed 1104 packages in 7m 107 packages are looking for funding run `npm fund` for details
-
Und? Lüppt das nun wieder?
-
leider nicht. Ich fürchte da ist jetzt alles am A*sch... Komm jetzt plötzlich nicht mal mehr per SSH auf den Raspi
-
So... Nochmal ab und wieder angestöpselt...
pi@raspberrypi:~ $ iobroker status node:internal/modules/cjs/loader:988 throw err; ^ Error: Cannot find module 'graceful-fs' Require stack: - /opt/iobroker/node_modules/iobroker.js-controller/node_modules/fs-extra/lib/fs /index.js - /opt/iobroker/node_modules/iobroker.js-controller/node_modules/fs-extra/lib/in dex.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:985:15 ) at Function.Module._load (node:internal/modules/cjs/loader:833:27) at Module.require (node:internal/modules/cjs/loader:1057:19) at require (node:internal/modules/cjs/helpers:103:18) at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/nod e_modules/fs-extra/lib/fs/index.js:5:12) at Module._compile (node:internal/modules/cjs/loader:1155:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10) at Module.load (node:internal/modules/cjs/loader:1033:32) at Function.Module._load (node:internal/modules/cjs/loader:868:12) at Module.require (node:internal/modules/cjs/loader:1057:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/fs-extra/lib /fs/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/fs-extra/lib /index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ] }
-
Here we go again.
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller
-
Ansonsten falls Du so verzweifelt bist und alles nicht hilft, dass Du Neuaufbauen willst/musst, kannst ja noch meine Radikalmethode verwenden. Hilft natürlich nur, wenn Du nicht versuchst Deinen iobroker neu zu installieren und Deine package.json überschreibst.
-
pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code Unknown system error -117 npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/graceful-fs npm ERR! dest /opt/iobroker/node_modules/.graceful-fs-i6Qs7iN3 npm ERR! errno -117 npm ERR! Unknown system error -117: Unknown system error -117, rename '/opt/iobroker/node_modules/graceful-fs' -> '/opt/iobroker/node_modules/.graceful-fs-i6Qs7iN3' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-11-11T11_20_41_275Z-debug-0.log
-
-
habe ich ja versucht, bzw. gemacht... Ändert aber anscheinend nix. Oder hab ich da was falsch verstanden?
pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code Unknown system error -117 npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/graceful-fs npm ERR! dest /opt/iobroker/node_modules/.graceful-fs-i6Qs7iN3 npm ERR! errno -117 npm ERR! Unknown system error -117: Unknown system error -117, rename '/opt/iobroker/node_modules/graceful-fs' -> '/opt/iobroker/node_modules/.graceful-fs-i6Qs7iN3' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-11-11T11_20_41_275Z-debug-0.log pi@raspberrypi:/opt/iobroker $ cd /opt/iobroker/node_modules pi@raspberrypi:/opt/iobroker/node_modules $ for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; done pi@raspberrypi:/opt/iobroker/node_modules $ ^C pi@raspberrypi:/opt/iobroker/node_modules $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code Unknown system error -117 npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/graceful-fs npm ERR! dest /opt/iobroker/node_modules/.graceful-fs-i6Qs7iN3 npm ERR! errno -117 npm ERR! Unknown system error -117: Unknown system error -117, rename '/opt/iobroker/node_modules/graceful-fs' -> '/opt/iobroker/node_modules/.graceful-fs-i6Qs7iN3' npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-11-11T11_26_35_301Z-debug-0.log pi@raspberrypi:/opt/iobroker $
-
Ah, ich glaube da hast du einen 'Fehler' in der RegEx aufgestöbert.
Komplette Ausgabe zufor i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do echo ${i%}; done
bitte.
-
@xxx_turbo_xxx sagte in iobroker startet nicht nach node-js Update 16.18.1:
Und auch mal bitte
find /opt/iobroker/node_modules -type d -iname '.*-????????' ! -iname '.local-chromium' | wc -l
-
Beim ersten Befehl passiert nichts (zumindest nicht offensichtlich..
der Zweite gibt 0 zurückpi@raspberrypi:/opt/iobroker/node_modules $ for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do echo ${i%}; done pi@raspberrypi:/opt/iobroker/node_modules $ find /opt/iobroker/node_modules -type d -iname '.*-????????' ! -iname '.local-chromium' | wc -l 0 pi@raspberrypi:/opt/iobroker/node_modules $