NEWS
Test Adapter mihome-vacuum v2.0.x
-
Also ich hab es nun gefixed bekommen.
Node12 installieren
IoBroker fix
npm rebuild im IoBroker Verzeichnis
npm rebuild --build-from-source canvas
Iobroker fixSeitdem funktioniert es auch mit node 12
@Kevin IObroker fix ging durch..
beim npm Fehler:
root@debian:/opt/iobroker# npm rebuild > iobroker@1.0.6 install /opt/iobroker/node_modules/iobroker > node lib/setup.js NPM version: 6.13.4 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! NPM 5 is currently NOT supported! Please use "npm install -g npm@4" to downgrade npm to 4.x and try again. You need to make sure to downgrade again with the above command after you installed an update to nodejs/npm! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker@1.0.6 install: `node lib/setup.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker@1.0.6 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_32_00_912Z-debug.log root@debian:/opt/iobroker# npm rebuild --build-from-source canvas > canvas@2.6.1 install /opt/iobroker/node_modules/canvas > node-pre-gyp install --fallback-to-build node-pre-gyp WARN Using request for node-pre-gyp https download Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Linux 4.9.0-4-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) node-pre-gyp ERR! System Linux 4.9.0-4-amd64 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas@2.6.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_32_42_894Z-debug.log root@debian:/opt/iobroker# npm rebuild --build-from-source canvas > canvas@2.6.1 install /opt/iobroker/node_modules/canvas > node-pre-gyp install --fallback-to-build node-pre-gyp WARN Using request for node-pre-gyp https download Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Linux 4.9.0-4-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) node-pre-gyp ERR! System Linux 4.9.0-4-amd64 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas@2.6.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_36_07_361Z-debug.logSonos, Intel Nuc, Iobroker Pro, Proxmox, IPad Air (Wand), Vis, Xiaomi, Devolo, Bose, Philips Hue, Instar, Synology
-
@Kevin IObroker fix ging durch..
beim npm Fehler:
root@debian:/opt/iobroker# npm rebuild > iobroker@1.0.6 install /opt/iobroker/node_modules/iobroker > node lib/setup.js NPM version: 6.13.4 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! NPM 5 is currently NOT supported! Please use "npm install -g npm@4" to downgrade npm to 4.x and try again. You need to make sure to downgrade again with the above command after you installed an update to nodejs/npm! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker@1.0.6 install: `node lib/setup.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker@1.0.6 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_32_00_912Z-debug.log root@debian:/opt/iobroker# npm rebuild --build-from-source canvas > canvas@2.6.1 install /opt/iobroker/node_modules/canvas > node-pre-gyp install --fallback-to-build node-pre-gyp WARN Using request for node-pre-gyp https download Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Linux 4.9.0-4-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) node-pre-gyp ERR! System Linux 4.9.0-4-amd64 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas@2.6.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_32_42_894Z-debug.log root@debian:/opt/iobroker# npm rebuild --build-from-source canvas > canvas@2.6.1 install /opt/iobroker/node_modules/canvas > node-pre-gyp install --fallback-to-build node-pre-gyp WARN Using request for node-pre-gyp https download Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Linux 4.9.0-4-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) node-pre-gyp ERR! System Linux 4.9.0-4-amd64 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas@2.6.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_36_07_361Z-debug.log -
@Kevin IObroker fix ging durch..
beim npm Fehler:
root@debian:/opt/iobroker# npm rebuild > iobroker@1.0.6 install /opt/iobroker/node_modules/iobroker > node lib/setup.js NPM version: 6.13.4 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! NPM 5 is currently NOT supported! Please use "npm install -g npm@4" to downgrade npm to 4.x and try again. You need to make sure to downgrade again with the above command after you installed an update to nodejs/npm! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker@1.0.6 install: `node lib/setup.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker@1.0.6 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_32_00_912Z-debug.log root@debian:/opt/iobroker# npm rebuild --build-from-source canvas > canvas@2.6.1 install /opt/iobroker/node_modules/canvas > node-pre-gyp install --fallback-to-build node-pre-gyp WARN Using request for node-pre-gyp https download Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Linux 4.9.0-4-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) node-pre-gyp ERR! System Linux 4.9.0-4-amd64 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas@2.6.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_32_42_894Z-debug.log root@debian:/opt/iobroker# npm rebuild --build-from-source canvas > canvas@2.6.1 install /opt/iobroker/node_modules/canvas > node-pre-gyp install --fallback-to-build node-pre-gyp WARN Using request for node-pre-gyp https download Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12) gyp ERR! System Linux 4.9.0-4-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) node-pre-gyp ERR! System Linux 4.9.0-4-amd64 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the canvas@2.6.1 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-07T09_36_07_361Z-debug.log@xADDRx Docker auf einer Synology? Ansonsten: Meld dich nicht als root an!
Da scheint mir die Installation von node mal wieder in die Hose gegangen zu sein.
Schau hier rein:
https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian -
@xADDRx Docker auf einer Synology? Ansonsten: Meld dich nicht als root an!
Da scheint mir die Installation von node mal wieder in die Hose gegangen zu sein.
Schau hier rein:
https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian -
@Thomas-Braun Keine Synology! Node habe ich nach der Anleitung damals ohne Fehler installiert gehabt.
@xADDRx
Dann ist da wohl alles mögliche verfummelt. Deine Version vom js-controller ist auch uralt. Jedenfalls lt. Log.
root-Login ist jedenfalls absoluter Quark. Kannste Mal den @Freaknet fragen. Nur ein paar Postings zuvor.Wenn du Hilfe beim glattziehen möchtest mach am besten einen neuen, eigenen Thread dafür auf. Hier führt das zu weit.
-
@xADDRx
Dann ist da wohl alles mögliche verfummelt. Deine Version vom js-controller ist auch uralt. Jedenfalls lt. Log.
root-Login ist jedenfalls absoluter Quark. Kannste Mal den @Freaknet fragen. Nur ein paar Postings zuvor.Wenn du Hilfe beim glattziehen möchtest mach am besten einen neuen, eigenen Thread dafür auf. Hier führt das zu weit.
@Thomas-Braun Hmmm. Also JS Controller ist aug 3.1.6. Auch habe ich sonst keine Porbleme. Sowohl die Karte als auch die Räume haben ja vorm Adapter Update funktionert und wurden geladen sobald man auf dem Button geklickt hat...
Sonos, Intel Nuc, Iobroker Pro, Proxmox, IPad Air (Wand), Vis, Xiaomi, Devolo, Bose, Philips Hue, Instar, Synology
-
@Thomas-Braun Hmmm. Also JS Controller ist aug 3.1.6. Auch habe ich sonst keine Porbleme. Sowohl die Karte als auch die Räume haben ja vorm Adapter Update funktionert und wurden geladen sobald man auf dem Button geklickt hat...
@xADDRx Das Install-Log zeigt was anderes an.
-
@xADDRx Das Install-Log zeigt was anderes an.
@Thomas-Braun Was sollte ich am besten tun??
Sonos, Intel Nuc, Iobroker Pro, Proxmox, IPad Air (Wand), Vis, Xiaomi, Devolo, Bose, Philips Hue, Instar, Synology
-
@Thomas-Braun Was sollte ich am besten tun??
Versuch mal das:
iobroker stop sudo apt-get update sudo apt-get upgrade sudo apt-get --purge remove nodejs -y sudo apt-get autoremove -y sudo reboot curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add - sudo sh -c "echo deb https://deb.nodesource.com/node_12.x disco main \> /etc/apt/sources.list.d/nodesource.list" sudo apt-get update sudo apt-get install nodejs -y npm install -g npm@6 sudo reboot iobroker update iobroker upgrade self iobroker fix cd /opt/iobroker/ npm rebuild -
Versuch mal das:
iobroker stop sudo apt-get update sudo apt-get upgrade sudo apt-get --purge remove nodejs -y sudo apt-get autoremove -y sudo reboot curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add - sudo sh -c "echo deb https://deb.nodesource.com/node_12.x disco main \> /etc/apt/sources.list.d/nodesource.list" sudo apt-get update sudo apt-get install nodejs -y npm install -g npm@6 sudo reboot iobroker update iobroker upgrade self iobroker fix cd /opt/iobroker/ npm rebuild@Kevin Woher weißt du dass da Disco läuft?
So wird das mutmaßliche Installationschaos doch nur noch größer...
Da dürfte eher ein Debian laufen, kein Ubuntu. -
@Kevin Woher weißt du dass da Disco läuft?
So wird das mutmaßliche Installationschaos doch nur noch größer...
Da dürfte eher ein Debian laufen, kein Ubuntu. -
@Thomas-Braun so habe ich es bei mir zum laufen gebracht. Auf raspbian
@Kevin Dann hast du jetzt ein falsches Repo drin. Disco Dingo ist nicht für Raspian gedacht.
Vermutlich bist Du auch auf einem hervorragenden Weg dein System zu zerballern. -
@Thomas-Braun Was sollte ich am besten tun??
@xADDRx Mach einen neuen Thread auf und poste da die Ausgabe von
lsb_release -asowie von
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejsKomplette Eingaben und auch Ausgaben posten, nichts kürzen oder abändern...
Das gleiche würde ich @Kevin auch empfehlen...
-
falls du den Container von Buanet nutzt, dann nimm die neue Version 5 davon. Das ist eine saubere Installation mit node 12 und der aktuellste js-controller..
Ich empfehle ich dir folgende Vorgehensweise:
- Backup von Iobroker mit z.B. backitup.
- neues leeres Volume anlegen.
- Container Image V 5 stable laden und starten
- In den container wechseln und das backup einspielen.
Dann sollte alles laufen
@K_o_bold
Habe die Version 5 drauf und bisher ausschließlich den Container von Buanet genutz. Funktioniert trotzdem nicht.Entsprechend der Anleitung von Buanet habe ich über portainer den ioBroker Container über Recreate neu erstellt und das neueste Image eingespielt. (siehe Bild)
-
@xADDRx Mach einen neuen Thread auf und poste da die Ausgabe von
lsb_release -asowie von
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejsKomplette Eingaben und auch Ausgaben posten, nichts kürzen oder abändern...
Das gleiche würde ich @Kevin auch empfehlen...
-
MIHOME App öffnen , dann geht es
Hallo,
ich habe das gleiche Problem. Ich habe zwei Roborock der ersten Generation, und der Adapter lief immer korrekt. Seit Update auf 2.x aber bleibt die Instanze des ersten Saugers auf "gelb" stehen, nur die des zweiten Saugers bekommt eine Verbindung.
Log des ersten Saugers:
{der Hinweis auf die 10 Minuten wiederholt sich dann endlos} mihome-vacuum.0 2020-08-10 17:10:56.044 info (11238) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-10 17:10:36.040 info (11238) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-10 17:10:16.571 info (11238) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-08-10 17:10:16.080 info (11238) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-10 17:10:16.063 info (11238) New generation or new fw(3.5.4,004004) detected, create new states goto and zoneclean mihome-vacuum.0 2020-08-10 17:10:16.017 info (11238) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-08-10 17:10:16.014 info (11238) Expert mode disabled, states deleted mihome-vacuum.0 2020-08-10 17:10:15.972 info (11238) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.20.1, js-controller: 3.1.4 host.iobroker 2020-08-10 17:10:10.405 info instance system.adapter.mihome-vacuum.0 started with pid 11238Konfiguration:
Adapter Mihome-vaccuum 2.1.1
Erster Sauger (der ohne Verbindung):: Port des Robot: 54321; eigener Port: 54321
Zweiter Sauger (der mit Verbindung): Port des Robot: 54321; eigener Port: 54322
Aktuelle Firmware auf beiden Saugern: 3.5.8_004018Der Tipp, die Mihome-App bei der Anmeldung geöffnet zu halten, hat nicht genutzt.
Weiß da jemand Abhilfe?
Grüße, EckartS
-
Hallo,
ich habe das gleiche Problem. Ich habe zwei Roborock der ersten Generation, und der Adapter lief immer korrekt. Seit Update auf 2.x aber bleibt die Instanze des ersten Saugers auf "gelb" stehen, nur die des zweiten Saugers bekommt eine Verbindung.
Log des ersten Saugers:
{der Hinweis auf die 10 Minuten wiederholt sich dann endlos} mihome-vacuum.0 2020-08-10 17:10:56.044 info (11238) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-10 17:10:36.040 info (11238) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-10 17:10:16.571 info (11238) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-08-10 17:10:16.080 info (11238) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-10 17:10:16.063 info (11238) New generation or new fw(3.5.4,004004) detected, create new states goto and zoneclean mihome-vacuum.0 2020-08-10 17:10:16.017 info (11238) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-08-10 17:10:16.014 info (11238) Expert mode disabled, states deleted mihome-vacuum.0 2020-08-10 17:10:15.972 info (11238) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v10.20.1, js-controller: 3.1.4 host.iobroker 2020-08-10 17:10:10.405 info instance system.adapter.mihome-vacuum.0 started with pid 11238Konfiguration:
Adapter Mihome-vaccuum 2.1.1
Erster Sauger (der ohne Verbindung):: Port des Robot: 54321; eigener Port: 54321
Zweiter Sauger (der mit Verbindung): Port des Robot: 54321; eigener Port: 54322
Aktuelle Firmware auf beiden Saugern: 3.5.8_004018Der Tipp, die Mihome-App bei der Anmeldung geöffnet zu halten, hat nicht genutzt.
Weiß da jemand Abhilfe?
Grüße, EckartS
-
@Thomas-Braun Hmmm. Also JS Controller ist aug 3.1.6. Auch habe ich sonst keine Porbleme. Sowohl die Karte als auch die Räume haben ja vorm Adapter Update funktionert und wurden geladen sobald man auf dem Button geklickt hat...
@xADDRx folgendes hat mir geholfen:
sudo iobroker stop cd /opt/iobroker sudo apt update sudo apt-get install build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev sudo npm install canvas --unsafe-perm=trueKatrte geht wieder und Räume wurden geladen
Sonos, Intel Nuc, Iobroker Pro, Proxmox, IPad Air (Wand), Vis, Xiaomi, Devolo, Bose, Philips Hue, Instar, Synology
-
Hallo,
ich habe erfolgreich meinen S6 maxv im ioBroker installiert, für meine beiden Etagen jeweils eine Karte erstellt, Räume abgetrennt, umbenannt und Moduseinstellungen gesetzt.Wenn ich nun ein "roomClean" Objekt auslose passiert im Log das Folgende:
mihome-vacuum.0 2020-08-13 20:39:22.260 info (14105) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-08-13 20:39:21.858 info (14105) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-13 20:39:21.801 info (14105) New generation or new fw(3.5.8,4436) detected, create new states goto and zoneclean mihome-vacuum.0 2020-08-13 20:39:21.714 info (14105) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-08-13 20:39:21.711 info (14105) Expert mode disabled, states deleted mihome-vacuum.0 2020-08-13 20:39:21.607 info (14105) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.18.3, js-controller: 3.1.6 mihome-vacuum.0 2020-08-13 20:38:49.057 info (12745) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-08-13 20:38:49.055 info (12745) terminating mihome-vacuum.0 2020-08-13 20:38:49.044 error (12745) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/roomManager.js:144:51 at /opt/iobroker/node_modules/iobroker.js-controller/lib/ad mihome-vacuum.0 2020-08-13 20:38:49.040 error (12745) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-08-13 20:37:33.316 info (12745) create states for water box filter mihome-vacuum.0 2020-08-13 20:37:33.313 info (12745) create states for water box mihome-vacuum.0 2020-08-13 20:37:14.454 info (12745) create state for carpet_mode mihome-vacuum.0 2020-08-13 20:37:13.819 info (12745) set nächster Timer: Nicht verfügbar mihome-vacuum.0 2020-08-13 20:37:13.441 info (12745) Connected mihome-vacuum.0 2020-08-13 20:37:13.381 info (12745) connecting, this can take up to 10 minutes ... mihome-vacuum.0 2020-08-13 20:37:13.369 info (12745) New generation or new fw(3.5.8,4436) detected, create new states goto and zoneclean mihome-vacuum.0 2020-08-13 20:37:13.290 info (12745) Create state clean_home for controlling by cloud adapter mihome-vacuum.0 2020-08-13 20:37:13.288 info (12745) Expert mode disabled, states deleted mihome-vacuum.0 2020-08-13 20:37:13.188 info (12745) starting. Version 2.1.1 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v12.18.3, js-controller: 3.1.6 mihome-vacuum.0 2020-08-13 20:36:40.744 info (9488) Terminated (NO_ERROR): Without reason mihome-vacuum.0 2020-08-13 20:36:40.742 info (9488) terminating mihome-vacuum.0 2020-08-13 20:36:40.724 error at processTicksAndRejections (internal/process/task_queues.js:97:5) mihome-vacuum.0 2020-08-13 20:36:40.724 error at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49 mihome-vacuum.0 2020-08-13 20:36:40.724 error at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23) mihome-vacuum.0 2020-08-13 20:36:40.724 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInRedis.js:673:13 mihome-vacuum.0 2020-08-13 20:36:40.724 error at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:6757:17 mihome-vacuum.0 2020-08-13 20:36:40.724 error at /opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/roomManager.js:144:51 mihome-vacuum.0 2020-08-13 20:36:40.724 error (9488) TypeError: Cannot read property 'val' of null mihome-vacuum.0 2020-08-13 20:36:40.717 error (9488) uncaught exception: Cannot read property 'val' of null mihome-vacuum.0 2020-08-13 20:35:27.231 info (9488) create states for water box filter mihome-vacuum.0 2020-08-13 20:35:27.230 info (9488) create states for water box mihome-vacuum.0 2020-08-13 20:35:18.347 info (9488) create state for carpet_mode mihome-vacuum.0 2020-08-13 20:35:17.329 info (9488) Connected mihome-vacuum.0 2020-08-13 20:35:07.224 info (9488) connecting, this can take up to 10 minutes ...Der Robi mach garnichts und der Adapter startet neu.
Kann mir jemand sagen was das Problem ist?Habe gerade noch diesen Post entdeckt und es mit "roomFanPower" auf BALANCED60 nochmal probiert.
mihome-vacuum.0 2020-08-13 20:47:57.910 error (14105) TypeError: Cannot read property 'val' of null at /opt/iobroker/node_modules/iobroker.mihome-vacuum/lib/roomManager.js:144:51 at /opt/iobroker/node_modules/iobroker.js-controller/lib/ad mihome-vacuum.0 2020-08-13 20:47:57.903 error (14105) uncaught exception: Cannot read property 'val' of nullGleiches Ergebnis.
Support us
854
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge