Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installation
    5. Troubleshooting NodeJS update

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Troubleshooting NodeJS update

    This topic has been deleted. Only users with topic management privileges can see it.
    • crunchip
      crunchip Forum Testing Most Active @MatthiasPetersen last edited by

      @matthiaspetersen probier es mit

      iobroker rebuild admin --install
      
      M 1 Reply Last reply Reply Quote 1
      • M
        MatthiasPetersen @crunchip last edited by

        @crunchip @Thomas-Braun Vielen lieben Dank für Eure Unterstützung und Eure schnellen Antworten. Das

        iobroker rebuild admin --install
        

        hat geholfen.

        1 Reply Last reply Reply Quote 0
        • T
          Tobi81 last edited by

          Hallo zusammen.

          Ich hab heute mein Debian Stretch auf Debian Buster (10) upgedatet und natürlich direkt auch nodejs auch direkt auf Version 18.

          Das habe ich bei meinem Master-System im Dockercontainer gemacht, sowie auf einem Raspbian Slave System.

          Auf dem Raspbian scheint alles gut verlaufen zu sein.

          Auf dem Master läuft auch ioBroker, jedoch kann ich keine Module updaten.

          Im Admin kommt beim ersten Updateversuch folgende Meldung:

          iobroker upgrade heatingcontrol@2.11.1 --debug
          
          Update heatingcontrol from @2.10.6 to @2.11.1
          
          host.iobroker Adapter "system.adapter.heatingcontrol.0" is stopped.
          
          NPM version: 9.6.7
          
          Installing iobroker.heatingcontrol@2.11.1... (System call)
          
          npm WARN skipping integrity check for git dependency ssh://git@github.com/noopkat/browser-serialport.git
          
          npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
          
          npm WARN deprecated jscs-preset-wikimedia@1.0.1: No longer maintained. We recomment migrating to ESLint with eslint-config-wikimedia.
          
          npm WARN deprecated topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
          
          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 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 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 request@2.88.2: request has been deprecated, 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 jscs@3.0.7: JSCS has merged with ESLint! See - https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2
          
          npm WARN deprecated joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
          
          npm WARN deprecated hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
          
          npm WARN deprecated har-validator@5.1.5: this library is no longer supported
          
          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 circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
          
          npm WARN deprecated babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
          
          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 uuid@2.0.3: 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 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 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 WARN cleanup Failed to remove some directories [
          
          npm WARN cleanup syscall: 'rmdir',
          
          npm WARN cleanup path: '/opt/iobroker/node_modules/cpu-features'npm WARN cleanup }npm WARN cleanup ],npm WARN cleanup [npm WARN cleanup '/opt/iobroker/node_modules/cpu-features',npm WARN cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/cpu-features'] {npm WARN cleanup errno: -39,npm WARN cleanup code: 'ENOTEMPTY',npm WARN cleanup syscall: 'rmdir',npm WARN cleanup path: '/opt/iobroker/node_modules/cpu-features'npm WARN cleanup }npm WARN cleanup ]npm WARN cleanup ]
          
          npm ERR! code 1npm ERR! path /opt/iobroker/node_modules/@serialport/bindings
          
          npm ERR! command failednpm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuildnpm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird betretennpm ERR! CXX(target) Release/obj.target/bindings/src/serialport.onpm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird verlassennpm ERR! gyp info it worked if it ends with oknpm ERR! gyp info using node-gyp@9.3.1npm ERR! gyp info using node@18.17.1 | linux | x64npm ERR! gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"npm ERR! gyp info spawn /usr/bin/python3npm ERR! gyp info spawn args [npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/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/@serialport/bindings/build/config.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',npm ERR! gyp info spawn args '-I',npm ERR! gyp info spawn args '/home/iobroker/.cache/node-gyp/18.17.1/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/18.17.1',npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',npm ERR! gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',npm ERR! gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/@serialport/bindings',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 makenpm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:78:69: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);npm ERR! ^~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:135:71: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);npm ERR! ^~~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:175:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);npm ERR! ^~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:215:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);npm ERR! ^~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:270:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);npm ERR! ^~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:314:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);npm ERR! ^~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’:npm ERR! ../src/serialport.cpp:329:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’npm ERR! results->Set(Nan::New<v8::String>("cts").ToLocalChecked(), Nan::New<v8::Boolean>(data->cts));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp:330:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’npm ERR! results->Set(Nan::New<v8::String>("dsr").ToLocalChecked(), Nan::New<v8::Boolean>(data->dsr));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp:331:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’npm ERR! results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:363:76: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);npm ERR! ^~~~~~~~~~~~~~~~~~~~npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’:
          
          npm ERR! ../src/serialport.cpp:378:106: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)’
          
          npm ERR! results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));npm ERR! ^npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,npm ERR! from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,npm ERR! from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:
          
          npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate expects 3 arguments, 2 providednpm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’npm ERR! V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,npm ERR! ^~~npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate expects 3 arguments, 2 providednpm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:npm ERR! ../src/serialport.cpp:409:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]npm ERR! uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
          
          npm ERR! ../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]npm ERR! SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {npm ERR! ^npm ERR! In file included from ../../../nan/nan.h:60,npm ERR! from ../src/./serialport.h:6,npm ERR! from ../src/serialport.cpp:1:npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1014:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]npm ERR! (node::addon_register_func) (regfunc), \npm ERR! ^npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1048:3: note: in expansion of macro ‘NODE_MODULE_X’npm ERR! NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)npm ERR! ^~~~~~~~~~~~~npm ERR! ../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’npm ERR! NODE_MODULE(serialport, init);npm ERR! ^~~~~~~~~~~npm ERR! make: *** [bindings.target.mk:116: Release/obj.target/bindings/src/serialport.o] Fehler 1npm ERR! gyp ERR! build error npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2npm ERR! gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:514:28)npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12)npm ERR! gyp ERR! System Linux 5.15.108-1-pvenpm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindingsnpm ERR! gyp ERR! node -v v18.17.1npm ERR! gyp ERR! node-gyp -v v9.3.1npm ERR! gyp ERR! not ok
          
          npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-31T13_02_01_266Z-debug-0.log
          
          Update "system.adapter.heatingcontrol.0"
          
          upload [4] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/heatingcontrol.png heatingcontrol.png image/png
          
          upload [3] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/img/info-big.png img/info-big.png image/png
          
          upload [2] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/index_m.html index_m.html text/html
          
          upload [1] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/style.css style.css text/css
          
          upload [0] heatingcontrol.admin /opt/iobroker/node_modules/iobroker.heatingcontrol/admin/words.js words.js application/javascript
          
          host.iobroker Adapter "system.adapter.heatingcontrol.0" is started
          
          Process exited with code 0
          

          Bei Updateversuchen weiterer Module ist die Ausgabe dann kürzer:

          $ iobroker upgrade ping@1.6.2 --debug
          
          Update ping from @1.5.3 to @1.6.2
          
          NPM version: 9.6.7
          
          Installing iobroker.ping@1.6.2... (System call)
          
          npm ERR! code ENOTEMPTYnpm ERR! syscall renamenpm ERR! path /opt/iobroker/node_modules/cpu-featuresnpm ERR! dest /opt/iobroker/node_modules/.cpu-features-JirOBYx7npm ERR! errno -39
          
          npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-31T13_16_17_169Z-debug-0.log
          
          host.iobroker Cannot install iobroker.ping@1.6.2: 217
          
          ERROR: Process exited with code 25
          

          Installiert ist mein System wie folgt:

          ======================= SUMMARY =======================
          		     v.2023-04-16
          
          
          Operatingsystem: 	Debian GNU/Linux 10 (buster)
          Kernel: 		5.15.108-1-pve
          Installation: 		lxc
          Failed to query server: Connection timed out
          Timezone: 		
          User-ID: 		1000
          X-Server: 		false
          Boot Target: 		graphical.target
          
          Pending OS-Updates: 	0
          Pending iob updates: 	12
          
          Nodejs-Installation: 	/usr/bin/nodejs 	v18.17.1
          			/usr/bin/node 		v18.17.1
          			/usr/bin/npm 		9.6.7
          			/usr/bin/npx 		9.6.7
          
          Recommended versions are nodejs 18.x.y and npm 9.x.y
          Your nodejs installation is correct
          
          MEMORY: 
                        total        used        free      shared  buff/cache   available
          Mem:           4.1G        2.5G        775M        8.0M        778M        1.6G
          Swap:          4.1G        0.0K        4.1G
          Total:         8.2G        2.5G        4.9G
          
          Active iob-Instances: 	43
          Active repo(s): stable
          
          ioBroker Core: 		js-controller 		4.0.24
          			admin 			6.3.5
          
          ioBroker Status: 	iobroker is running on this host.
          
          
          Objects type: jsonl
          States  type: jsonl
          
          Status admin and web instance:
          + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
          + system.adapter.admin.1                  : admin                 : iobroker2                                -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
          + system.adapter.web.0                    : web                   : iobroker                                 -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
          
          Objects: 		14436
          States: 		12673
          
          Size of iob-Database:
          
          14M	/opt/iobroker/iobroker-data/objects.jsonl
          14M	/opt/iobroker/iobroker-data/objects.json.migrated
          14M	/opt/iobroker/iobroker-data/objects.json.bak.migrated
          14M	/opt/iobroker/iobroker-data/states.jsonl
          2.4M	/opt/iobroker/iobroker-data/states.json.migrated
          2.4M	/opt/iobroker/iobroker-data/states.json.bak.migrated
          
          
          *********************************************************************
          Some problems detected, please run iob fix and try to have them fixed
          *********************************************************************
          
          =================== END OF SUMMARY ====================
          

          iob fix habe ich natürlich schon oft ausprobiert.

          mikeal created this issue in request/request

          open Request’s Past, Present and Future #3142

          mikeal created this issue in request/request

          open Request’s Past, Present and Future #3142

          mikeal created this issue in request/request

          open Request’s Past, Present and Future #3142

          Qix- created this issue in visionmedia/debug

          closed ReDos Vulnerability Regression Visibility Notice #797

          crunchip DJMarc75 2 Replies Last reply Reply Quote 0
          • crunchip
            crunchip Forum Testing Most Active @Tobi81 last edited by crunchip

            @tobi81 sagte in Troubleshooting NodeJS update:

            ERROR: Process exited with code 25

            ist oben angepinnt bei NEWS

            1 Reply Last reply Reply Quote 0
            • DJMarc75
              DJMarc75 @Tobi81 last edited by

              @tobi81 sagte in Troubleshooting NodeJS update:

              hab heute mein Debian Stretch auf Debian Buster (10) upgedate

              von Tod auf Sterbebett quasi 😉

              Warum nicht auf Bullseye ? Welche dubiose Anleitung hast Du verwendet ?

              Und wie @crunchip schrieb, die Lösung ist angepinnt 😉

              crunchip 1 Reply Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active @DJMarc75 last edited by

                @djmarc75 sagte in Troubleshooting NodeJS update:

                Warum nicht auf Bullseye

                weil per update nicht überspringen kann

                T 1 Reply Last reply Reply Quote 0
                • T
                  Tobi81 @crunchip last edited by Tobi81

                  @crunchip

                  @djmarc75 sagte in Troubleshooting NodeJS update:

                  Warum nicht auf Bullseye ? Welche dubiose Anleitung hast Du verwendet ?

                  Ja, leider habe ich ein bisschen verschlafen das System aktuell zu halten und hole das natürlich nach.
                  Von Stretch --> Buster --> Bullseye

                  Das letzte Upgrade wollte ich erst machen wenn ioBroker wieder läuft.

                  Die angepinnte News mit meinem Problem habe ich natürlich nicht gesehen, aber trotzdem habe ich ja den Fixer mehrer Male gestartet und das hat leider nichts gebraucht.

                  Ich habe gerade versucht die aktuellste Version so herunterzuladen

                  curl -fsL https://iobroker.net/fix.sh | bash -
                  

                  Aber das Ergebnis bei einem Adapterupgradeversuch ist immer noch:

                  tobias@iobroker:/opt/iobroker$ iob upgrade --debug
                  
                  This upgrade of "yahka" will introduce the following changes:
                  ==========================================================================
                  -> 1.0.3:
                  Corrected empty device list with rebuild
                  
                  -> 1.0.1:
                  we ensured controller 5 compatibility
                  Formatting
                  ==========================================================================
                  
                  BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES!
                  Would you like to upgrade yahka from @0.17.0 to @1.0.3 now? [(y)es, (n)o]: n
                  No upgrade of "yahka" desired.
                  
                  This upgrade of "ping" will introduce the following changes:
                  ==========================================================================
                  -> 1.6.2:
                  Handling of state updates causing crashes with js-controller 5 has been corrected. (Issue #106)
                  Trailing spaces are now removed from ip address and name. Trailing spaces blocked correct operation. (Issue #98)
                  Added json config
                  Added different intervals for online and offline devices
                  implemented export/import of devices
                  
                  -> 1.6.0:
                  Handling of state updates causing crashes with js-controller 5 has been corrected. (Issue #106)
                  Trailing spaces are now removed from ip address and name. Trailing spaces blocked correct operation. (Issue #98)
                  Added json config
                  ==========================================================================
                  
                  Would you like to upgrade ping from @1.5.3 to @1.6.2 now? [(y)es, (n)o]: y
                  Update ping from @1.5.3 to @1.6.2
                  NPM version: 9.6.7
                  Installing iobroker.ping@1.6.2... (System call)
                  npm WARN skipping integrity check for git dependency ssh://git@github.com/noopkat/browser-serialport.git 
                  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 topo@3.0.3: This module has moved and is now available at @hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
                  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 babel@6.23.0: In 6.x, the babel package has been deprecated in favor of babel-cli. Check https://opencollective.com/babel to support the Babel maintainers
                  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 hoek@6.1.3: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
                  npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
                  npm WARN deprecated circular-json@0.5.9: CircularJSON is in maintenance only, flatted is its successor.
                  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 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 jscs-preset-wikimedia@1.0.1: No longer maintained. We recomment migrating to ESLint with eslint-config-wikimedia.
                  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 nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.
                  npm WARN deprecated uuid@2.0.3: 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 joi@14.3.1: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
                  npm WARN deprecated jscs@3.0.7: JSCS has merged with ESLint! See - https://medium.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2
                  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 WARN cleanup Failed to remove some directories [
                  npm WARN cleanup   [
                  npm WARN cleanup     '/opt/iobroker/node_modules/cpu-features',
                  npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/cpu-features'] {
                  npm WARN cleanup       errno: -39,
                  npm WARN cleanup       code: 'ENOTEMPTY',
                  npm WARN cleanup       syscall: 'rmdir',
                  npm WARN cleanup       path: '/opt/iobroker/node_modules/cpu-features'
                  npm WARN cleanup     }
                  npm WARN cleanup   ],
                  npm WARN cleanup   [
                  npm WARN cleanup     '/opt/iobroker/node_modules/cpu-features',
                  npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/cpu-features'] {
                  npm WARN cleanup       errno: -39,
                  npm WARN cleanup       code: 'ENOTEMPTY',
                  npm WARN cleanup       syscall: 'rmdir',
                  npm WARN cleanup       path: '/opt/iobroker/node_modules/cpu-features'
                  npm WARN cleanup     }
                  npm WARN cleanup   ]
                  npm WARN cleanup ]
                  npm ERR! code 1
                  npm ERR! path /opt/iobroker/node_modules/@serialport/bindings
                  npm ERR! command failed
                  npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
                  npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird betreten
                  npm ERR!   CXX(target) Release/obj.target/bindings/src/serialport.o
                  npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/@serialport/bindings/build“ wird verlassen
                  npm ERR! gyp info it worked if it ends with ok
                  npm ERR! gyp info using node-gyp@9.3.1
                  npm ERR! gyp info using node@18.17.1 | linux | x64
                  npm ERR! gyp info find Python using Python version 3.7.3 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   '/usr/lib/node_modules/npm/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/@serialport/bindings/build/config.gypi',
                  npm ERR! gyp info spawn args   '-I',
                  npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
                  npm ERR! gyp info spawn args   '-I',
                  npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.17.1/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/18.17.1',
                  npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                  npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.17.1/<(target_arch)/node.lib',
                  npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/@serialport/bindings',
                  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! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:78:69: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                  npm ERR!                                                                      ^~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:135:71: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                  npm ERR!                                                                        ^~~~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:175:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                  npm ERR!                                                                       ^~~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:215:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                  npm ERR!                                                                       ^~~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:270:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                  npm ERR!                                                                     ^~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:314:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                  npm ERR!                                                                     ^~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’:
                  npm ERR! ../src/serialport.cpp:329:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’
                  npm ERR!      results->Set(Nan::New<v8::String>("cts").ToLocalChecked(), Nan::New<v8::Boolean>(data->cts));
                  npm ERR!                                                                                                 ^
                  npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
                  npm ERR!                  from ../../../nan/nan.h:60,
                  npm ERR!                  from ../src/./serialport.h:6,
                  npm ERR!                  from ../src/serialport.cpp:1:
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! ../src/serialport.cpp:330:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’
                  npm ERR!      results->Set(Nan::New<v8::String>("dsr").ToLocalChecked(), Nan::New<v8::Boolean>(data->dsr));
                  npm ERR!                                                                                                 ^
                  npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
                  npm ERR!                  from ../../../nan/nan.h:60,
                  npm ERR!                  from ../src/./serialport.h:6,
                  npm ERR!                  from ../src/serialport.cpp:1:
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! ../src/serialport.cpp:331:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’
                  npm ERR!      results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd));
                  npm ERR!                                                                                                 ^
                  npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
                  npm ERR!                  from ../../../nan/nan.h:60,
                  npm ERR!                  from ../src/./serialport.h:6,
                  npm ERR!                  from ../src/serialport.cpp:1:
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:363:76: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                  npm ERR!                                                                             ^~~~~~~~~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’:
                  npm ERR! ../src/serialport.cpp:378:106: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)’
                  npm ERR!      results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate));
                  npm ERR!                                                                                                           ^
                  npm ERR! In file included from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-array-buffer.h:13,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8.h:24,
                  npm ERR!                  from /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:73,
                  npm ERR!                  from ../../../nan/nan.h:60,
                  npm ERR!                  from ../src/./serialport.h:6,
                  npm ERR!                  from ../src/serialport.cpp:1:
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:244:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note: candidate: ‘v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>)’
                  npm ERR!    V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index,
                  npm ERR!                                      ^~~
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/v8-object.h:247:37: note:   candidate expects 3 arguments, 2 provided
                  npm ERR! ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
                  npm ERR! ../src/serialport.cpp:409:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                  npm ERR!    uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                  npm ERR!                                                                       ^~~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp: At global scope:
                  npm ERR! ../src/serialport.cpp:430:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
                  npm ERR!  SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                  npm ERR!                             ^
                  npm ERR! ../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
                  npm ERR!  SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                  npm ERR!                               ^
                  npm ERR! In file included from ../../../nan/nan.h:60,
                  npm ERR!                  from ../src/./serialport.h:6,
                  npm ERR!                  from ../src/serialport.cpp:1:
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1014:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                  npm ERR!        (node::addon_register_func) (regfunc),                          \
                  npm ERR!                                            ^
                  npm ERR! /home/iobroker/.cache/node-gyp/18.17.1/include/node/node.h:1048:3: note: in expansion of macro ‘NODE_MODULE_X’
                  npm ERR!    NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                  npm ERR!    ^~~~~~~~~~~~~
                  npm ERR! ../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’
                  npm ERR!  NODE_MODULE(serialport, init);
                  npm ERR!  ^~~~~~~~~~~
                  npm ERR! make: *** [bindings.target.mk:116: Release/obj.target/bindings/src/serialport.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
                  npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:514:28)
                  npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
                  npm ERR! gyp ERR! System Linux 5.15.108-1-pve
                  npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                  npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings
                  npm ERR! gyp ERR! node -v v18.17.1
                  npm ERR! gyp ERR! node-gyp -v v9.3.1
                  npm ERR! gyp ERR! not ok
                  
                  npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-08-31T13_46_32_906Z-debug-0.log
                  upload [4] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/img/info-big.png img/info-big.png image/png
                  upload [3] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/index.html index.html text/html
                  upload [2] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/index_m.html index_m.html text/html
                  upload [1] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/ping.png ping.png image/png
                  upload [0] ping.admin /opt/iobroker/node_modules/iobroker.ping/admin/words.js words.js application/javascript
                  

                  Yahka habe ich erst einmal übersprungen, da ich denke dass der Ping Adapter die wenigsten Probleme machen sollte.

                  mikeal created this issue in request/request

                  open Request’s Past, Present and Future #3142

                  mikeal created this issue in request/request

                  open Request’s Past, Present and Future #3142

                  Qix- created this issue in visionmedia/debug

                  closed ReDos Vulnerability Regression Visibility Notice #797

                  mikeal created this issue in request/request

                  open Request’s Past, Present and Future #3142

                  DJMarc75 1 Reply Last reply Reply Quote 0
                  • DJMarc75
                    DJMarc75 @Tobi81 last edited by

                    @tobi81 Wenn Du ein aktuelles Backup hast dann tu Dir einen Gefallen und installiere Debian neu - gleich mit Bullseye in der 64 Bit LITE-Version und spül das Backup dann zurück.

                    T 1 Reply Last reply Reply Quote 1
                    • T
                      Tobi81 @DJMarc75 last edited by

                      @djmarc75 Wenn es keine anderen Dinge mehr gibt die ich machen kann, dann muss ich den Container zurückspielen und eine Neuinstallation die Tage machen.

                      Aber vielleicht hat noch jemand eine Idee. 🙂

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tobi81 last edited by

                        Ich hab jetzt eine Neuinstallation auf Debian Bookworm gemacht und bin gerade dabei ioBroker wieder komplett an's Laufen zu bekommen.
                        Hat sich also erledigt.

                        mac89muc 1 Reply Last reply Reply Quote 0
                        • mac89muc
                          mac89muc @Tobi81 last edited by

                          Hallo zusammen,

                          mein ioBroker läuft auf einem Mac mini M2 mit macOS Ventura.
                          Ich nutze aktuell node v16.17.0 npm 8.15.0 js-controller 4.0.24

                          Ich finde keine aktuelle Anleitung für's korrekte Updaten von node.js für meine Konfiguration - kann mir jemand helfen?

                          Reicht es die neue node Version als .pkg Installerdatei für macOS runterzuladen auf https://nodejs.org/de und auszuführen?

                          Muss ich die alte deinstallieren, muss ich nach der Installation noch irgendwelche Verknüpfungen im Terminal herstellen?

                          Möchte mich nicht durchprobieren mit dem Ergebnis, dass im schlimmsten Fall nichts mehr läuft und ich mich mit Backups zurückspielen rumschlage und wieder auf der alten Version bin.

                          Bin über Hilfe zu den verschiedenen Schritten beim Update dankbar.

                          Gruß

                          1 Reply Last reply Reply Quote 0
                          • S
                            Stoni last edited by Stoni

                            Hallo Leute,

                            das große Zittern beginnt wieder, nachdem mir mein ioB empfiehlt, Controller, Admin etc. upzudaten, was aber nicht geht, ehe man nodejs geupdatet hat.
                            Ich habe auf meinem Raspi4 noch Buster mit nodejs 14.21.3.

                            Ich glaube, dass ich auf Bullseye updaten konnte. Zumindest bin ich die Anleitung von @Thomas-Braun durchgegangen. Es kam bis zum Ende keine Fehlermeldung.

                            Nun wollte ich nodejs 14 löschen und die aktuelle Version 18 installieren. Der Puls steigt. Bereits beim Versuch, zu löschen, kommen Fehlermeldungen:

                            
                            pi@raspberrypi:~ $ sudo apt purge --autoremove nodejs* npm node-*
                            Paketlisten werden gelesen… Fertig
                            Abhängigkeitsbaum wird aufgebaut… Fertig
                            Statusinformationen werden eingelesen… Fertig
                            Hinweis: »nodejs-legacy« wird für das Suchmuster »nodejs*« gewählt.
                            Hinweis: »nodejs« wird für das Suchmuster »nodejs*« gewählt.
                            Hinweis: »nodejs-dev« wird für das Suchmuster »nodejs*« gewählt.
                            Hinweis: »nodejs-doc« wird für das Suchmuster »nodejs*« gewählt.
                            Hinweis: »nodejs« wird an Stelle von »nodejs-legacy« gewählt.
                            Hinweis: »nodejs« wird an Stelle von »nodejs-dev« gewählt.
                            E: Paket node-v14.9.0-linux-armv6l kann nicht gefunden werden.
                            E: Mittels des Musters »node-v14.9.0-linux-armv6l« konnte kein Paket gefunden werden.
                            E: Paket node-v14.9.0-linux-armv6l.tar.xz kann nicht gefunden werden.
                            E: Mittels des Musters »node-v14.9.0-linux-armv6l.tar.xz« konnte kein Paket gefunden werden.
                            
                            

                            Weiter komme ich nicht.

                            Ist das der richtige Weg?

                            sudo rm `sudo find / -name nodesource.gpg`
                            sudo rm `sudo find / -name nodesource.key`
                            sudo rm /etc/apt/sources.list.d/nodesource.list
                            
                            NODE_MAJOR=18
                            sudo apt update
                            sudo apt install -y ca-certificates curl gnupg
                            sudo mkdir -p /etc/apt/keyrings
                            curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
                            echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_${NODE_MAJOR}.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list
                            sudo apt update
                            sudo apt install nodejs
                            

                            Können die Profis weiterhelfen?

                            Vielen Dank!!
                            Stoni

                            Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Stoni last edited by

                              @stoni sagte in Troubleshooting NodeJS update:

                              Weiter komme ich nicht.

                              Welcher Pi?

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                Stoni @Thomas Braun last edited by

                                @thomas-braun

                                Pi4

                                Bullseye hat geklappt

                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Homoran
                                  Homoran Global Moderator Administrators @Stoni last edited by

                                  @stoni sagte in Troubleshooting NodeJS update:

                                  armv6l

                                  klingt nach pi1

                                  1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Stoni last edited by Thomas Braun

                                    @stoni sagte in Troubleshooting NodeJS update:

                                    Pi4

                                    Und warum liegt dann da eine Datei node-v14.9.0-linux-armv6lin deinem Home herum? Hat da a) nix zu suchen und ist b) auch falsch.

                                    Lösch die.

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      Stoni @Thomas Braun last edited by

                                      @thomas-braun wie lösche ich die?

                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Stoni last edited by

                                        @stoni
                                        Erstmal schauen wo die liegt:

                                        ls -lAh
                                        
                                        S 1 Reply Last reply Reply Quote 0
                                        • S
                                          Stoni @Thomas Braun last edited by

                                          @thomas-braun

                                          pi@raspberrypi:~ $ ls -lAh
                                          insgesamt 19M
                                          -rw------- 1 pi pi 7,1K 15. Sep 16:56 .bash_history
                                          -rw-r--r-- 1 pi pi  220 26. Sep 2019  .bash_logout
                                          -rw-r--r-- 1 pi pi 3,6K 27. Nov 2019  .bashrc
                                          drwxr-xr-x 3 pi pi 4,0K 27. Nov 2019  .cache
                                          drwx------ 3 pi pi 4,0K 27. Nov 2019  .config
                                          -rw-r--r-- 1 pi pi 161K 30. Nov 2020  deCONZ_ConBeeII_0x26680700.bin.GCF
                                          drwx------ 3 pi pi 4,0K 27. Nov 2019  .gnupg
                                          drwxr-xr-x 2 pi pi 4,0K 27. Nov 2019  .iobroker
                                          drwxr-xr-x 3 pi pi 4,0K 27. Nov 2019  .local
                                          drwxr-xr-x 6 pi pi 4,0K 27. Aug 2020  node-v14.9.0-linux-armv6l
                                          -rw-r--r-- 1 pi pi  19M 27. Aug 2020  node-v14.9.0-linux-armv6l.tar.xz
                                          drwxr-xr-x 4 pi pi 4,0K 27. Nov 2019  .npm
                                          -rw------- 1 pi pi   36 27. Nov 2019  .npmrc
                                          -rw-r--r-- 1 pi pi  807 26. Sep 2019  .profile
                                          
                                          
                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @Stoni last edited by

                                            @stoni sagte in Troubleshooting NodeJS update:

                                            rm -rf node-v14.9*
                                            

                                            Und dann versuch mal das Skript von hier:
                                            https://forum.iobroker.net/topic/68035/iob-node-fix-skript

                                            S 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            955
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            nodejs 18 nodejs update
                                            60
                                            504
                                            84523
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo