NEWS
Adapter-Installationen schlagen fehl
-
Hallo Leute,
im Moment kann ich leider keine Updates mehr machen. Egal welchen Adapter ich installieren möchte nach dem "System Call" geht nichts mehr.
Neustarts gemacht
npm intall iobroker gemacht
JS-Controller 0.8.4
Was mir noch aufgefallen ist: Bei jeder Adapterinstallation wird sayit mitinstalliert.
aber selbst das geht nicht
> iobroker 2016-01-23 17:15:20 error host.raspberrypi Cannot install iobroker.sayit: 254
Beim Wolf Adapter kam das hier ` > $ ./iobroker add wolf
npm install iobroker.wolf –production --prefix "/opt/iobroker" (System call)
npm
WARN
enoent ENOENT, open '/opt/iobroker/package.json'
npm
WARN
mongodb-core@1.2.28 requires a peer of kerberos@~0.0 but none was installed.
npm WARN
iobroker No description
npm
WARN iobroker No repository field.
npm
WARN
iobroker No README data
npm
WARN
iobroker No license field.
host.raspberrypi install adapter wolf
npm install --production --prefix "/opt/iobroker/node_modules/iobroker.wolf" (System call)
npm
ERR!
Linux 4.1.7-v7+
npm ERR! argv "node" "/usr/local/bin/npm" "install" "--production" "--prefix" "/opt/iobroker/node_modules/iobroker.wolf"
npm ERR! node v0.12.6npm
ERR! npm v3.5.2
npm ERR!
Cannot read property 'target' of nullnpm ERR!
npm ERR! If you need help, you may report this error at:
npm
ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /opt/npm-debug.log
Cannot install iobroker.wolf: 1
ERROR: process exited with code 25 `
könnt ihr mir helfen?
-
hi,
scheint leider nun ein Standard-Problem mit den Jessie-Image zu werden.
Einmal vorher folgendes ausführen:
sudo apt-get install libkrb5-dev
Die Begründung steht hier:
-
Hi Nobody,
vielen Dank für Deinen Tipp, leider bringt es keiner Besserung.
Nicht mal Updates gehen mehr
Hier Beispiel von Node-Red Update:
$ ./iobroker upgrade node-red npm install iobroker.node-red --production --prefix "/opt/iobroker" (System call) npm ERR! Linux 4.1.7-v7+ npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6npm ERR! npm v3.5.2 npm ERR! code ECONNRESETnpm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESETnpm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+ npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6 npm ERR! npm v3.5.2npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity.npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+ npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itselfnpm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity.npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESETnpm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESETnpm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that thenpm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESETnpm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itselfnpm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESET npm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESET npm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! code ECONNRESETnpm ERR! errno ECONNRESET npm ERR! syscall read npm ERR! network read ECONNRESETnpm ERR! network This is most likely not a problem with npm itself npm ERR! network and is related to network connectivity. npm ERR! network In most cases you are behind a proxy or have bad network settings. npm ERR! network npm ERR! network If you are behind a proxy, please make sure that the npm ERR! network 'proxy' config is set properly. See: 'npm help config' npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker" npm ERR! node v0.12.6 npm ERR! npm v3.5.2 npm ERR! shasum check failed for /tmp/npm-2687-e3746185/registry.npmjs.org/when/-/when-3.7.7.tgznpm ERR! Expected: aba03fc3bb736d6c88b091d013d8a8e590d84718 npm ERR! Actual: e70ad1d480b0a11ef0f7d0e7542269a06a693a85 npm ERR! From: https://registry.npmjs.org/when/-/when-3.7.7.tgz npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! <https: github.com/npm/issues=""> npm ERR! Please include the following file with any support request: npm ERR! /opt/npm-debug.log ERROR: host.raspberrypi Cannot install iobroker.node-red: 1 ERROR: process exited with code 25</https:>
-
ok, das ist jetzt aber ein anderer Fehler und auch kein spezifischer Fehler für die Installation mit ioBroker sondern entweder ein Netzproblem oder ein Problem mit npm selbst.
Klappt der Zugang zum Internet vom System aus?
Falls der Zugriff auf das Internet und auf die npm-Server geht, versuche mal den npm Cache komplett zu löschen und es dann erneut zu versuchen.
sudo rm -rf ~/.npm
Was mir noch aufgefallen ist:
` > npm ERR! node v0.12.6npmERR! npm v3.5.2 `
Die npm Version passt nicht richtig zu node.js Version.
Wenn ich mich richtig erinnere sollte alles unter node.js 4.x eigentlich nur npm Versionen 2.x verwenden.
-
du bist spitze! ich hatte da mal ein Update auf NPM 3.x gemacht blöderweise…
hab mit````
npm install npm@2 -gdanke!!!!