NEWS
NPM Fehler seit Upgrade auf 8.x
ioBroker Allgemein
9
Beiträge
2
Kommentatoren
1.1k
Aufrufe
2
Watching
-
Hallo zusammen,
Seit dem Update auf Admin 6.x und damit den Upgrade von Nodejs habe ich vermehrt Probleme, wenn ich die Adapter aktualisieren möchte. Ständig erhalten ich Errorcode 217 und wenn ich dann die Vorschläge aus dem Forum befolge, gehen die nächsten 2-3 Updates durch und ich hänge wieder fest.
ichIch lösche dann regelmässig die Verzeichnisse gemäss dem Einzeiler aus dem HowTo...
for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; doneSoweit so gut, wie ich verstanden habe ich dies ein bekanntest Problem. Was mit jedoch noch aufgefallen ist, dass ich jede Menge NPM Fehler erhalten...
Installing iobroker.discovery@3.0.5... (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 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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0 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 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 coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size 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! 🚀 @niftylettuceWas ist schief gelaufen? Jemand eine Idee
-
Hallo zusammen,
Seit dem Update auf Admin 6.x und damit den Upgrade von Nodejs habe ich vermehrt Probleme, wenn ich die Adapter aktualisieren möchte. Ständig erhalten ich Errorcode 217 und wenn ich dann die Vorschläge aus dem Forum befolge, gehen die nächsten 2-3 Updates durch und ich hänge wieder fest.
ichIch lösche dann regelmässig die Verzeichnisse gemäss dem Einzeiler aus dem HowTo...
for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; doneSoweit so gut, wie ich verstanden habe ich dies ein bekanntest Problem. Was mit jedoch noch aufgefallen ist, dass ich jede Menge NPM Fehler erhalten...
Installing iobroker.discovery@3.0.5... (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 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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated xmldom@0.1.31: Deprecated due to CVE-2021-21366 resolved in 0.5.0 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 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 coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size 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! 🚀 @niftylettuceWas ist schief gelaufen? Jemand eine Idee
@dalmabrain sagte in NPM Fehler seit Upgrade auf 8.x:
jede Menge NPM Fehler
Ich sehe keinen einzigen.
Nur Hinweise / Warnings. -
@dalmabrain sagte in NPM Fehler seit Upgrade auf 8.x:
jede Menge NPM Fehler
Ich sehe keinen einzigen.
Nur Hinweise / Warnings.@thomas-braun Kann ich das dann ignorieren? Ich war nur unversichert, da ich bereits schon viele graue Haare mit dem Error 25 und 217 bekommen habe 😊
-
@thomas-braun Kann ich das dann ignorieren? Ich war nur unversichert, da ich bereits schon viele graue Haare mit dem Error 25 und 217 bekommen habe 😊
Wie bist du denn da insgesamt unterwegs?
iobroker update -i sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs -
Wie bist du denn da insgesamt unterwegs?
iobroker update -i sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs@thomas-braun said in NPM Fehler seit Upgrade auf 8.x:
Hier wären die Resultate...Ist etwas auffällig?
iobroker update -i
bkos@iobroker:~$ iobroker update -i Used repository: stable Adapter "admin" : 6.2.20 , installed 6.2.20 Adapter "alexa2" : 3.11.2 , installed 3.17.5 Adapter "backitup" : 2.4.10 , installed 2.4.10 Adapter "cloud" : 4.2.2 , installed 4.2.2 Adapter "daswetter" : 3.1.2 , installed 3.1.3 Adapter "devices" : 1.0.12 , installed 1.0.12 Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "dwd" : 2.8.3 , installed 2.8.3 Adapter "echarts" : 1.0.12 , installed 1.0.12 Adapter "flot" : 1.11.0 , installed 1.11.0 Adapter "fullcalendar" : 1.2.0 , installed 1.2.0 Adapter "fullybrowser" : 2.1.2 , installed 2.1.2 Adapter "habpanel" : 0.5.0 , installed 0.5.0 Adapter "harmony" : 1.2.2 , installed 1.2.2 Adapter "history" : 2.2.0 , installed 2.1.6 [Updatable] Adapter "hue" : 3.7.1 , installed 3.7.1 Adapter "ical" : 1.13.1 , installed 1.13.1 Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "influxdb" : 3.1.7 , installed 3.1.7 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.11.8 , installed 1.11.8 Adapter "jarvis" : 3.0.11 , installed 3.0.13 Adapter "javascript" : 6.0.0 , installed 6.0.0 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "knx" : 2.0.13 , installed 2.0.14 Adapter "meross" : 1.13.0 , installed 1.13.0 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "mqtt-client" : 1.6.3 , installed 1.6.3 Adapter "netatmo" : 1.7.1 , installed 1.7.1 Adapter "node-red" : 3.3.1 , installed 3.3.1 Adapter "openweathermap": 0.3.0 , installed 0.3.0 Adapter "owfs" : 0.7.0 , installed 0.7.0 Adapter "proxmox" : 1.3.4 , installed 1.3.5 Adapter "proxy" : 1.3.1 , installed 1.3.1 Adapter "pvforecast" : 2.3.0 , installed 2.3.0 Adapter "sayit" : 1.12.3 , installed 1.12.6 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "simple-api" : 2.7.0 , installed 2.7.0 Adapter "smartgarden" : 2.0.0 , installed 2.0.0 Adapter "socketio" : 4.2.0 , installed 6.1.7 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "sonos" : 2.2.3 , installed 2.2.3 Adapter "telegram" : 1.14.1 , installed 1.14.1 Adapter "text2command" : 2.2.2 , installed 2.2.2 Adapter "tr-064" : 4.2.16 , installed 4.2.16 Adapter "trashschedule": 2.0.3 , installed 2.0.3 Adapter "tuya" : 3.6.15 , installed 3.6.15 Adapter "unifi" : 0.5.10 , installed 0.5.10 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-canvas-gauges": 0.1.5, installed 0.1.5 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.2.0 , installed 1.3.0 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.3 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-justgage" : 1.0.2 , installed 1.0.2 Adapter "vis-map" : 1.0.4 , installed 1.0.4 Adapter "vis-material-advanced": 1.7.2, installed 1.7.2 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 4.3.0 , installed 5.2.3 Adapter "wifilight" : 1.1.4 , installed 1.1.4 Adapter "wled" : 0.6.7 , installed 0.6.7 Adapter "wolf" : 1.5.0 , installed 1.5.0 Adapter "ws" : 1.3.0 , installed 2.1.2 Adapter "yahka" : 0.13.1 , installed 0.13.1sudo ln -s /usr/bin/node /usr/bin/nodejs
sudo ln -s /usr/bin/node /usr/bin/nodejs We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for bkos: ln: failed to create symbolic link '/usr/bin/nodejs': File existsuname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs x86_64 /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.17.0 v16.17.0 8.15.0 bkos /home/bkos Hit:1 http://security.debian.org/debian-security stretch/updates InRelease Ign:2 http://ftp.de.debian.org/debian stretch InRelease Hit:3 http://ftp.de.debian.org/debian stretch-updates InRelease Hit:4 http://ftp.de.debian.org/debian stretch Release Hit:5 https://deb.nodesource.com/node_16.x stretch InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. nodejs: Installed: 16.17.0-1nodesource1 Candidate: 16.17.0-1nodesource1 Version table: *** 16.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_16.x stretch/main amd64 Packages 100 /var/lib/dpkg/status 4.8.2~dfsg-1 500 500 http://ftp.de.debian.org/debian stretch/main amd64 Packages -
@thomas-braun said in NPM Fehler seit Upgrade auf 8.x:
Hier wären die Resultate...Ist etwas auffällig?
iobroker update -i
bkos@iobroker:~$ iobroker update -i Used repository: stable Adapter "admin" : 6.2.20 , installed 6.2.20 Adapter "alexa2" : 3.11.2 , installed 3.17.5 Adapter "backitup" : 2.4.10 , installed 2.4.10 Adapter "cloud" : 4.2.2 , installed 4.2.2 Adapter "daswetter" : 3.1.2 , installed 3.1.3 Adapter "devices" : 1.0.12 , installed 1.0.12 Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "dwd" : 2.8.3 , installed 2.8.3 Adapter "echarts" : 1.0.12 , installed 1.0.12 Adapter "flot" : 1.11.0 , installed 1.11.0 Adapter "fullcalendar" : 1.2.0 , installed 1.2.0 Adapter "fullybrowser" : 2.1.2 , installed 2.1.2 Adapter "habpanel" : 0.5.0 , installed 0.5.0 Adapter "harmony" : 1.2.2 , installed 1.2.2 Adapter "history" : 2.2.0 , installed 2.1.6 [Updatable] Adapter "hue" : 3.7.1 , installed 3.7.1 Adapter "ical" : 1.13.1 , installed 1.13.1 Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "influxdb" : 3.1.7 , installed 3.1.7 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.11.8 , installed 1.11.8 Adapter "jarvis" : 3.0.11 , installed 3.0.13 Adapter "javascript" : 6.0.0 , installed 6.0.0 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "knx" : 2.0.13 , installed 2.0.14 Adapter "meross" : 1.13.0 , installed 1.13.0 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "mqtt-client" : 1.6.3 , installed 1.6.3 Adapter "netatmo" : 1.7.1 , installed 1.7.1 Adapter "node-red" : 3.3.1 , installed 3.3.1 Adapter "openweathermap": 0.3.0 , installed 0.3.0 Adapter "owfs" : 0.7.0 , installed 0.7.0 Adapter "proxmox" : 1.3.4 , installed 1.3.5 Adapter "proxy" : 1.3.1 , installed 1.3.1 Adapter "pvforecast" : 2.3.0 , installed 2.3.0 Adapter "sayit" : 1.12.3 , installed 1.12.6 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "simple-api" : 2.7.0 , installed 2.7.0 Adapter "smartgarden" : 2.0.0 , installed 2.0.0 Adapter "socketio" : 4.2.0 , installed 6.1.7 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "sonos" : 2.2.3 , installed 2.2.3 Adapter "telegram" : 1.14.1 , installed 1.14.1 Adapter "text2command" : 2.2.2 , installed 2.2.2 Adapter "tr-064" : 4.2.16 , installed 4.2.16 Adapter "trashschedule": 2.0.3 , installed 2.0.3 Adapter "tuya" : 3.6.15 , installed 3.6.15 Adapter "unifi" : 0.5.10 , installed 0.5.10 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-canvas-gauges": 0.1.5, installed 0.1.5 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.2.0 , installed 1.3.0 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.3 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-justgage" : 1.0.2 , installed 1.0.2 Adapter "vis-map" : 1.0.4 , installed 1.0.4 Adapter "vis-material-advanced": 1.7.2, installed 1.7.2 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 4.3.0 , installed 5.2.3 Adapter "wifilight" : 1.1.4 , installed 1.1.4 Adapter "wled" : 0.6.7 , installed 0.6.7 Adapter "wolf" : 1.5.0 , installed 1.5.0 Adapter "ws" : 1.3.0 , installed 2.1.2 Adapter "yahka" : 0.13.1 , installed 0.13.1sudo ln -s /usr/bin/node /usr/bin/nodejs
sudo ln -s /usr/bin/node /usr/bin/nodejs We trust you have received the usual lecture from the local System Administrator. It usually boils down to these three things: #1) Respect the privacy of others. #2) Think before you type. #3) With great power comes great responsibility. [sudo] password for bkos: ln: failed to create symbolic link '/usr/bin/nodejs': File existsuname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs x86_64 /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.17.0 v16.17.0 8.15.0 bkos /home/bkos Hit:1 http://security.debian.org/debian-security stretch/updates InRelease Ign:2 http://ftp.de.debian.org/debian stretch InRelease Hit:3 http://ftp.de.debian.org/debian stretch-updates InRelease Hit:4 http://ftp.de.debian.org/debian stretch Release Hit:5 https://deb.nodesource.com/node_16.x stretch InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. nodejs: Installed: 16.17.0-1nodesource1 Candidate: 16.17.0-1nodesource1 Version table: *** 16.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_16.x stretch/main amd64 Packages 100 /var/lib/dpkg/status 4.8.2~dfsg-1 500 500 http://ftp.de.debian.org/debian stretch/main amd64 Packages'stretch' ist tot. Installier da eine lebende Distribution. 'bullseye' z. B.
-
'stretch' ist tot. Installier da eine lebende Distribution. 'bullseye' z. B.
@thomas-braun ach herje...Heisst das jetzt Neuinstallation? :scream:
-
@thomas-braun ach herje...Heisst das jetzt Neuinstallation? :scream:
Kommt drauf an wie sattelfest du auf der Konsole bist und wie 'verlebt' die bisherigen Installation ist. Und ob zwei Distributions-Sprünge nicht doch mehr aufwand sind als eine frische Neuinstallation.
-
Kommt drauf an wie sattelfest du auf der Konsole bist und wie 'verlebt' die bisherigen Installation ist. Und ob zwei Distributions-Sprünge nicht doch mehr aufwand sind als eine frische Neuinstallation.
@thomas-braun :rolling_on_the_floor_laughing: dann vielleicht Neuinstallation und Backup einspielen... :hand_with_index_and_middle_fingers_crossed:
Auf jeden Fall ein grosses Danke an Dich!!!!!!
793
Online32.6k
Benutzer82.0k
Themen1.3m
Beiträge