NEWS
Upgrade io.broker admin von 2.0.7 auf 2.0.9 schlug fehl
-
Hallo Zusammen !
Bei meinem heutigen Upgrade des ioboker.admin von Version 2.0.7 auf 2.0.9 blieb die Software hängen.
Habe dann über putty folgendes eingegeben:
sudo pgrep -f '^io.*' |xargs kill -9
cd /opt/iobroker
sudo npm cache clean
sudo npm install iobroker.js-controller
sudo npm install iobroker.admin
sudo chmod 777 * -R
iobroker l i
iobroker start
hier das Ergebnis:
npm ERR! Linux 4.4.38-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "iobroker.js-controller"
npm ERR! node v4.8.0
npm ERR! npm v2.15.11
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client
npm ERR! code ENOTEMPTY
npm ERR! errno -39
npm ERR! syscall rmdir
npm ERR! ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! error rolling back Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client'
npm ERR! error rolling back at Error (native)
npm ERR! error rolling back { [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client']
npm ERR! error rolling back errno: -39,
npm ERR! error rolling back code: 'ENOTEMPTY',
npm ERR! error rolling back syscall: 'rmdir',
npm ERR! error rolling back path: '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client' }
npm ERR! Please include the following file with any support request:
npm ERR! /opt/iobroker/npm-debug.log
pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.admin
npm WARN unmet dependency /opt/iobroker/node_modules/iobroker.ical/node_modules/request/node_modules/http-signature/node_modules/jsprim requires assert-plus@'1.0.0' but will load
npm WARN unmet dependency /opt/iobroker/node_modules/iobroker.ical/node_modules/request/node_modules/http-signature/node_modules/assert-plus,
npm WARN unmet dependency which is version 0.2.0
iobroker.admin@2.0.9 node_modules/iobroker.admin
├── connect-flash@0.1.1
├── xtend@4.0.1
├── passport.socketio@3.7.0
├── cookie-parser@1.4.3 (cookie-signature@1.0.6, cookie@0.3.1)
├── passport-local@1.0.0 (passport-strategy@1.0.0)
├── passport@0.3.2 (passport-strategy@1.0.0, pause@0.0.1)
├── express-session@1.15.6 (utils-merge@1.0.1, on-headers@1.0.1, cookie-signature@1.0.6, cookie@0.3.1, parseurl@1.3.2, depd@1.1.2, crc@3.4.4, uid-safe@2.1.5, debug@2.6.9)
├── body-parser@1.18.2 (content-type@1.0.4, bytes@3.0.0, depd@1.1.2, qs@6.5.1, on-finished@2.3.0, raw-body@2.3.2, http-errors@1.6.2, debug@2.6.9, iconv-lite@0.4.19, type-is@1.6.15)
├── express@4.16.2 (cookie-signature@1.0.6, utils-merge@1.0.1, content-type@1.0.4, cookie@0.3.1, parseurl@1.3.2, escape-html@1.0.3, array-flatten@1.1.1, setprototypeof@1.1.0, encodeurl@1.0.2, merge-descriptors@1.0.1, methods@1.1.2, fresh@0.5.2, content-disposition@0.5.2, etag@1.8.1, range-parser@1.2.0, path-to-regexp@0.1.7, vary@1.1.2, serve-static@1.13.1, statuses@1.3.1, safe-buffer@5.1.1, depd@1.1.2, on-finished@2.3.0, qs@6.5.1, finalhandler@1.1.0, debug@2.6.9, proxy-addr@2.0.2, type-is@1.6.15, accepts@1.3.4, send@0.16.1)
├── socket.io@1.7.4 (object-assign@4.1.0, socket.io-adapter@0.5.0, has-binary@0.1.7, debug@2.3.3, socket.io-parser@2.3.1, engine.io@1.8.5, socket.io-client@1.7.4)
├── express-fileupload@0.1.4 (streamifier@0.1.1, busboy@0.2.14, fs-extra@0.22.1)
└── request@2.83.0 (aws-sign2@0.7.0, oauth-sign@0.8.2, tunnel-agent@0.6.0, forever-agent@0.6.1, is-typedarray@1.0.0, caseless@0.12.0, safe-buffer@5.1.1, stringstream@0.0.5, aws4@1.6.0, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.1, performance-now@2.1.0, qs@6.5.1, uuid@3.2.1, combined-stream@1.0.5, mime-types@2.1.17, tough-cookie@2.3.3, form-data@2.3.1, hawk@6.0.2, http-signature@1.2.0, har-validator@5.0.3)
pi@raspberrypi:/opt/iobroker $ sudo chmod 777 * -R
pi@raspberrypi:/opt/iobroker $ iobroker l i
module.js:327
throw err;
^
Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
at node.js:1043:3
pi@raspberrypi:/opt/iobroker $ iobroker start
module.js:327
throw err;
^
Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Function.Module.runMain (module.js:441:10)
at startup (node.js:140:18)
at node.js:1043:3
wenn ich jetzt folgendes eingebe:
cd /opt/iobroker
sudo chmod 777 * -R
sudo npm install iobroker.js-controller –production
erscheint:
npm ERR! Linux 4.4.38-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "iobroker.js-controller" "–production"
npm ERR! node v4.8.0
npm ERR! npm v2.15.11
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client
npm ERR! code ENOTEMPTY
npm ERR! errno -39
npm ERR! syscall rmdir
npm ERR! ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! error rolling back Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client'
npm ERR! error rolling back at Error (native)
npm ERR! error rolling back { [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client']
npm ERR! error rolling back errno: -39,
npm ERR! error rolling back code: 'ENOTEMPTY',
npm ERR! error rolling back syscall: 'rmdir',
npm ERR! error rolling back path: '/opt/iobroker/node_modules/iobroker.js-controller/node_modules/jszip/node_modules/core-js/client' }
npm ERR! Please include the following file with any support request:
npm ERR! /opt/iobroker/npm-debug.log
hat jemand für mich eine Idee ?
(hoffentlich muss ich nicht iobroker komplett neu aufsetzen. weiss nämlich nicht mehr wie es geht…)
Danke und Gruß
Marcus
-
Hi,
Was bedeutet denn das:
> blieb die Software hängen?Und wieso killst du alle iobroker Prozesse bloß weil sich ein Adapter deiner Meinung nach nicht updated?
Welche HW benutzt du? Je nach HW kann so ein Update schonmal ein wenig dauern. Wie hast du denn fest gestellt das die „Software hängen geblieben“ ist?
Wenn du noch nicht viel konfiguriert hattest und auf deinem System nur iobroker läuft/lief… würde ich es schnell neu installieren.
Gruß
PS: Bitte beim nächsten mal logfile in Spoiler und Code tags setzen
Support us
523
Online32.6k
Benutzer82.2k
Themen1.3m
Beiträge