[fixed] Fehler beim Updaten von sayit
-
Hallo,
seit den Wochenende habe ich ein Problem damit den sayit Adapter upzudaten.
Auch ein deinstallieren und neu installiert schlägt fehl.
root@pi01:/opt/iobroker# iobroker upgrade sayit npm install iobroker.sayit --production --prefix "/opt/iobroker" (System call) npm http GET https://registry.npmjs.org/iobroker.sayit npm http 304 https://registry.npmjs.org/iobroker.sayit npm http GET https://registry.npmjs.org/jsftp npm http GET https://registry.npmjs.org/ivona-node npm http 304 https://registry.npmjs.org/jsftp npm http 304 https://registry.npmjs.org/ivona-node npm http GET https://registry.npmjs.org/aws4 npm http 304 https://registry.npmjs.org/aws4 npm http GET https://registry.npmjs.org/lru-cache npm http 304 https://registry.npmjs.org/lru-cache npm http GET https://registry.npmjs.org/debug/2.2.0 npm http GET https://registry.npmjs.org/ftp-response-parser/1.0.0 npm http GET https://registry.npmjs.org/parse-listing/1.1.3 npm http GET https://registry.npmjs.org/once/1.3.0 npm http GET https://registry.npmjs.org/unorm/1.4.1 npm http GET https://registry.npmjs.org/event-stream/3.1.7 npm http 304 https://registry.npmjs.org/debug/2.2.0 npm http 304 https://registry.npmjs.org/parse-listing/1.1.3 npm http 304 https://registry.npmjs.org/unorm/1.4.1 npm http 304 https://registry.npmjs.org/ftp-response-parser/1.0.0 npm http 304 https://registry.npmjs.org/once/1.3.0 npm http 304 https://registry.npmjs.org/event-stream/3.1.7 npm http GET https://registry.npmjs.org/ms/0.7.1 npm http 304 https://registry.npmjs.org/ms/0.7.1 npm http GET https://registry.npmjs.org/pause-stream/0.0.11 npm http GET https://registry.npmjs.org/split npm http GET https://registry.npmjs.org/stream-combiner npm http GET https://registry.npmjs.org/through npm http GET https://registry.npmjs.org/duplexer npm http GET https://registry.npmjs.org/from npm http GET https://registry.npmjs.org/map-stream npm http 304 https://registry.npmjs.org/pause-stream/0.0.11 npm http 304 https://registry.npmjs.org/stream-combiner npm http 304 https://registry.npmjs.org/from npm http 200 https://registry.npmjs.org/split npm http 304 https://registry.npmjs.org/duplexer npm http 304 https://registry.npmjs.org/through npm http 304 https://registry.npmjs.org/map-stream npm http GET https://registry.npmjs.org/readable-stream npm http 304 https://registry.npmjs.org/readable-stream npm http GET https://registry.npmjs.org/core-util-is npm http GET https://registry.npmjs.org/isarray/0.0.1 npm http GET https://registry.npmjs.org/string_decoder npm http GET https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/isarray/0.0.1 npm http 304 https://registry.npmjs.org/inherits npm http 304 https://registry.npmjs.org/string_decoder npm http 304 https://registry.npmjs.org/core-util-is Killed npm ERR! iobroker.sayit@1.0.0 install: `node main.js --install` npm ERR! Exit status 137 npm ERR! npm ERR! Failed at the iobroker.sayit@1.0.0 install script. npm ERR! This is most likely a problem with the iobroker.sayit package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node main.js --install npm ERR! You can get their info via: npm ERR! npm owner ls iobroker.sayit npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.18.11-v7+ npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker.sayit" "--production" "--prefix" "/opt/iobroker" npm ERR! cwd /opt/iobroker npm ERR! node -v v0.10.22 npm ERR! npm -v 1.3.14 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /opt/iobroker/npm-debug.log npm ERR! not ok code 0 host.pi01 Cannot install iobroker.sayit: 1Hat jemand eine Idee wie ich den Fehler eingrenzen kann?
-
/opt/iobroker/npm-debug.log ?
-
Thema hat sich erledigt.
Das System machte nach über einem Jahr updaten immer mehr Probleme. Habe mich entschlossen, alles neu aufzubauen. Mit jessie und ohne Restmüll läuft jetzt alles wieder flott. auch die sayit Updateprobleme sind plötzlich weg.
