js-controller 3.1 jetzt im STABLE!
-
seit Update auf 3.1.4 bekomm ich sehr oft (mal jede Minute, mal alle halbe Stunde, ...) diese Fehler.
Kommt vom HS100-Adapter.
Vor dem Update waren diese Fehler nicht da.
Liegt das am HS100 oder am JS-Controller?
Heute 12:06 error host.iobroker Caught by controller[0]: TCP 10.0.1.79:9999 Error: TCP Socket Closed. segment:0 hadError:false Heute 12:06 error hs100.0 Error: TCP Socket Closed. segment:0 hadError:false at Socket.socket.once.hadError (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19) at Object.onceWrapper (events.js:286:20) at Socket.emit (events.js:198:13) at TCP._handle.close (net.js:607:12) Heute 12:06 error hs100.0 unhandled promise rejection: TCP Socket Closed. segment:0 hadError:false Heute 12:06 error hs100.0 Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). Heute 12:04 error host.iobroker Caught by controller[1]: TCP 10.0.1.80:9999 Error: TCP Socket Closed. segment:0 hadError:false Heute 12:04 error hs100.0 Error: TCP Socket Closed. segment:0 hadError:false at Socket.socket.once.hadError (/opt/iobroker/node_modules/tplink-smarthome-api/lib/network/tcp-socket.js:113:19) at Object.onceWrapper (events.js:286:20) at Socket.emit (events.js:198:13) at TCP._handle.close (net.js:607:12) Heute 12:04 error hs100.0 unhandled promise rejection: TCP Socket Closed. segment:0 hadError:false Heute 12:04 error hs100.0 Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). -
@Negalein sagte in js-controller 3.1 jetzt im STABLE!:
Liegt das am HS100 oder am JS-Controller?
Bei mir keine Probleme mit den beiden. Schon mal den Adapter, oder falls das nicht hilft, den Rechner neu gestartet?
-
@Mike08 bleibt erhalten.
-
@Dr-Bakterius sagte in js-controller 3.1 jetzt im STABLE!:
Bei mir keine Probleme mit den beiden. Schon mal den Adapter, oder falls das nicht hilft, den Rechner neu gestartet?
Ja, Adapter neu gestartet, Rechner neu gestartet. Hilft nichts.
Bin zumindest nicht allein mit dem Problem. -
Hallo,
seit dem Update bekomme ich im Log Warnungen vom Fhem-Adapter. Hier ein kleiner Auszug.2020-05-31 21:22:41.452 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.KUE_Ventil_Weather.state: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.452 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.462 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung.battery: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.462 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.469 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung_T1.state: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.470 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.477 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung_T1.temperature: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.478 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.485 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung_T1_T2.state: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.485 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.493 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung_T1_T2.temperature: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.493 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.500 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung_T2.state: The state property "ts" has the wrong type "undefined" (should be "number")! 2020-05-31 21:22:41.501 - warn: fhem.0 (26962) This value will not be set in future versions. Please report this to the developer. 2020-05-31 21:22:41.510 - warn: fhem.0 (26962) State value to set is invalid for fhem.0.DG_Temp_Heizung_T2.temperature: The state property "ts" has the wrong type "undefined" (should be "number")!
Node.js: v12.17.0
NPM: 6.14.4
js-controller: 3.1.4
Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
Hier gehts zur Hilfe. -
Hallo alle
Haben mal eben upgedatet
Vorher auch noch die Scriptengine
Ich habe während der Installation von beiden ziemlich viele gyp errors
Leider kann ich gar nichts damit anfangen.root@ioBroker-Rock64:/opt/iobroker# iobroker upgrade self Update js-controller from @2.2.9 to @3.1.4 NPM version: 6.14.4 npm install iobroker.js-controller@3.1.4 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call) Package pixman-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `pixman-1.pc' to the PKG_CONFIG_PATH environment variable No package 'pixman-1' found gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in bindin g.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modu les/node-gyp/lib/configure.js:351:16) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces s.js:275:12) gyp ERR! System Linux 4.17.0-rc6-rk3328 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy p/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/nod e_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_pat h=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_ab i_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72" gyp ERR! cwd /opt/iobroker/node_modules/canvas gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_mo dules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build -- module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name =canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_ver sion=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' ( 1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modu les/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:310:20) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:1021:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/chi ld_process.js:286:5) node-pre-gyp ERR! System Linux 4.17.0-rc6-rk3328 node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node- pre-gyp" "install" "--fallback-to-build" node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas node-pre-gyp ERR! node -v v12.16.3 node-pre-gyp ERR! node-pre-gyp -v v0.11.0 node-pre-gyp ERR! not ok ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.1 info sharp Attempting to build from source via node-gyp but this may fail due to the above error info sharp Please see https://sharp.pixelplumbing.com/install for required depen dencies ../src/common.cc:23:22: fatal error: vips/vips8: No such file or directory #include <vips/vips8> ^ compilation terminated. make: *** [Release/obj.target/sharp/src/common.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_module s/node-gyp/lib/build.js:194:23) gyp ERR! stack at ChildProcess.emit (events.js:310:20) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces s.js:275:12) gyp ERR! System Linux 4.17.0-rc6-rk3328 gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy p/bin/node-gyp.js" "rebuild" gyp ERR! cwd /opt/iobroker/node_modules/sharp gyp ERR! node -v v12.16.3 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok Starting node restart.js root@ioBroker-Rock64:/opt/iobroker#Im log habe ich níchts Aufälliges gefunden ausser (nach "warn" gefiltert):
javascript.0 2020-06-01 00:36:16.534 warn (20487) script.js.common.Statusansagen: clearInterval() => not found iot.0 2020-06-01 00:35:18.824 error (20741) [ALEXA] Cannot process "hm-rpc.0.KEQ0631374.1.PRESS_SHORT": TypeError: friendlyName.split is not a function iot.0 2020-06-01 00:35:10.782 warn (20741) Cannot initialize getImage: Error: Cannot find module 'canvas' Require stack: - /opt/iobroker/node_modules/iobroker.iot/lib/getImage.js - /opt/iobroker/node_modules/iobroker.iot/lib/alexaCusto host.ioBroker-Rock64 2020-06-01 00:35:00.046 warn instance system.adapter.tvspielfilm.0 already running with pid 20628 host.ioBroker-Rock64 2020-06-01 00:34:07.569 error system.adapter.js-controller.0 invalid modeSonst scheint alles zu laufen. Die Version die der Admin anzeigt ist 4.0.10
Gruss Ralf
-
@derrapf sagte in js-controller 3.1 jetzt im STABLE!:
pixman-1
sudo apt install libpixman-1-dev libpango1.0-dev libjpeg62-turbo-dev cd /opt/iobroker npm rebuild canvas --build-from-source -
@Mike08 Jupp, bleibt aus ... darf ich den Grund erfahren das Du es deaktivierst? Nur persönliches Interesse ...
-
@Negalein Adapter. ggf mal nach einem Update schauen?
-
@sth_technik Bitte Issue beim Adapter anlegen und schauen ob es ggf eine neue Version gibt.
-
@apollon77 sagte in js-controller 3.1 jetzt im STABLE!:
Adapter. ggf mal nach einem Update schauen?
Adapter ist aktuell.
Hab dort ein Issue angelegt. Eventuell kann @arteck dazu was sagen. -
Hallo zusammen.
Irgendwie hat es meine IOBroker nach dem Update zerbröselt. Läuft in einem Docker auf einer QNAP TS-451+.
iobroker start module.js:550 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (module.js:548:15) at Function.Module._load (module.js:475:25) at Function.Module.runMain (module.js:694:10) at startup (bootstrap_node.js:204:16) at bootstrap_node.js:625:3Fragt mich aber bitte nicht wieso das so ist.
Kann jemand helfen?
Für eure Hilfe im Voraus vielen Dank.VG
Martin
Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
Hier gehts zur Hilfe. -
which nodejs && nodejs -v && which node && node -v && which npm && npm -v -
@MattinK Auch das Log vom Update wäre interessant
-
@apollon77 @sth_technik
Ich habe eine lssue erstellt. Rückantwort war vom stable des fhem Adapters 1.3 auf 1.5.2 updaten. Fehler war da nach nicht mehr da. -
@MattinK Moin, bei mir genau das gleich Problem... hier der Output:
RasPi:/opt/iobroker $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v
/usr/bin/nodejs
v8.14.0
/usr/bin/node
v8.14.0
/usr/bin/npm
6.4.1 -
@tomte-me
node 8 ist tot.
node 12 instalieren. -
@tomte-me
Moin, ich habe das Problem gelöst bekommen. Hier ist aber Handarbeit dann erst ein mal angesagt. Wie Thomas Braun schrieb lag es wohl an dem veralterten node.Ich bin nach dieser Anleitung vorgegangen
https://forum.iobroker.net/topic/22867/how-to-node-js-für-iobroker-richtig-updatenAber zuvor muss man den node.js auf eine neuere Version updaten. In den genannten Artikel wird noch node 10 installiert. Also wie folgt ändern.
curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash - sudo apt-get install -y nodejsDanach dann alle Befehle nach und nach ausgeführt. Bei Installieren des Adapters steht da ein "SELECT ALL". Das kannst du weg lassen.
Danach installiert sich iobroker neu. Dann noch den iobroker starten und dann werden alle Instanzen nach und nach neu installiert. Das dauert eine Weile.
So habe ich meinen iobroker wieder ans laufen bekommen, ohne irgend einen Verlust der Einstellungen und der VIS.
VG
Martin -
@MattinK Jupp, steht alles ganz oben im ersten Post inklusive Link zu den nodejs Upgrade Anleitungen
-
@Thomas-Braun
Hallo Thomas
Soll ich die drei Befehle ausführen? Was tun die genau?Ich hab's ausgeführt und danach iot upgedatet. Kommen aber immer noch diese Gyp Fehler:
$ ./iobroker upgrade iot Update iot from @1.4.18 to @1.5.3 host.ioBroker-Rock64 Adapter "system.adapter.iot.0" is stopped. NPM version: 6.14.4 npm install iobroker.iot@1.5.3 --loglevel error --prefix "/opt/iobroker" (System call) ../src/Canvas.cc: In static member function 'static Nan::NAN_METHOD_RETURN_TYPE Canvas::ToBuffer(Nan::NAN_METHOD_ARGS_TYPE)':../src/Canvas.cc:415:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (canvas->nBytes() > node::Buffer::kMaxLength) { ~~~~~~~~~~~~~~~~~^~~~~~ ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.1info sharp Attempting to build from source via node-gyp but this may fail due to the above error info sharp Please see https://sharp.pixelplumbing.com/install for required dependencies ../src/common.cc:23:22: fatal error: vips/vips8: No such file or directory #include <vips/vips8> ^ compilation terminated. make: *** [Release/obj.target/sharp/src/common.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)gyp ERR! stack at ChildProcess.emit (events.js:310:20)gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)gyp ERR! System Linux 4.17.0-rc6-rk3328 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/sharpgyp ERR! node -v v12.16.3gyp ERR! node-gyp -v v5.1.0gyp ERR! not ok Update "system.adapter.iot.0" upload [30] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/runtime-main.293df86c.js static/js/runtime-main.293df86c.js application/javascript upload [20] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.998ec878.chunk.js.LICENSE.txt static/js/2.998ec878.chunk.js.LICENSE.txt text/plain upload [19] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.998ec878.chunk.js static/js/2.998ec878.chunk.js application/javascript upload [18] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.09585381.chunk.js.map static/js/2.09585381.chunk.js.map application/json upload [17] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.09585381.chunk.js.LICENSE.txt static/js/2.09585381.chunk.js.LICENSE.txt text/plain upload [16] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/js/2.09585381.chunk.js static/js/2.09585381.chunk.js application/javascript upload [15] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/main.d4bed9c6.chunk.css.map static/css/main.d4bed9c6.chunk.css.map application/json upload [14] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/main.d4bed9c6.chunk.css static/css/main.d4bed9c6.chunk.css text/css upload [13] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/2.b1b16afe.chunk.css.map static/css/2.b1b16afe.chunk.css.map application/json upload [12] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/static/css/2.b1b16afe.chunk.css static/css/2.b1b16afe.chunk.css text/css upload [11] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/service-worker.js service-worker.js application/javascript upload [10] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/precache-manifest.bebcfb9ed8ff6b9f47417e68cd1ee624.js precache-manifest.bebcfb9ed8ff6b9f47417e68cd1ee624.js application/javascript upload [9] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/precache-manifest.64c35f13f942d5febcd49006c799b298.js precache-manifest.64c35f13f942d5febcd49006c799b298.js application/javascript upload [8] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/precache-manifest.537015042a8c3fa504c76d01ebb32c7c.js precache-manifest.537015042a8c3fa504c76d01ebb32c7c.js application/javascript upload [7] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/manifest.json manifest.json application/json upload [6] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/iot.png iot.png image/png upload [5] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/index_m.html index_m.html text/html upload [4] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/favicon.ico favicon.ico image/vnd.microsoft.icon upload [3] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/blockly.js blockly.js application/javascript upload [2] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/asset-manifest.json asset-manifest.json application/json upload [1] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/alexalogo.png alexalogo.png image/png upload [0] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/actions.js actions.js application/javascript Adapter "iot" updated host.ioBroker-Rock64 Adapter "system.adapter.iot.0" is started process exited with code 0Gruss Ralf
