js-controller Lucy (Version 7.0) jetzt im Beta Repository
-
@foxriver76 Wenn ich es richtig gemacht habe wirft er das aus:
Nov 15 12:52:44 iobrokervm sudo[1312491]: pam_unix(sudo:auth): conversation failed Nov 15 12:52:44 iobrokervm sudo[1312491]: pam_unix(sudo:auth): auth could not identify password for [iobroker] -
Dann verwendest du den User 'iobroker' als deinen Standarduser und nicht wie es richtig wäre als Systemuser. Der hat und braucht nämlich gar kein Passwort.
Leg dir einen User an und verwende den.
-
@thomas-braun ich denke das ist auch das Problem warum das UI upgrade failed dann
-
Möglich. War halt noch nie eine gute Idee 'iobroker' als Standarduser zu verwenden.
Unter Umständen müsste der 'iobroker' auch dann auf 'NOLOGIN' umgestellt werden. -
@thomas-braun Ja da der Update Prozess versucht wird als
systemdDienst zu starten könnte ich mir sehr gut vorstellen dass da was nicht ganz passt an dem User der ioBroker ausfuehrt. Denn auf einem stinknormalen Debian sollte der Prozess mittlerweile gut etabliert sein den wir verwenden. -
@thomas-braun Hmmm.. Ich logge mich mit dem User Oliver ein. Als den habe ich IOB nach der Anleitung installiert.
Als iobroker logge ich mich nie ein.
sieht bei mir so aus:
oliver@iobrokervm:~$ ps -ef|grep iobroker iobroker 1315299 1 33 13:00 ? 00:09:53 iobroker.js-controller iobroker 1315321 1315299 1 13:00 ? 00:00:28 io.admin.1 iobroker 1315364 1315299 0 13:00 ? 00:00:01 io.email.0 iobroker 1315385 1315299 13 13:00 ? 00:03:49 io.javascript.0 iobroker 1315400 1315299 0 13:00 ? 00:00:02 io.scenes.0 iobroker 1315415 1315299 0 13:00 ? 00:00:14 io.telegram.0Hab jetzt nicht wirklich ne Idee, was ich machen muss...
-
@foxriver76 sagte in js-controller Lucy (Version 7.0) jetzt im Beta Repository:
@thomas-braun Ja da der Update Prozess versucht wird als
systemdDienst zu starten könnte ich mir sehr gut vorstellen dass da was nicht ganz passt an dem User der ioBroker ausfuehrt.Was könnte denn da nicht passen? Ich rufe als User Oliver iob start auf, iobroker läuft unter User iobroker
-
Dazu müsste man aber Näheres zum jetzigen Setup wissen.
Am besten in einem separaten Thread und dann dort die Langfassung von
iob diagrein. Da kann man schonmal einiges herauslesen
-
@thomas-braun
Gerne: Hier entlang -
@foxriver76 Update von 7.0.3 auf js-controller 7.0.4 via admin UI lief ohne Probleme durch
-
@feuersturm Bei mir leider das gleiche Problem wie immer
-
update von 7.0.3 auf 7.0.4 via Gui unter Proxmox LXC Bookworm und Node 20 ohne Fehler.
System sehr stabil mit fast 70 Adaptern und 600 Devices, 50000 Objects.
Speicherverbrauch sehr gering meist ca 7-8GB. Letztes Jahr kam ich unter 10GB Ram nicht weg - ist aber auch ein Vergleich mit Apple und Birne. -
@foxriver76 Beim update von 7.0.4 auf 7.0.5 via admin UI kommt folgendes
Im log steht folgender Fehler
2024-12-08 19:13:16.514 - info: host.ioB-Prod-Testsystem All instances are stopped. 2024-12-08 19:13:16.713 - info: host.ioB-Prod-Testsystem terminated 2024-12-08 19:13:23.097 - info: host.ioB-Prod-Testsystem [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller 2024-12-08 19:13:23.112 - info: host.ioB-Prod-Testsystem [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081 2024-12-08 19:15:07.825 - error: host.ioB-Prod-Testsystem [CONTROLLER_AUTO_UPGRADE] Could not install js-controller@7.0.5 2024-12-08 19:15:08.446 - info: host.ioB-Prod-Testsystem [CONTROLLER_AUTO_UPGRADE] Final information delivered 2024-12-08 19:15:08.564 - info: host.ioB-Prod-Testsystem [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller 2024-12-08 19:15:11.826 - info: host.ioB-Prod-Testsystem iobroker.js-controller version 7.0.4 js-controller starting 2024-12-08 19:15:11.845 - info: host.ioB-Prod-Testsystem Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker 2024-12-08 19:15:11.855 - info: host.ioB-Prod-Testsystem hostname: ioB-Prod-Testsystem, node: v22.11.0 2024-12-08 19:15:11.862 - info: host.ioB-Prod-Testsystem ip addresses: 192.168.178.105 fe80::be24:11ff:fe8c:71a4 2024-12-08 19:15:15.958 - info: host.ioB-Prod-Testsystem connected to Objects and States 2024-12-08 19:15:16.017 - info: host.ioB-Prod-Testsystem added notifications configuration of host 2024-12-08 19:15:17.369 - info: host.ioB-Prod-Testsystem 69 instances found 2024-12-08 19:15:17.482 - info: host.ioB-Prod-Testsystem starting 54 instances -
@foxriver76 Kleine Ergänzug. Hab gerade auf meinem Testsystem ein Update vom iot Adapter gestartet von 3.4.3 auf 3.4.4
Dort kommt ein sehr ähnlicher Fehler$ iobroker upgrade iot@3.4.4 --debug Update iot from @3.4.3 to @3.4.4 Installing iobroker.iot@3.4.4... (System call) npm error code E404 npm error 404 Not Found - GET https://registry.npmjs.org/iobroker.iot - Not foundnpm error 404npm error 404 'iobroker.iot@3.4.4' is not in this registry.npm error 404npm error 404 Note that you can also install from anpm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-12-08T18_23_13_049Z-debug-0.log Updating objects from io-package.json for adapter "iot" with version "3.4.3" -
2024-12-08 18:26:14.651 - [32minfo[39m: host.iobroker iobroker upgrade iot@3.4.4 --debug 2024-12-08 18:26:21.604 - [32minfo[39m: host.iobroker iobroker Update iot from @3.4.3 to @3.4.4 2024-12-08 18:26:21.803 - [32minfo[39m: host.iobroker iobroker host.iobroker Adapter "system.adapter.iot.0" is stopped. 2024-12-08 18:26:21.829 - [32minfo[39m: host.iobroker "system.adapter.iot.0" disabled 2024-12-08 18:26:21.830 - [32minfo[39m: host.iobroker stopInstance system.adapter.iot.0 (force=false, process=true) 2024-12-08 18:26:21.840 - [32minfo[39m: host.iobroker stopInstance system.adapter.iot.0 send kill signal 2024-12-08 18:26:21.900 - [32minfo[39m: iot.0 (1131) Got terminate signal TERMINATE_YOURSELF 2024-12-08 18:26:22.110 - [32minfo[39m: iot.0 (1131) terminating 2024-12-08 18:26:22.167 - [32minfo[39m: iot.0 (1131) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-12-08 18:26:22.318 - [32minfo[39m: iot.0 (1131) Connection changed: disconnect 2024-12-08 18:26:22.356 - [32minfo[39m: iot.0 (1131) Connection lost 2024-12-08 18:26:22.744 - [32minfo[39m: iot.0 (1131) terminating 2024-12-08 18:26:22.845 - [32minfo[39m: host.iobroker stopInstance timeout system.adapter.iot.0 killing pid 1131 2024-12-08 18:26:22.967 - [33mwarn[39m: host.iobroker instance system.adapter.iot.0 terminated due to SIGKILL 2024-12-08 18:26:22.967 - [32minfo[39m: host.iobroker instance system.adapter.iot.0 terminated with code null () 2024-12-08 18:26:23.646 - [32minfo[39m: host.iobroker iobroker NPM version: 10.8.2 2024-12-08 18:26:23.649 - [32minfo[39m: host.iobroker iobroker Installing iobroker.iot@3.4.4... (System call) 2024-12-08 18:26:48.079 - [32minfo[39m: host.iobroker iobroker 2024-12-08 18:26:48.084 - [32minfo[39m: host.iobroker iobroker added 1 package, and changed 4 packages in 24s 2024-12-08 18:26:48.086 - [32minfo[39m: host.iobroker iobroker 277 packages are looking for funding run `npm fund` for details 2024-12-08 18:26:56.547 - [32minfo[39m: host.iobroker iobroker Updating objects from io-package.json for adapter "iot" with version "3.4.4" 2024-12-08 18:26:56.621 - [32minfo[39m: host.iobroker iobroker Update "system.adapter.iot.0" 2024-12-08 18:26:57.952 - [32minfo[39m: host.iobroker iobroker upload [36] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/actions.js actions.js application/javascript 2024-12-08 18:26:58.102 - [32minfo[39m: host.iobroker iobroker upload [30] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/index_m.html index_m.html text/html 2024-12-08 18:26:58.149 - [32minfo[39m: host.iobroker iobroker upload [20] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/it.json rules/i18n/it.json application/json 2024-12-08 18:26:58.156 - [32minfo[39m: host.iobroker iobroker upload [19] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/nl.json rules/i18n/nl.json application/json 2024-12-08 18:26:58.167 - [32minfo[39m: host.iobroker iobroker upload [18] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/pl.json rules/i18n/pl.json application/json 2024-12-08 18:26:58.176 - [32minfo[39m: host.iobroker iobroker upload [17] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/pt.json rules/i18n/pt.json application/json 2024-12-08 18:26:58.179 - [32minfo[39m: host.iobroker iobroker upload [16] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/ru.json rules/i18n/ru.json application/json 2024-12-08 18:26:58.184 - [32minfo[39m: host.iobroker iobroker upload [15] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/uk.json rules/i18n/uk.json application/json 2024-12-08 18:26:58.187 - [32minfo[39m: host.iobroker iobroker upload [14] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/i18n/zh-cn.json rules/i18n/zh-cn.json application/json 2024-12-08 18:26:58.190 - [32minfo[39m: host.iobroker iobroker upload [13] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/main.aeb070a1.js rules/static/js/main.aeb070a1.js application/javascript 2024-12-08 18:26:58.194 - [32minfo[39m: host.iobroker iobroker upload [12] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/main.aeb070a1.js.map rules/static/js/main.aeb070a1.js.map application/json 2024-12-08 18:26:58.198 - [32minfo[39m: host.iobroker iobroker upload [11] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_prop-types_index_js.998adfa4.chunk.js rules/static/js/node_modules_prop-types_index_js.998adfa4.chunk.js application/javascript 2024-12-08 18:26:58.203 - [32minfo[39m: host.iobroker iobroker upload [10] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_prop-types_index_js.998adfa4.chunk.js.map rules/static/js/node_modules_prop-types_index_js.998adfa4.chunk.js.map application/json 2024-12-08 18:26:58.208 - [32minfo[39m: host.iobroker iobroker upload [9] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_react-dom_index_js-_ef070.106c4109.chunk.js rules/static/js/node_modules_react-dom_index_js-_ef070.106c4109.chunk.js application/javascript 2024-12-08 18:26:58.213 - [32minfo[39m: host.iobroker iobroker upload [8] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_react-dom_index_js-_ef070.106c4109.chunk.js.map rules/static/js/node_modules_react-dom_index_js-_ef070.106c4109.chunk.js.map application/json 2024-12-08 18:26:58.216 - [32minfo[39m: host.iobroker iobroker upload [7] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_react-dom_index_js-_ef071.a71f5d5d.chunk.js rules/static/js/node_modules_react-dom_index_js-_ef071.a71f5d5d.chunk.js application/javascript 2024-12-08 18:26:58.219 - [32minfo[39m: host.iobroker iobroker upload [6] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_react-dom_index_js-_ef071.a71f5d5d.chunk.js.map rules/static/js/node_modules_react-dom_index_js-_ef071.a71f5d5d.chunk.js.map application/json 2024-12-08 18:26:58.224 - [32minfo[39m: host.iobroker iobroker upload [5] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_react_index_js.d0cc0ba3.chunk.js rules/static/js/node_modules_react_index_js.d0cc0ba3.chunk.js application/javascript 2024-12-08 18:26:58.229 - [32minfo[39m: host.iobroker iobroker upload [4] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/node_modules_react_index_js.d0cc0ba3.chunk.js.map rules/static/js/node_modules_react_index_js.d0cc0ba3.chunk.js.map application/json 2024-12-08 18:26:58.232 - [32minfo[39m: host.iobroker iobroker upload [3] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/src_ActionVisu_jsx.e5871f1f.chunk.js rules/static/js/src_ActionVisu_jsx.e5871f1f.chunk.js application/javascript 2024-12-08 18:26:58.238 - [32minfo[39m: host.iobroker iobroker upload [2] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/src_ActionVisu_jsx.e5871f1f.chunk.js.map rules/static/js/src_ActionVisu_jsx.e5871f1f.chunk.js.map application/json 2024-12-08 18:26:58.243 - [32minfo[39m: host.iobroker iobroker upload [1] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_build_index_js.892c0b30.chunk.js rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_build_index_js.892c0b30.chunk.js application/javascript 2024-12-08 18:26:58.263 - [32minfo[39m: host.iobroker iobroker upload [0] iot.admin /opt/iobroker/node_modules/iobroker.iot/admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_build_index_js.892c0b30.chunk.js.map rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_build_index_js.892c0b30.chunk.js.map application/json 2024-12-08 18:26:58.313 - [32minfo[39m: host.iobroker iobroker host.iobroker Adapter "system.adapter.iot.0" is started 2024-12-08 18:26:58.342 - [32minfo[39m: host.iobroker "system.adapter.iot.0" enabled 2024-12-08 18:26:58.989 - [32minfo[39m: host.iobroker instance system.adapter.iot.0 in version "3.4.4" started with pid 27140 2024-12-08 18:26:59.394 - [32minfo[39m: host.iobroker iobroker exit 0 2024-12-08 18:27:02.830 - [32minfo[39m: iot.0 (27140) starting. Version 3.4.4 in /opt/iobroker/node_modules/iobroker.iot, node: v20.18.1, js-controller: 7.0.4Ich will damit nur aufzeigen, dass das kein grundsätzliches Problem ist.
-
Ich hatte auch das Problem das der 7.0.5 nach der Installation gar nicht der 7.0.5 war und danach das erneute Update nicht klappte.
So, ich habe es gerade über die Shell / Bash gemacht,
zuerst sicherheitshalber einiob fixund dann
iob upgrade selfist nun auf der 7.0.5,
Upgrade meiner 3 Adapter in der Warteschliefe klappte nun auch, inklusive des Admin 7.4.4 -
Dass Update von 7.0.4 auf 7.0.5 lief hier auf dem Testsystem ohne Probleme durch. Update über die UI gemacht.
-
Wäre interessant 7.0.4 auf 7.0.5 von einem Docker System zu sehen ob es wieder tut
-
Selbe Fehlermeldung über Admin von 7.0.4 auf 7.0.5 unter Docker.
-
@ofbeqnpolkkl6mby5e13 selbe? Welche?
