Probleme bei Adapter Updates
-
-
@siggi0904 Danke. Das führt leider nicht weiter. Der Artikel bezieht sich auf "Directory not empty" Probleme. Das ist bei mir nicht der Fall.
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs iobroker updateDann einen der Adapter mit --debug-Option installieren.
-
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs iobroker updateDann einen der Adapter mit --debug-Option installieren.
@thomas-braun said in Probleme bei Adapter Updates:
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
Danke.
Dann sehen die letzten Zeilen wiefolgt aus:5116 info run diskusage@1.1.3 install node_modules/diskusage node-gyp rebuild 5117 info run iobroker.js-controller@4.0.23 install node_modules/iobroker.js-controller node iobroker.js setup first 5118 info run diskusage@1.1.3 install { code: 0, signal: null } 5119 timing build:run:install:node_modules/diskusage Completed in 4610ms 5120 info run iobroker.vis@1.4.15 install node_modules/iobroker.vis node main.js --install 5121 info run iobroker.js-controller@4.0.23 install { code: 0, signal: null } 5122 timing build:run:install:node_modules/iobroker.js-controller Completed in 9468ms 5123 info run iobroker.vis-google-fonts@1.0.3 install node_modules/iobroker.vis-google-fonts node main.js --install 5124 info run iobroker.vis-google-fonts@1.0.3 install { code: 0, signal: null } 5125 timing build:run:install:node_modules/iobroker.vis-google-fonts Completed in 3504ms 5126 info run sqlite3@5.1.1 install node_modules/sqlite3 node-pre-gyp install --fallback-to-build 5127 info run sqlite3@5.1.1 install { code: 0, signal: null } 5128 timing build:run:install:node_modules/sqlite3 Completed in 1001ms 5129 info run unix-dgram@2.0.4 install node_modules/unix-dgram node-gyp rebuild 5130 info run iobroker.vis@1.4.15 install { code: 0, signal: null } 5131 timing build:run:install:node_modules/iobroker.vis Completed in 9604ms 5132 info run ursa-optional@0.9.10 install node_modules/ursa-optional node rebuild.js 5133 info run unix-dgram@2.0.4 install { code: 0, signal: null } 5134 timing build:run:install:node_modules/unix-dgram Completed in 3659ms 5135 info run ursa-optional@0.9.10 install { code: 0, signal: null } 5136 timing build:run:install:node_modules/ursa-optional Completed in 3773ms 5137 timing build:run:install Completed in 17987ms 5138 info run @root/acme@3.1.0 postinstall node_modules/@root/acme node scripts/postinstall 5139 info run core-js@2.6.12 postinstall node_modules/core-js node -e "try{require('./postinstall')}catch(e){}" 5140 info run @root/acme@3.1.0 postinstall { code: 0, signal: null } 5141 timing build:run:postinstall:node_modules/@root/acme Completed in 134ms 5142 info run esbuild@0.11.23 postinstall node_modules/esbuild node install.js 5143 info run core-js@2.6.12 postinstall { code: 0, signal: null } 5144 timing build:run:postinstall:node_modules/core-js Completed in 139ms 5145 info run iobroker.javascript@6.0.0 postinstall node_modules/iobroker.javascript node ./install/installTypings.js 5146 info run esbuild@0.11.23 postinstall { code: 0, signal: null } 5147 timing build:run:postinstall:node_modules/esbuild Completed in 174ms 5148 info run underscore@1.13.5 postinstall node_modules/underscore patch-package 5149 info run underscore@1.13.5 postinstall { code: 127, signal: null } 5150 info run iobroker.javascript@6.0.0 postinstall { code: 0, signal: null } 5151 timing build:run:postinstall:node_modules/iobroker.javascript Completed in 4520ms 5152 timing reify:rollback:createSparse Completed in 7965ms 5153 timing reify:rollback:retireShallow Completed in 363ms 5154 timing command:install Completed in 113941ms 5155 verbose stack Error: command failed 5155 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27) 5155 verbose stack at ChildProcess.emit (node:events:513:28) 5155 verbose stack at maybeClose (node:internal/child_process:1093:16) 5155 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) 5156 verbose pkgid underscore@1.13.5 5157 verbose cwd /opt/iobroker 5158 verbose Linux 4.15.0-166-generic 5159 verbose node v16.17.0 5160 verbose npm v8.15.0 5161 error code 127 5162 error path /opt/iobroker/node_modules/underscore 5163 error command failed 5164 error command sh /tmp/postinstall-4edfe6af.sh 5165 error /tmp/postinstall-4edfe6af.sh: 1: /tmp/postinstall-4edfe6af.sh: patch-package: not found 5166 verbose exit 127 5167 timing npm Completed in 114120ms 5168 verbose unfinished npm timer reify 1663967600347 5169 verbose unfinished npm timer reify:build 1663967686652 5170 verbose unfinished npm timer build 1663967686657 5171 verbose unfinished npm timer build:deps 1663967686658 5172 verbose unfinished npm timer build:run:postinstall 1663967705577 5173 verbose unfinished npm timer build:run:postinstall:node_modules/underscore 1663967705886 5174 verbose code 127MOD-EDIT: Code in code-tags gesetzt!
-
@thomas-braun said in Probleme bei Adapter Updates:
uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
Danke.
Dann sehen die letzten Zeilen wiefolgt aus:5116 info run diskusage@1.1.3 install node_modules/diskusage node-gyp rebuild 5117 info run iobroker.js-controller@4.0.23 install node_modules/iobroker.js-controller node iobroker.js setup first 5118 info run diskusage@1.1.3 install { code: 0, signal: null } 5119 timing build:run:install:node_modules/diskusage Completed in 4610ms 5120 info run iobroker.vis@1.4.15 install node_modules/iobroker.vis node main.js --install 5121 info run iobroker.js-controller@4.0.23 install { code: 0, signal: null } 5122 timing build:run:install:node_modules/iobroker.js-controller Completed in 9468ms 5123 info run iobroker.vis-google-fonts@1.0.3 install node_modules/iobroker.vis-google-fonts node main.js --install 5124 info run iobroker.vis-google-fonts@1.0.3 install { code: 0, signal: null } 5125 timing build:run:install:node_modules/iobroker.vis-google-fonts Completed in 3504ms 5126 info run sqlite3@5.1.1 install node_modules/sqlite3 node-pre-gyp install --fallback-to-build 5127 info run sqlite3@5.1.1 install { code: 0, signal: null } 5128 timing build:run:install:node_modules/sqlite3 Completed in 1001ms 5129 info run unix-dgram@2.0.4 install node_modules/unix-dgram node-gyp rebuild 5130 info run iobroker.vis@1.4.15 install { code: 0, signal: null } 5131 timing build:run:install:node_modules/iobroker.vis Completed in 9604ms 5132 info run ursa-optional@0.9.10 install node_modules/ursa-optional node rebuild.js 5133 info run unix-dgram@2.0.4 install { code: 0, signal: null } 5134 timing build:run:install:node_modules/unix-dgram Completed in 3659ms 5135 info run ursa-optional@0.9.10 install { code: 0, signal: null } 5136 timing build:run:install:node_modules/ursa-optional Completed in 3773ms 5137 timing build:run:install Completed in 17987ms 5138 info run @root/acme@3.1.0 postinstall node_modules/@root/acme node scripts/postinstall 5139 info run core-js@2.6.12 postinstall node_modules/core-js node -e "try{require('./postinstall')}catch(e){}" 5140 info run @root/acme@3.1.0 postinstall { code: 0, signal: null } 5141 timing build:run:postinstall:node_modules/@root/acme Completed in 134ms 5142 info run esbuild@0.11.23 postinstall node_modules/esbuild node install.js 5143 info run core-js@2.6.12 postinstall { code: 0, signal: null } 5144 timing build:run:postinstall:node_modules/core-js Completed in 139ms 5145 info run iobroker.javascript@6.0.0 postinstall node_modules/iobroker.javascript node ./install/installTypings.js 5146 info run esbuild@0.11.23 postinstall { code: 0, signal: null } 5147 timing build:run:postinstall:node_modules/esbuild Completed in 174ms 5148 info run underscore@1.13.5 postinstall node_modules/underscore patch-package 5149 info run underscore@1.13.5 postinstall { code: 127, signal: null } 5150 info run iobroker.javascript@6.0.0 postinstall { code: 0, signal: null } 5151 timing build:run:postinstall:node_modules/iobroker.javascript Completed in 4520ms 5152 timing reify:rollback:createSparse Completed in 7965ms 5153 timing reify:rollback:retireShallow Completed in 363ms 5154 timing command:install Completed in 113941ms 5155 verbose stack Error: command failed 5155 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27) 5155 verbose stack at ChildProcess.emit (node:events:513:28) 5155 verbose stack at maybeClose (node:internal/child_process:1093:16) 5155 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) 5156 verbose pkgid underscore@1.13.5 5157 verbose cwd /opt/iobroker 5158 verbose Linux 4.15.0-166-generic 5159 verbose node v16.17.0 5160 verbose npm v8.15.0 5161 error code 127 5162 error path /opt/iobroker/node_modules/underscore 5163 error command failed 5164 error command sh /tmp/postinstall-4edfe6af.sh 5165 error /tmp/postinstall-4edfe6af.sh: 1: /tmp/postinstall-4edfe6af.sh: patch-package: not found 5166 verbose exit 127 5167 timing npm Completed in 114120ms 5168 verbose unfinished npm timer reify 1663967600347 5169 verbose unfinished npm timer reify:build 1663967686652 5170 verbose unfinished npm timer build 1663967686657 5171 verbose unfinished npm timer build:deps 1663967686658 5172 verbose unfinished npm timer build:run:postinstall 1663967705577 5173 verbose unfinished npm timer build:run:postinstall:node_modules/underscore 1663967705886 5174 verbose code 127MOD-EDIT: Code in code-tags gesetzt!
Vollständige Ein- und Ausgaben (in CodeTags eingebettet).
-
Vollständige Ein- und Ausgaben (in CodeTags eingebettet).
Auch das, wenn's hilft. ;-) Aber ich kann mir nicht vorstellen, dass jemand hier 5174 Zeilen Logdatei lesen möchte.
Und leider sehe ich in dieser Logdatei, auf die unten verwiesen wird und deren Ende ich oben gepostet habe nicht, wo das zugehörige Log anfängt.
Aber I/O war:/opt/iobroker$ sudo iobroker upgrade vis-canvas-gauges --debug This upgrade of "vis-canvas-gauges" will introduce the following changes: ========================================================================== -> 1.0.1: Added workaround for firefox canvas problem ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade vis-canvas-gauges from @0.1.5 to @1.0.1 now? [(y)es, (n)o]: y Update vis-canvas-gauges from @0.1.5 to @1.0.1 NPM version: 8.15.0 Installing iobroker.vis-canvas-gauges@1.0.1... (System call) 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 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 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 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 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 127 npm ERR! path /opt/iobroker/node_modules/underscore npm ERR! command failed npm ERR! command sh /tmp/postinstall-4edfe6af.sh npm ERR! /tmp/postinstall-4edfe6af.sh: 1: /tmp/postinstall-4edfe6af.sh: patch-package: not found npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-23T21_13_20_174Z-debug-0.log host.homie Cannot install iobroker.vis-canvas-gauges@1.0.1: 127 -
Auch das, wenn's hilft. ;-) Aber ich kann mir nicht vorstellen, dass jemand hier 5174 Zeilen Logdatei lesen möchte.
Und leider sehe ich in dieser Logdatei, auf die unten verwiesen wird und deren Ende ich oben gepostet habe nicht, wo das zugehörige Log anfängt.
Aber I/O war:/opt/iobroker$ sudo iobroker upgrade vis-canvas-gauges --debug This upgrade of "vis-canvas-gauges" will introduce the following changes: ========================================================================== -> 1.0.1: Added workaround for firefox canvas problem ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade vis-canvas-gauges from @0.1.5 to @1.0.1 now? [(y)es, (n)o]: y Update vis-canvas-gauges from @0.1.5 to @1.0.1 NPM version: 8.15.0 Installing iobroker.vis-canvas-gauges@1.0.1... (System call) 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 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 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 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 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 127 npm ERR! path /opt/iobroker/node_modules/underscore npm ERR! command failed npm ERR! command sh /tmp/postinstall-4edfe6af.sh npm ERR! /tmp/postinstall-4edfe6af.sh: 1: /tmp/postinstall-4edfe6af.sh: patch-package: not found npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-23T21_13_20_174Z-debug-0.log host.homie Cannot install iobroker.vis-canvas-gauges@1.0.1: 127@aski71 sagte in Probleme bei Adapter Updates:
Aber ich kann mir nicht vorstellen, dass jemand hier 5174 Zeilen Logdatei lesen möchte.
Richtig, will keiner, wenn es nicht nötig ist. Hier ist es nicht nötig.
Aber die Ein- und Ausgaben zu
sudo ln -s /usr/bin/node /usr/bin/nodejs uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs iobroker updatewären notwendig.
-
Auch das, wenn's hilft. ;-) Aber ich kann mir nicht vorstellen, dass jemand hier 5174 Zeilen Logdatei lesen möchte.
Und leider sehe ich in dieser Logdatei, auf die unten verwiesen wird und deren Ende ich oben gepostet habe nicht, wo das zugehörige Log anfängt.
Aber I/O war:/opt/iobroker$ sudo iobroker upgrade vis-canvas-gauges --debug This upgrade of "vis-canvas-gauges" will introduce the following changes: ========================================================================== -> 1.0.1: Added workaround for firefox canvas problem ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade vis-canvas-gauges from @0.1.5 to @1.0.1 now? [(y)es, (n)o]: y Update vis-canvas-gauges from @0.1.5 to @1.0.1 NPM version: 8.15.0 Installing iobroker.vis-canvas-gauges@1.0.1... (System call) 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 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 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 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 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 127 npm ERR! path /opt/iobroker/node_modules/underscore npm ERR! command failed npm ERR! command sh /tmp/postinstall-4edfe6af.sh npm ERR! /tmp/postinstall-4edfe6af.sh: 1: /tmp/postinstall-4edfe6af.sh: patch-package: not found npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-23T21_13_20_174Z-debug-0.log host.homie Cannot install iobroker.vis-canvas-gauges@1.0.1: 127@aski71 sagte in Probleme bei Adapter Updates:
sudo iobroker upgrade
Verboten!
iobroker NIE NIE NIEMALS per sudo/root anpacken.
Fix das:iobroker stop iobroker fix iobroker start -
Auch das, wenn's hilft. ;-) Aber ich kann mir nicht vorstellen, dass jemand hier 5174 Zeilen Logdatei lesen möchte.
Und leider sehe ich in dieser Logdatei, auf die unten verwiesen wird und deren Ende ich oben gepostet habe nicht, wo das zugehörige Log anfängt.
Aber I/O war:/opt/iobroker$ sudo iobroker upgrade vis-canvas-gauges --debug This upgrade of "vis-canvas-gauges" will introduce the following changes: ========================================================================== -> 1.0.1: Added workaround for firefox canvas problem ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade vis-canvas-gauges from @0.1.5 to @1.0.1 now? [(y)es, (n)o]: y Update vis-canvas-gauges from @0.1.5 to @1.0.1 NPM version: 8.15.0 Installing iobroker.vis-canvas-gauges@1.0.1... (System call) 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 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 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 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 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 127 npm ERR! path /opt/iobroker/node_modules/underscore npm ERR! command failed npm ERR! command sh /tmp/postinstall-4edfe6af.sh npm ERR! /tmp/postinstall-4edfe6af.sh: 1: /tmp/postinstall-4edfe6af.sh: patch-package: not found npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-09-23T21_13_20_174Z-debug-0.log host.homie Cannot install iobroker.vis-canvas-gauges@1.0.1: 127@aski71 Ah, moment...
/opt/iobroker$ sudo ln -s /usr/bin/node /usr/bin/nodejs ln: failed to create symbolic link '/usr/bin/nodejs': File exists /opt/iobroker$ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && 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 4.0.23 ak ak adm cdrom sudo dip plugdev lxd sambashare lpadmin iobroker /opt/iobroker Ign:1 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 InRelease Hit:2 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 https://deb.nodesource.com/node_16.x bionic InRelease Hit:6 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 https://repo.mosquitto.org/debian buster InRelease Hit:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 Release Hit:9 https://repo.mosquitto.org/debian jessie InRelease Hit:10 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:11 https://repo.mosquitto.org/debian stretch InRelease Hit:12 https://dl.ubnt.com/unifi/debian stable InRelease Reading package lists... Done Building dependency tree Reading state information... Done 2 packages can be upgraded. Run 'apt list --upgradable' to see them. nodejs: Installed: 16.17.0-1nodesource1 Candidate: 16.17.1-1nodesource1 Version table: 16.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bionic/main amd64 Packages *** 16.17.0-1nodesource1 100 100 /var/lib/dpkg/status 8.10.0~dfsg-2ubuntu0.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 8.10.0~dfsg-2ubuntu0.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 8.10.0~dfsg-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages -
@aski71 sagte in Probleme bei Adapter Updates:
sudo iobroker upgrade
Verboten!
iobroker NIE NIE NIEMALS per sudo/root anpacken.
Fix das:iobroker stop iobroker fix iobroker start@thomas-braun said in Probleme bei Adapter Updates:
@aski71 sagte in Probleme bei Adapter Updates:
sudo iobroker upgrade
Verboten!
iobroker NIE NIE NIEMALS per sudo/root anpacken.
Fix das:iobroker stop iobroker fix iobroker startDas ging bei mir noch nie ohne sudo.
-
@aski71 Ah, moment...
/opt/iobroker$ sudo ln -s /usr/bin/node /usr/bin/nodejs ln: failed to create symbolic link '/usr/bin/nodejs': File exists /opt/iobroker$ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && 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 4.0.23 ak ak adm cdrom sudo dip plugdev lxd sambashare lpadmin iobroker /opt/iobroker Ign:1 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 InRelease Hit:2 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease Hit:3 http://de.archive.ubuntu.com/ubuntu bionic InRelease Hit:4 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 https://deb.nodesource.com/node_16.x bionic InRelease Hit:6 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 https://repo.mosquitto.org/debian buster InRelease Hit:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 Release Hit:9 https://repo.mosquitto.org/debian jessie InRelease Hit:10 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:11 https://repo.mosquitto.org/debian stretch InRelease Hit:12 https://dl.ubnt.com/unifi/debian stable InRelease Reading package lists... Done Building dependency tree Reading state information... Done 2 packages can be upgraded. Run 'apt list --upgradable' to see them. nodejs: Installed: 16.17.0-1nodesource1 Candidate: 16.17.1-1nodesource1 Version table: 16.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bionic/main amd64 Packages *** 16.17.0-1nodesource1 100 100 /var/lib/dpkg/status 8.10.0~dfsg-2ubuntu0.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 8.10.0~dfsg-2ubuntu0.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 8.10.0~dfsg-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 PackagesWas soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer... -
@thomas-braun said in Probleme bei Adapter Updates:
@aski71 sagte in Probleme bei Adapter Updates:
sudo iobroker upgrade
Verboten!
iobroker NIE NIE NIEMALS per sudo/root anpacken.
Fix das:iobroker stop iobroker fix iobroker startDas ging bei mir noch nie ohne sudo.
@aski71 sagte in Probleme bei Adapter Updates:
Das ging bei mir noch nie ohne sudo.
Doch, in senkrechten Installationen geht das natürlich ohne sudo.
Du hast das aber irgendwas wild falsch zusammenstöpselt. -
Was soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer...@thomas-braun said in Probleme bei Adapter Updates:
Was soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer...Keine Ahnung. Ich habe nie was anderes gemacht, als die üblichen Upgrades über das iobroker Kommando.
Respektive Systemupgrades via apt. -
@aski71 sagte in Probleme bei Adapter Updates:
Das ging bei mir noch nie ohne sudo.
Doch, in senkrechten Installationen geht das natürlich ohne sudo.
Du hast das aber irgendwas wild falsch zusammenstöpselt.@thomas-braun said in Probleme bei Adapter Updates:
@aski71 sagte in Probleme bei Adapter Updates:
Das ging bei mir noch nie ohne sudo.
Doch, in senkrechten Installationen geht das natürlich ohne sudo.
Du hast das aber irgendwas wild falsch zusammenstöpselt.Dann gab es wohl wild falsch zusammen gestöpselte Anleitungen.
-
@thomas-braun said in Probleme bei Adapter Updates:
Was soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer...Keine Ahnung. Ich habe nie was anderes gemacht, als die üblichen Upgrades über das iobroker Kommando.
Respektive Systemupgrades via apt.@aski71 sagte in Probleme bei Adapter Updates:
Ich habe nie was anderes gemacht, als die üblichen Upgrades über das iobroker Kommando.
Das kann nicht sein.
Muss auf bionic lauten, nicht auf xenial:
Ign:1 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 InRelease Hit:8 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 ReleaseMuss auf bionic lauten, nicht auf buster/jessie/stretch:
Hit:7 https://repo.mosquitto.org/debian buster InRelease Hit:9 https://repo.mosquitto.org/debian jessie InRelease Hit:11 https://repo.mosquitto.org/debian stretch InRelease -
@thomas-braun said in Probleme bei Adapter Updates:
Was soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer...Keine Ahnung. Ich habe nie was anderes gemacht, als die üblichen Upgrades über das iobroker Kommando.
Respektive Systemupgrades via apt.@aski71 said in Probleme bei Adapter Updates:
@thomas-braun said in Probleme bei Adapter Updates:
Was soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer...Keine Ahnung. Ich habe nie was anderes gemacht, als die üblichen Upgrades über das iobroker Kommando.
Respektive Systemupgrades via apt.Und wie entfrankensteine ich das nun am besten?
-
@aski71 said in Probleme bei Adapter Updates:
@thomas-braun said in Probleme bei Adapter Updates:
Was soll denn das für ein Frankenstein-Zoo an Paketquellen sein?
Da geht ja ALLES kreuz und quer...Keine Ahnung. Ich habe nie was anderes gemacht, als die üblichen Upgrades über das iobroker Kommando.
Respektive Systemupgrades via apt.Und wie entfrankensteine ich das nun am besten?
Schau dir die /etc/apt/sources.list.d/mosquitto.list (oder so ähnlich) an.
Da dürfte der Hauptquark drin stehen. Davon abgesehen ist mosquitto in den main Repos von 'bionic', soweit ich das sehe.Ist aber OT für das Thema hier.
-
Schau dir die /etc/apt/sources.list.d/mosquitto.list (oder so ähnlich) an.
Da dürfte der Hauptquark drin stehen. Davon abgesehen ist mosquitto in den main Repos von 'bionic', soweit ich das sehe.Ist aber OT für das Thema hier.
@thomas-braun said in Probleme bei Adapter Updates:
Schau dir die /etc/apt/sources.list.d/mosquitto.list (oder so ähnlich) an.
Da dürfte der Hauptquark drin stehen. Davon abgesehen ist mosquitto in den main Repos von 'bionic', soweit ich das sehe.Ist aber OT für das Thema hier.
Wenn ich mir das oder so ähnlich anschaue, stehe ich garantiert davor, wie der Ochse vor'm Berg, wenn mir keiner sagt, wie das richtig aussehen muss.
Vor allem frage ich mich aber, warum das überhaupt falsch ist. -
@thomas-braun said in Probleme bei Adapter Updates:
Schau dir die /etc/apt/sources.list.d/mosquitto.list (oder so ähnlich) an.
Da dürfte der Hauptquark drin stehen. Davon abgesehen ist mosquitto in den main Repos von 'bionic', soweit ich das sehe.Ist aber OT für das Thema hier.
Wenn ich mir das oder so ähnlich anschaue, stehe ich garantiert davor, wie der Ochse vor'm Berg, wenn mir keiner sagt, wie das richtig aussehen muss.
Vor allem frage ich mich aber, warum das überhaupt falsch ist.@aski71 sagte in Probleme bei Adapter Updates:
Vor allem frage ich mich aber, warum das überhaupt falsch ist.
Vermutlich, weil du die Anleitung von hier:
https://mosquitto.org/blog/2013/01/mosquitto-debian-repository/
falsch verstanden hast.
Da steht:Then one of the following, depending on which version of debian you are using:
sudo wget http://repo.mosquitto.org/debian/mosquitto-jessie.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-stretch.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-buster.listDu hast aber keine der drei Debian-Versionen, du hast ein Ubuntu 'Bionic' laufen.
sudo rm /etc/apt/sources.list.d/mosquitto-* sudo apt update apt policy mosquitto -
@aski71 sagte in Probleme bei Adapter Updates:
Vor allem frage ich mich aber, warum das überhaupt falsch ist.
Vermutlich, weil du die Anleitung von hier:
https://mosquitto.org/blog/2013/01/mosquitto-debian-repository/
falsch verstanden hast.
Da steht:Then one of the following, depending on which version of debian you are using:
sudo wget http://repo.mosquitto.org/debian/mosquitto-jessie.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-stretch.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-buster.listDu hast aber keine der drei Debian-Versionen, du hast ein Ubuntu 'Bionic' laufen.
sudo rm /etc/apt/sources.list.d/mosquitto-* sudo apt update apt policy mosquitto@thomas-braun said in Probleme bei Adapter Updates:
@aski71 sagte in Probleme bei Adapter Updates:
Vor allem frage ich mich aber, warum das überhaupt falsch ist.
Vermutlich, weil du die Anleitung von hier:
https://mosquitto.org/blog/2013/01/mosquitto-debian-repository/
falsch verstanden hast.
Da steht:Then one of the following, depending on which version of debian you are using:
sudo wget http://repo.mosquitto.org/debian/mosquitto-jessie.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-stretch.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-buster.listDu hast aber keine der drei Debian-Versionen, du hast ein Ubuntu 'Bionic' laufen.
sudo rm /etc/apt/sources.list.d/mosquitto-* sudo apt update apt policy mosquittoIch sehe diese Dateien tatsächlich zum allererstenmal und hab da noch nie was drin gebastelt.
ak@homie:/etc/apt/sources.list.d$ ls -l total 38 -rw-r--r-- 1 root root 62 Feb 22 2022 100-ubnt-unifi.list -rw-r--r-- 1 root root 70 Dec 27 2018 certbot-ubuntu-certbot-bionic.list -rw-r--r-- 1 root root 177 Dec 27 2018 certbot-ubuntu-certbot-xenial.list -rw-r--r-- 1 root root 134 Dec 20 2018 certbot-ubuntu-certbot-xenial.list.distUpgrade -rw-r--r-- 1 root root 179 Dec 27 2018 certbot-ubuntu-certbot-xenial.list.save -rw-r--r-- 1 root root 94 Jan 25 2019 mongodb-org-3.4.list -rw-r--r-- 1 root root 50 Jun 25 2019 mosquitto-buster.list -rw-r--r-- 1 root root 50 Aug 8 2018 mosquitto-jessie.list -rw-r--r-- 1 root root 51 Aug 8 2018 mosquitto-stretch.list -rw-r--r-- 1 root root 204 Feb 9 2022 nodesource.list -rw-r--r-- 1 root root 108 Dec 20 2018 nodesource.list.distUpgrade -rw-r--r-- 1 root root 198 Dec 27 2018 nodesource.list.saveDas sind die Dateien, die ich vorfinde. Die Mücken also alle löschen?
-
@thomas-braun said in Probleme bei Adapter Updates:
@aski71 sagte in Probleme bei Adapter Updates:
Vor allem frage ich mich aber, warum das überhaupt falsch ist.
Vermutlich, weil du die Anleitung von hier:
https://mosquitto.org/blog/2013/01/mosquitto-debian-repository/
falsch verstanden hast.
Da steht:Then one of the following, depending on which version of debian you are using:
sudo wget http://repo.mosquitto.org/debian/mosquitto-jessie.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-stretch.list
sudo wget http://repo.mosquitto.org/debian/mosquitto-buster.listDu hast aber keine der drei Debian-Versionen, du hast ein Ubuntu 'Bionic' laufen.
sudo rm /etc/apt/sources.list.d/mosquitto-* sudo apt update apt policy mosquittoIch sehe diese Dateien tatsächlich zum allererstenmal und hab da noch nie was drin gebastelt.
ak@homie:/etc/apt/sources.list.d$ ls -l total 38 -rw-r--r-- 1 root root 62 Feb 22 2022 100-ubnt-unifi.list -rw-r--r-- 1 root root 70 Dec 27 2018 certbot-ubuntu-certbot-bionic.list -rw-r--r-- 1 root root 177 Dec 27 2018 certbot-ubuntu-certbot-xenial.list -rw-r--r-- 1 root root 134 Dec 20 2018 certbot-ubuntu-certbot-xenial.list.distUpgrade -rw-r--r-- 1 root root 179 Dec 27 2018 certbot-ubuntu-certbot-xenial.list.save -rw-r--r-- 1 root root 94 Jan 25 2019 mongodb-org-3.4.list -rw-r--r-- 1 root root 50 Jun 25 2019 mosquitto-buster.list -rw-r--r-- 1 root root 50 Aug 8 2018 mosquitto-jessie.list -rw-r--r-- 1 root root 51 Aug 8 2018 mosquitto-stretch.list -rw-r--r-- 1 root root 204 Feb 9 2022 nodesource.list -rw-r--r-- 1 root root 108 Dec 20 2018 nodesource.list.distUpgrade -rw-r--r-- 1 root root 198 Dec 27 2018 nodesource.list.saveDas sind die Dateien, die ich vorfinde. Die Mücken also alle löschen?
@aski71 sagte in Probleme bei Adapter Updates:
Alles überflüssig/falsch.
Löschen:sudo rm /etc/apt/sources.list.d/certbot-ubuntu-certbot-xenial* sudo rm /etc/apt/sources.list.d/mosquitto* sudo rm /etc/apt/sources.list.d/nodesource.list.* sudo rm /etc/apt/sources.list.d/mongodb* sudo apt update apt policy mosquitto mongodb
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden535
Online32.9k
Benutzer83.0k
Themen1.3m
Beiträge