Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren
Error/Bug
33
Beiträge
4
Kommentatoren
1.4k
Aufrufe
3
Watching
-
@wendy2702
3.2.16which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejsliefert?
-
Hier der Fehlercode dazu nach der Aktualisierung schmiert der komplette Iobroker ab kann ihn nur durch einspielen eines Backups wieder zu laufen bringen
$ ./iobroker upgrade vis Update vis from @1.3.4 to @1.3.8 NPM version: 6.14.12npm install iobroker.vis@1.3.8 --loglevel error --prefix "/opt/iobroker" (System call) ERROR: internal/modules/cjs/loader.js:818 throw err; ^Error: Cannot find module 'mime'Require stack:- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js- /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js- /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15) at Function.Module._load (internal/modules/cjs/loader.js:667:27) at Module.require (internal/modules/cjs/loader.js:887:19) at require (internal/modules/cjs/helpers.js:74:18) at Upload.uploadAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js:525:24) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:211:28 at installNpm (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2557:9) at finishUpgrade (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:205:13) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:419:21 at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupInstall.js:223:55 { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ]} ERROR: process exited with code 1```@ibot sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
^Error: Cannot find module 'mime'Require stack:-
Habe gerade für dich mal das Forum nach diesem Fehler durchsucht.
Konnte nur "Probleme" in Zusammenhang mit einer Windows-Installation finden. -
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejsliefert?
@thomas-braun sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs v12.22.1 /usr/bin/node v12.22.1 /usr/bin/npm 6.14.12 nodejs: Installiert: 12.22.1-1nodesource1 Installationskandidat: 12.22.1-1nodesource1 Versionstabelle: *** 12.22.1-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages -
@thomas-braun sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs v12.22.1 /usr/bin/node v12.22.1 /usr/bin/npm 6.14.12 nodejs: Installiert: 12.22.1-1nodesource1 Installationskandidat: 12.22.1-1nodesource1 Versionstabelle: *** 12.22.1-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packagesiobroker update iobroker upgradeWenn das nicht funktioniert:
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
iobroker update iobroker upgradeWenn das nicht funktioniert:
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller@thomas-braun
na dem Upgrade Befehl kommt:Error: Cannot find module 'mime' Require stack: - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15) at Function.Module._load (internal/modules/cjs/loader.js:667:27) at Module.require (internal/modules/cjs/loader.js:887:19) at require (internal/modules/cjs/helpers.js:74:18) at Upload.uploadAdapter (/opt/iobroker/node_modules/iobroker.js-controller/l ib/setup/setupUpload.js:525:24) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade. js:211:28 at installNpm (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.j s:2557:9) at finishUpgrade (/opt/iobroker/node_modules/iobroker.js-controller/lib/setu p/setupUpgrade.js:205:13) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade. js:419:21 at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupInstall. js:223:55 { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpload.js' , '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js ', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ] }MOD EDIT: CODE TAGS KORRIGIERT
-
iobroker update iobroker upgradeWenn das nicht funktioniert:
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller@thomas-braun
nach:cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controllernpm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.12 > unix-dgram@2.0.3 install /opt/iobroker/node_modules/unix-dgram > node-gyp rebuild make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird betreten CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o In file included from ../../nan/nan.h:56, from ../src/unix_dgram.cc:5: /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:736:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(unix_dgram, Initialize) ^~~~~~~~~~~ SOLINK_MODULE(target) Release/obj.target/unix_dgram.node COPY Release/unix_dgram.node make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird verlassen > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional > node rebuild.js ursaNative bindings compilation fail. This is not an issue. Modules that depend on it will use fallbacks. > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage > node-gyp rebuild make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird betreten CXX(target) Release/obj.target/diskusage/src/main.o In file included from ../../nan/nan.h:56, from ../src/main.cpp:3: /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:736:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(diskusage, Init) ^~~~~~~~~~~ CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o SOLINK_MODULE(target) Release/obj.target/diskusage.node COPY Release/diskusage.node make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird verlassen > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object _design/system updated > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme > node scripts/postinstall npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@3.2.16 added 254 packages from 265 contributors, removed 6 packages, updated 1 package and moved 16 packages in 96.989s 13 packages are looking for funding run `npm fund` for details ╭────────────────────────────────────────────────────────────────╮ │ │ │ New major version of npm available! 6.14.12 → 7.10.0 │ │ Changelog: https://github.com/npm/cli/releases/tag/v7.10.0 │ │ Run npm install -g npm to update! │ │ │ ╰────────────────────────────────────────────────────────────────╯ -
@thomas-braun
nach:cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controllernpm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.12 > unix-dgram@2.0.3 install /opt/iobroker/node_modules/unix-dgram > node-gyp rebuild make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird betreten CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o In file included from ../../nan/nan.h:56, from ../src/unix_dgram.cc:5: /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:736:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(unix_dgram, Initialize) ^~~~~~~~~~~ SOLINK_MODULE(target) Release/obj.target/unix_dgram.node COPY Release/unix_dgram.node make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird verlassen > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional > node rebuild.js ursaNative bindings compilation fail. This is not an issue. Modules that depend on it will use fallbacks. > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage > node-gyp rebuild make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird betreten CXX(target) Release/obj.target/diskusage/src/main.o In file included from ../../nan/nan.h:56, from ../src/main.cpp:3: /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:736:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/iobroker/.cache/node-gyp/12.22.1/include/node/node.h:770:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(diskusage, Init) ^~~~~~~~~~~ CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o SOLINK_MODULE(target) Release/obj.target/diskusage.node COPY Release/diskusage.node make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird verlassen > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first object _design/system updated > @root/acme@3.1.0 postinstall /opt/iobroker/node_modules/@root/acme > node scripts/postinstall npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@3.2.16 added 254 packages from 265 contributors, removed 6 packages, updated 1 package and moved 16 packages in 96.989s 13 packages are looking for funding run `npm fund` for details ╭────────────────────────────────────────────────────────────────╮ │ │ │ New major version of npm available! 6.14.12 → 7.10.0 │ │ Changelog: https://github.com/npm/cli/releases/tag/v7.10.0 │ │ Run npm install -g npm to update! │ │ │ ╰────────────────────────────────────────────────────────────────╯Und?
-
Und?
-
@thomas-braun
iobroker ist über die webobefläche nicht mehr ereichbar soll ich das npm Update durchführen?@ibot
Auf gar keinen Fall!
Das macht es nur schlimmer.
npm wird nur über den Paketmanager aktualisiert, im Zuge eine Updates von nodejs.iobroker status iobroker list adapters iobroker list instances -
@ibot
Auf gar keinen Fall!
Das macht es nur schlimmer.
npm wird nur über den Paketmanager aktualisiert, im Zuge eine Updates von nodejs.iobroker status iobroker list adapters iobroker list instances@thomas-braun sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
iobroker status
iobroker list adapters
iobroker list instancespi@raspberrypi:/opt/iobroker $ iobroker status iobroker is running on this host. Objects type: file States type: file pi@raspberrypi:/opt/iobroker $ iobroker list adapters system.adapter.admin : admin - v4.2.1 system.adapter.discovery : discovery - v2.6.1 system.adapter.flot : flot - v1.10.6 system.adapter.history : history - v1.9.12 system.adapter.info : info - v1.7.14 system.adapter.javascript : javascript - v5.0.14 system.adapter.mqtt : mqtt - v2.3.5 system.adapter.mqtt-client : mqtt-client - v1.3.1 system.adapter.node-red : node-red - v2.2.0 system.adapter.rpi2 : rpi2 - v1.2.0 system.adapter.sonoff : sonoff - v2.4.0 system.adapter.vis : vis - v1.3.4 system.adapter.vis-hqwidgets : vis-hqwidgets - v1.1.7 system.adapter.web : web - v3.3.0 system.adapter.yahka : yahka - v0.12.0 pi@raspberrypi:/opt/iobroker $ iobroker list instances + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.flot.0 : flot : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.info.0 : info : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : raspberrypi - enabled + instance is alive -
@thomas-braun sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
iobroker status
iobroker list adapters
iobroker list instancespi@raspberrypi:/opt/iobroker $ iobroker status iobroker is running on this host. Objects type: file States type: file pi@raspberrypi:/opt/iobroker $ iobroker list adapters system.adapter.admin : admin - v4.2.1 system.adapter.discovery : discovery - v2.6.1 system.adapter.flot : flot - v1.10.6 system.adapter.history : history - v1.9.12 system.adapter.info : info - v1.7.14 system.adapter.javascript : javascript - v5.0.14 system.adapter.mqtt : mqtt - v2.3.5 system.adapter.mqtt-client : mqtt-client - v1.3.1 system.adapter.node-red : node-red - v2.2.0 system.adapter.rpi2 : rpi2 - v1.2.0 system.adapter.sonoff : sonoff - v2.4.0 system.adapter.vis : vis - v1.3.4 system.adapter.vis-hqwidgets : vis-hqwidgets - v1.1.7 system.adapter.web : web - v3.3.0 system.adapter.yahka : yahka - v0.12.0 pi@raspberrypi:/opt/iobroker $ iobroker list instances + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.flot.0 : flot : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.info.0 : info : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.mqtt.0 : mqtt : raspberrypi - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.rpi2.0 : rpi2 : raspberrypi - enabled + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : raspberrypi - enabled + instance is alive@ibot
Sollte eigentlich laufen. Welche Meldungen bekommst du? -
@ibot
Sollte eigentlich laufen. Welche Meldungen bekommst du?@thomas-braun sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
Sollte eigentlich laufen.
sehe ich auch so!
@Ibot
hast du mal den Browsercache gelöscht? -
@ibot
Sollte eigentlich laufen. Welche Meldungen bekommst du? -
@thomas-braun
Im Browser stehtCannot GET /@ibot sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
Starte den Pi mal sauber durch:
iobroker stop sudo rebootUnd BrowserCache löschen, wie @Homoran schon sagte.
-
@thomas-braun sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
Sollte eigentlich laufen.
sehe ich auch so!
@Ibot
hast du mal den Browsercache gelöscht? -
@homoran
Hallo, ja habe ich sobald ich das Backup zurückspiele ist über den Browser auch alles wieder ereichbar -
@homoran
Hallo, ja habe ich sobald ich das Backup zurückspiele ist über den Browser auch alles wieder ereichbar@ibot sagte in Vis lässt sich nicht von 1.3.4 zu 1.3.8 aktualisieren:
sobald ich das Backup zurückspiele
von Backup hat niemand was gesagt!
-
@thomas-braun
ich habe mit dem Iobroker Tool vorab ein Backup erstellt. Nach dem Neustart ist Iobroker wieder ereichbar und Vis ist auch aktuell Top Npm Cache trotzdem noch löschen? -
@thomas-braun
ich habe mit dem Iobroker Tool vorab ein Backup erstellt. Nach dem Neustart ist Iobroker wieder ereichbar und Vis ist auch aktuell Top Npm Cache trotzdem noch löschen?Nö, wenn alles läuft lass die Finger davon.
Was liefert denn jetzt ein
iobroker update iobroker upgrade
Support us
265
Online32.7k
Benutzer82.5k
Themen1.3m
Beiträge