NEWS
Yahka lässt sich nicht installieren
-
Hi guys,
habe meinen ioBroker vom Raspberry auf eine virtuelle Linux Maschine (Debian GNU/Linux 9 x64) umgezogen.
Leider kann ich dort den Homekit bzw. Yahka Adapter nicht mehr installieren.
Hat jemand eine Idee? Erhalte folgende Fehlermeldung.
Kompletter Auszug des Installationsfensters:
$ ./iobroker add yahka --host ioBroker NPM version: 6.4.1 npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call) gyp ERR! build error gyp ERR! stack Error: not found: makegyp ERR! stack at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19) gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16 gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5 gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Linux 4.9.0-7-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /opt/iobroker/node_modules/curve25519-n gyp ERR! node -v v8.12.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLEnpm ERR! errno 1 npm ERR! curve25519-n@1.4.0 install: `node-gyp rebuild`npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the curve25519-n@1.4.0 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! /root/.npm/_logs/2018-11-09T12_33_37_926Z-debug.log host.ioBroker install adapter yahka NPM version: 6.4.1npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call) gyp ERR! build error gyp ERR! stack Error: not found: makegyp ERR! stack at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29) gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5 gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Linux 4.9.0-7-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /opt/iobroker/node_modules/curve25519-n gyp ERR! node -v v8.12.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLEnpm ERR! errno 1 npm ERR! curve25519-n@1.4.0 install: `node-gyp rebuild`npm ERR! Exit status 1npm ERR! npm ERR! Failed at the curve25519-n@1.4.0 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! /root/.npm/_logs/2018-11-09T12_33_48_573Z-debug.log host.ioBroker install adapter yahka NPM version: 6.4.1npm install iobroker.yahka --production --save --prefix "/opt/iobroker" (System call) gyp ERR! build error gyp ERR! stack Error: not found: makegyp ERR! stack at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12) gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19) gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5 gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Linux 4.9.0-7-amd64 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /opt/iobroker/node_modules/curve25519-n gyp ERR! node -v v8.12.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm ERR! code ELIFECYCLEnpm ERR! errno 1npm ERR! curve25519-n@1.4.0 install: `node-gyp rebuild`npm ERR! Exit status 1npm ERR! npm ERR! Failed at the curve25519-n@1.4.0 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! /root/.npm/_logs/2018-11-09T12_33_58_665Z-debug.log host.ioBroker install adapter yahka ERROR: host.ioBroker Cannot install yahka ERROR: process exited with code 13 -
lass mich mal für dich googeln ..
..
..
https://www.google.com/search?q=Error%3 … 3A+makegyp
Der erste Link sieht mal ziemlich vielversprechend aus
-
Danke! Dieser Foreneintrag ist mir trotz intensivem suchen durch die Lappen gegangen.
Konnte den Adapter dann tatsächlich installieren. Allerdings lässt er sich nicht starten.
Kann die kommenden Log-Einträge nicht richtig interpretieren. Vll kannst Du was damit anfangen?
2018-11-11 12:02:39.933 - error: Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:96 2018-11-11 12:02:39.933 - error: Caught by controller[0]: throw err 2018-11-11 12:02:39.933 - error: Caught by controller[0]: ^ 2018-11-11 12:02:39.933 - error: Caught by controller[0]: Error: Could not locate the bindings file. Tried: 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/build/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/build/Debug/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/build/Release/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/out/Debug/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/Debug/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/out/Release/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/Release/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/build/default/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: → /opt/iobroker/node_modules/ed25519-hap/compiled/8.12.0/linux/x64/ed25519.node 2018-11-11 12:02:39.933 - error: Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:93:9) 2018-11-11 12:02:39.933 - error: Caught by controller[0]: at Object. (/opt/iobroker/node_modules/ed25519-hap/index.js:1:99) 2018-11-11 12:02:39.933 - error: Caught by controller[0]: at Module._compile (module.js:653:30) 2018-11-11 12:02:39.933 - error: Caught by controller[0]: at Object.Module._extensions..js (module.js:664:10) 2018-11-11 12:02:39.933 - error: Caught by controller[0]: at Module.load (module.js:566:32) 2018-11-11 12:02:39.934 - error: Caught by controller[0]: at tryModuleLoad (module.js:506:12) 2018-11-11 12:02:39.934 - error: Caught by controller[0]: at Function.Module._load (module.js:498:3) 2018-11-11 12:02:39.934 - error: Caught by controller[0]: at Module.require (module.js:597:17) 2018-11-11 12:02:39.934 - error: Caught by controller[0]: at require (internal/module.js:11:18) 2018-11-11 12:02:39.934 - error: Caught by controller[0]: at Object. (/opt/iobroker/node_modules/hap-nodejs/lib/HAPServer.js:8:15) 2018-11-11 12:02:39.934 - error: host.ioBroker-test instance system.adapter.yahka.0 terminated with code 1 () -
im Dateianhang das Log aus dem Verzeichnis /opt/iobroker/log.
Ich hoffe du hast das gemeint?
In der ioBroker-Gui bekome ich nur die Einträge, die ich vorhin gesendet habe.
Oder gibt es ein separates Install-Log?
-
Moin,
also ich konnte den Adapter nun ans laufen bringen. Aber leider weiß ich nicht, was letztendlich das Problem gelöst hat.
Nach der Installation der zwei fehlenden Pakete habe ich den Adapter insgesamt 3x über die Gui installiert. Beim dritten mal hat es funktioniert.
Werde heute Abend mal ein paar Geräte einfügen und testen, ob die Bridge auch gefunden wird.
Sorry, dass ich keine vernünftige Rückmeldung gebenkann. Trotzdem 1000 Dank !
Support us
635
Online32.7k
Benutzer82.4k
Themen1.3m
Beiträge