NEWS
Beta Test js-controller Kiera (v6.0)
-
@dergraf123 mit dieser Fehlermeldung kann man die Probleme nicht lösen
-
@dergraf123 gibt’s da auch ein log zu?
-
Hier die Logs zu den Adaptern:
SQL:
host.iobroker 2024-06-13 18:57:32.129 info Restart adapter system.adapter.sql.0 because enabled host.iobroker 2024-06-13 18:57:32.128 error instance system.adapter.sql.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[1]: Node.js v20.14.0 host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at node:internal/main/run_main_module:28:49 host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.sql/main.js:3481:5) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.sql/main.js:111:15) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: TypeError: utils.Adapter is not a constructor host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: ^ host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: adapter = new utils.Adapter(options); host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.sql/main.js:111 host.iobroker 2024-06-13 18:57:31.674 info instance system.adapter.sql.0 started with pid 2283
YAMAHA:
host.iobroker 2024-06-13 18:57:32.129 info Restart adapter system.adapter.sql.0 because enabled host.iobroker 2024-06-13 18:57:32.128 error instance system.adapter.sql.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[1]: Node.js v20.14.0 host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at node:internal/main/run_main_module:28:49 host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.sql/main.js:3481:5) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.sql/main.js:111:15) host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: TypeError: utils.Adapter is not a constructor host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: ^ host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: adapter = new utils.Adapter(options); host.iobroker 2024-06-13 18:57:32.128 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.sql/main.js:111 host.iobroker 2024-06-13 18:57:31.674 info instance system.adapter.sql.0 started with pid 2283
DAIKIN:
host.iobroker 2024-06-13 19:00:37.371 info Restart adapter system.adapter.daikin.0 because enabled host.iobroker 2024-06-13 19:00:37.371 error instance system.adapter.daikin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[1]: Node.js v20.14.0 host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at node:internal/main/run_main_module:28:49 host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12) host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32) host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14) host.iobroker 2024-06-13 19:00:37.371 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.daikin/daikin.js:661:5) host.iobroker 2024-06-13 19:00:37.370 error Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.daikin/daikin.js:229:15) host.iobroker 2024-06-13 19:00:37.370 error Caught by controller[0]: TypeError: utils.Adapter is not a constructor host.iobroker 2024-06-13 19:00:37.370 error Caught by controller[0]: ^ host.iobroker 2024-06-13 19:00:37.370 error Caught by controller[0]: adapter = new utils.Adapter(options); host.iobroker 2024-06-13 19:00:37.370 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.daikin/daikin.js:229 host.iobroker 2024-06-13 19:00:36.950 info instance system.adapter.daikin.0 started with pid 2779
-
Hallo.
Gerade Master und 2 Slaves auf 6.0.4 aktualisiert.
Alle installierten Instances laufen.Gruß
-
@dergraf123
Sorry im moment nur handy.
Aber falls noch nicht gepostet bitte die Versionen der Adapter posten.yahama braucht nen Update -> @Garfonso
da du als Maintainer dort drinnen stehst hab ich den beim Cleanup der community Adapters nicht aktualissiert. Bitte so bald als möglich adapter-core und teste etc. aktualisierern. Dankedaiki hat core 3.0.4 drinne, sollte eigentlich passen -> @apollon77
wenn du Zeit hast ev trotzdem auf 3.1.4/6 hochziehensql hat adapter-core": "^3.0.3" drinnen, sollte eigentlich passen. -> @foxriver76
ev. hochziehen? Aber an sich sollte 3.x.x ja passen!?!? -
@mcm1957 Daikin hat leider im Release 2.6.0, SQL auch 2.6.0
-
@foxriver76 said in Beta Test js-controller Kiera (v6.0):
@mcm1957 Daikin hat leider im Release 2.6.0, SQL auch 2.6.0
Sorry,
Auf das hab ich nicht geschaut. Red dich bitte mit @Apollon77 wg. Daikin zusammen.
Bin nur temporär im Netz da openliga ne prioUpdate (wg. EM) brauchte. -
SQL 3.0.1 sollte laufen
-
@foxriver76 Update von 6.0.2 auf 6.0.4 war auf beiden Testsystemen erfolgreich.
Es kam blieb nach dem Update aber diese Meldung stehen
-
@thomas-braun sorry, konnte gestern nicht mehr weiter machen...
gerade versucht javascript neu zu starten mit folgendem log:javascript.0 2024-06-14 05:43:13.308 info terminating javascript.0 2024-06-14 05:43:12.810 warn Terminated (UNCAUGHT_EXCEPTION): Without reason javascript.0 2024-06-14 05:43:12.809 info terminating javascript.0 2024-06-14 05:43:12.707 error Exception-Code: ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath './package.json' is not defined by "exports" in /opt/iobroker/node_modules/@iobroker-javascript.0/regex/package.json javascript.0 2024-06-14 05:43:12.706 error Error: Package subpath './package.json' is not defined by "exports" in /opt/iobroker/node_modules/@iobroker-javascript.0/regex/package.json at exportsNotFound (node:internal/modules/esm/resolve:304:10) at packageExportsResolve (node:internal/modules/esm/resolve:651:9) at resolveExports (node:internal/modules/cjs/loader:592:36) at Function.Module._findPath (node:internal/modules/cjs/loader:669:31) at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1131:27) at Function.resolve (node:internal/modules/helpers:190:19) at listInstalledNodeModules (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:126:34) at installLibraries (/opt/iobroker/node_modules/iobroker.javascript/main.js:1836:36) javascript.0 2024-06-14 05:43:12.706 error unhandled promise rejection: Package subpath './package.json' is not defined by "exports" in /opt/iobroker/node_modules/@iobroker-javascript.0/regex/package.json javascript.0 2024-06-14 05:43:12.706 error 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(). javascript.0 2024-06-14 05:43:12.674 info starting. Version 8.5.2 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.14.0, js-controller: 6.0.3 javascript.0 2024-06-14 05:42:39.592 info terminating javascript.0 2024-06-14 05:42:39.092 warn Terminated (UNCAUGHT_EXCEPTION): Without reason javascript.0 2024-06-14 05:42:39.091 info terminating javascript.0 2024-06-14 05:42:38.973 error Exception-Code: ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath './package.json' is not defined by "exports" in /opt/iobroker/node_modules/@iobroker-javascript.0/regex/package.json javascript.0 2024-06-14 05:42:38.972 error Error: Package subpath './package.json' is not defined by "exports" in /opt/iobroker/node_modules/@iobroker-javascript.0/regex/package.json at exportsNotFound (node:internal/modules/esm/resolve:304:10) at packageExportsResolve (node:internal/modules/esm/resolve:651:9) at resolveExports (node:internal/modules/cjs/loader:592:36) at Function.Module._findPath (node:internal/modules/cjs/loader:669:31) at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1131:27) at Function.resolve (node:internal/modules/helpers:190:19) at listInstalledNodeModules (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/utils.ts:126:34) at installLibraries (/opt/iobroker/node_modules/iobroker.javascript/main.js:1836:36) javascript.0 2024-06-14 05:42:38.972 error unhandled promise rejection: Package subpath './package.json' is not defined by "exports" in /opt/iobroker/node_modules/@iobroker-javascript.0/regex/package.json javascript.0 2024-06-14 05:42:38.971 error 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(). javascript.0 2024-06-14 05:42:38.912 info starting. Version 8.5.2 in /opt/iobroker/node_modules/iobroker.javascript, node: v20.14.0, js-controller: 6.0.3
-
@da_woody bitte einfach auf 6.0.4 upgraden
-
@feuersturm Hier wäre das Browser Log interessant falls es wieder passiert.
-
@foxriver76 wurde mir gerade angeboten, gemacht, alle adapter grün!
thnx für die prompte erledigung! -
@foxriver76 sagte in Beta Test js-controller Kiera (v6.0):
@malleralle Ebenfalls nicht im Repo, hilft nur auf GitHub forken, adapter-core upgraden und von dort neu installieren.
Danke @foxriver76
Habe ich erfolgreich hinbekommen.
epson-workforce läuft bei mir wieder. -
@malleralle said in Beta Test js-controller Kiera (v6.0):
@foxriver76 sagte in Beta Test js-controller Kiera (v6.0):
@malleralle Ebenfalls nicht im Repo, hilft nur auf GitHub forken, adapter-core upgraden und von dort neu installieren.
Danke @foxriver76
Habe ich erfolgreich hinbekommen.
epson-workforce läuft bei mir wieder.Wenn du oder der originale dev den Adapter ins Reponaufnehmenbwillst gerne melden. Kann nur sein dass ev noch andere Anpassungen notwendig sind um mindeststandard zu erreichen. Gibt ja vielleicht noch andere pot. User.
Mcm1957
-
Mit JS-Controller 6 gibt es ja nun auch Benachrichtigung über verfügbare System Updates:
Zum einen ist der Titel des Hinweises falsch. Zum anderen habe ich diese Pakete bereits installiert, werde die Meldung aber nicht los. Nach Klick auf "Bestätigen" ist sie weg. Aber ein Reload des Browsertabs oder ein neuer Admin Tab, zeigt den Badge beim Host immer wieder an.
-
@diginix der Titel "Adapterwarnungen" meinst du? Dann Admin Issue anlegen.
Die Frage ist hast du die Paketupdates auch mit
apt
ausgeführt? Sonst wird es bei jedem Check neu generiert -
Das dürfte dieser Sonderstrick von Ubuntu sein, der sich da 'phased updates' nennt.
https://ubuntu.com/server/docs/about-apt-upgrade-and-phased-updates
-
@foxriver76 Ja, die Updates wurde installiert mit:
sudo apt update sudo apt -y dist-upgrade
Aber ich sehe gerade, dass nicht alles inst wird:
The following upgrades have been deferred due to phasing: cloud-init snapd 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
$ sudo apt list --upgradeable -a Listing... Done cloud-init/noble-updates 24.1.3-0ubuntu3.3 all [upgradable from: 24.1.3-0ubuntu3.2] cloud-init/now 24.1.3-0ubuntu3.2 all [installed,upgradable to: 24.1.3-0ubuntu3.3] cloud-init/noble 24.1.3-0ubuntu3 all snapd/noble-updates 2.63+24.04 amd64 [upgradable from: 2.62+24.04build1] snapd/noble,now 2.62+24.04build1 amd64 [installed,upgradable to: 2.63+24.04]
Von daher ist der Hinweis vom Host tatsächlich richtig.
-
@diginix sagte in Beta Test js-controller Kiera (v6.0):
The following upgrades have been deferred due to phasing:
Siehe meine Vermutung von zuvor.
Das sind 'phased updates'.Schnubbibuntu halt...