Alpha Test js-controller 4.0

Thomas Braun

Hab hier mal flugs umgestellt. Auf den ersten Blick keine Show Stopper, System läuft problemlos weiter.
Node17/npm8 als Runtime.

apollon77

@thomas-braun sagte in Alpha Test js-controller 4.0:

Node17/npm8 als Runtime.

Jaja der ganz "edgy" Test wieder

Thomas Braun

@apollon77
Ja, lüppt aber...
Einer muss den Job ja machen.

Feuersturm

@apollon77 Bei mehreren Adaptern taucht im Log folgendes auf

nina.0 (5475) Sets unsupported

Was steckt hier dahinter, bzw. wie soll die Fehleransprache bei den Adaptern lauten?

apollon77

@feuersturm Was ist es bei Dir für ein System? Wenn es die "mnormale File/JsonlL" DB ist dann ist das ok und wird mit nächstem Update auf debug log geändert

Feuersturm

@apollon77 Ist ein jsonl System. Master gerade aktualisiert. Gleich ist der Slave dran.

proxmox@ioBrokerTestsystem:/opt/iobroker$ iobroker status
iobroker is running on this host.
Objects type: jsonl
States  type: jsonl

apollon77

@feuersturm Das liegt aktuell daran das dein Multihost nicht voll aktualisiert ist. Sollte danach wieder verschwinden

Feuersturm

@apollon77 Jup, Master und Slave sind jetzt auf js-controller 4.0 und die Meldungen sind nicht mehr da.
System startet ohne Probleme und bisher keine Probleme ersichtlich.

Habe gerade den Slave Host neu gestartet, indem ich eine Logging Änderung für Seq im Host konfiguriert habe was zum Neustart des Hosts geführt hat.
Im Log stand dann folgendes:

2022-01-31 23:26:17.539 - debug: history.1 (9160) Plugin sentry destroyed
2022-01-31 23:26:17.517 - info: host.ioBrokerNew received SIGTERM
2022-01-31 23:26:17.542 - info: discovery.0 (9175) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-01-31 23:26:17.547 - info: history.1 (9160) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-01-31 23:26:17.566 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=true)
2022-01-31 23:26:17.570 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=true)
2022-01-31 23:26:17.583 - info: discovery.0 (9175) Got terminate signal TERMINATE_YOURSELF
2022-01-31 23:26:17.593 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 send kill signal
2022-01-31 23:26:18.332 - info: host.ioBrokerNew instance system.adapter.history.1 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-01-31 23:26:18.594 - info: host.ioBrokerNew instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-01-31 23:26:18.598 - info: host.ioBrokerNew All instances are stopped.
2022-01-31 23:26:18.638 - error: host.ioBrokerNew uncaught exception: Connection is closed.
2022-01-31 23:26:18.640 - error: host.ioBrokerNew Error: Connection is closed.
at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:628:24)
at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
at ObjectsInRedisClient._getObject (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:2662:37)
at Immediate. (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:2708:33)
at processImmediate (internal/timers.js:466:21)
2022-01-31 23:26:18.644 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=false)
2022-01-31 23:26:18.646 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=false)
2022-01-31 23:26:18.649 - info: host.ioBrokerNew iobroker _restart
2022-01-31 23:26:18.915 - info: host.ioBrokerNew terminated
2022-01-31 23:26:18.919 - info: host.ioBrokerNew terminated
2022-01-31 23:26:21.591 - info: host.ioBrokerNew iobroker.js-controller version 4.0.0 js-controller starting
2022-01-31 23:26:21.603 - info: host.ioBrokerNew Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-01-31 23:26:21.605 - info: host.ioBrokerNew hostname: ioBrokerNew, node: v14.18.1
2022-01-31 23:26:21.607 - info: host.ioBrokerNew ip addresses: 192.168.178.78 fe80::d4a0:37ff:fe8e:f0c1
2022-01-31 23:26:22.091 - info: host.ioBrokerNew connected to Objects and States
2022-01-31 23:26:22.123 - info: host.ioBrokerNew added notifications configuration of host
2022-01-31 23:26:23.102 - info: host.ioBrokerNew 59 instances found
2022-01-31 23:26:23.199 - info: host.ioBrokerNew starting 2 instances
2022-01-31 23:26:23.415 - info: host.ioBrokerNew instance system.adapter.history.1 started with pid 9238
2022-01-31 23:26:25.047 - debug: history.1 (9238) Redis Objects: Use Redis connection: 192.168.178.77:9001
2022-01-31 23:26:25.156 - debug: history.1 (9238) Objects client ready ... initialize now
2022-01-31 23:26:25.160 - debug: history.1 (9238) Objects create System PubSub Client
2022-01-31 23:26:25.164 - debug: history.1 (9238) Objects create User PubSub Client
2022-01-31 23:26:25.287 - debug: history.1 (9238) Objects client initialize lua scripts
2022-01-31 23:26:25.297 - debug: history.1 (9238) Objects connected to redis: 192.168.178.77:9001
2022-01-31 23:26:25.361 - debug: history.1 (9238) Redis States: Use Redis connection: 192.168.178.77:9000
2022-01-31 23:26:25.396 - debug: history.1 (9238) States create System PubSub Client
2022-01-31 23:26:25.398 - debug: history.1 (9238) States create User PubSub Client
2022-01-31 23:26:25.463 - debug: history.1 (9238) States connected to redis: 192.168.178.77:9000
2022-01-31 23:26:25.989 - debug: history.1 (9238) Plugin sentry Initialize Plugin (enabled=true)
2022-01-31 23:26:26.362 - info: history.1 (9238) starting. Version 1.10.5 in /opt/iobroker/node_modules/iobroker.history, node: v14.18.1, js-controller: 4.0.0-alpha.67-20220131-6621d47f
2022-01-31 23:26:27.423 - info: host.ioBrokerNew instance system.adapter.discovery.0 started with pid 9253
2022-01-31 23:26:30.270 - info: discovery.0 (9253) starting. Version 2.7.5 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.18.1, js-controller: 4.0.0-alpha.67-20220131-6621d47f

mrjeschke

@apollon77
Nach dem update auf den js-controller 4 bekomme ich wieder invalid
Type errors.


2022-01-31 23:45:51.995 - warn: info.0 (9932) Object info.0.sysinfo.cpu.currentLoad.currentLoad is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2022-01-31 23:45:51.996 - warn: info.0 (9932) This object will not be created in future versions. Please report this to the developer.
2022-01-31 23:45:51.998 - warn: info.0 (9932) Object info.0.sysinfo.cpu.currentLoad.currentLoadUser is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2022-01-31 23:45:51.999 - warn: info.0 (9932) This object will not be created in future versions. Please report this to the developer.
2022-01-31 23:45:52.000 - warn: info.0 (9932) Object info.0.sysinfo.cpu.currentLoad.currentLoadSystem is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2022-01-31 23:45:52.000 - warn: info.0 (9932) This object will not be created in future versions. Please report this to the developer.
2022-01-31 23:45:52.002 - warn: info.0 (9932) Object info.0.sysinfo.cpu.currentLoad.currentLoadNice is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2022-01-31 23:45:52.002 - warn: info.0 (9932) This object will not be created in future versions. Please report this to the developer.
2022-01-31 23:45:52.003 - warn: info.0 (9932) Object info.0.sysinfo.cpu.currentLoad.currentLoadIdle is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2022-01-31 23:45:52.003 - warn: info.0 (9932) This object will not be created in future versions. Please report this to the developer.
2022-01-31 23:45:52.004 - warn: info.0 (9932) Object info.0.sysinfo.cpu.currentLoad.currentLoadIrq is invalid: obj.common.min has an invalid type! Expected "number", received "string"
2022-01-31 23:45:52.005 - warn: info.0 (9932) This object will not be created in future versions. Please report this to the developer.

edit: war etwas zu schnell.
Fehler war vorher auch schon da, war aber vorher Info, jetzt Warnung

amg_666

@apollon77
update lief durch:

The object "system.certificates" was updated successfully.
States DB type migrated from "file" to "jsonl"
Objects DB type migrated from "file" to "jsonl"
ioBroker configuration updated
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (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":"x64"})
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":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/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":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/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":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/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":"x64"})

+ iobroker.js-controller@4.0.0-alpha.67-20220131-6621d47f
added 21 packages from 19 contributors, removed 1 package and updated 38 packages in 91.744s

183 packages are looking for funding
  run `npm fund` for details

Im Admin kam erstmal nix, das liegt aber glaube ich am Firefox und dem Cache. Nach F5 kam dann

Update Slave lief auch durch, da kam dann allerdings


   ╭───────────────────────────────────────────────────────────────╮
   │                                                               │
   │     New major version of npm available! 6.14.15 -> 8.3.0      │
   │   Changelog: https://github.com/npm/cli/releases/tag/v8.3.0   │
   │               Run npm install -g npm to update!               │
   │                                                               │
   ╰───────────────────────────────────────────────────────────────╯

pi@iostrom:/opt/iobroker $
pi@iostrom:/opt/iobroker $ + iobroker.js-controller@4.0.0-alpha.67-20220131-6621d47f
-bash: +: Kommando nicht gefunden.
pi@iostrom:/opt/iobroker $ added 46 packages from 20 contributors, removed 146 packages and updated 38 packages in 122.123s
-bash: added: Kommando nicht gefunden.
pi@iostrom:/opt/iobroker $
pi@iostrom:/opt/iobroker $ 38 packages are looking for funding
-bash: 38: Kommando nicht gefunden.
pi@iostrom:/opt/iobroker $   run `npm fund` for details

Soll npm 8.3.0 installiert werden ???? Ich denke mal nein, oder?

Fazit: Alle Instanzen grün, System läuft

Thomas Braun

@amg_666 sagte in Alpha Test js-controller 4.0:

Soll npm 8.3.0 installiert werden ???? Ich denke mal nein, oder?

Nein, die Meldung kommt auch nicht vom iobroker sondern von npm selber.

apollon77

@maik-0 ja weil das Objekt falsch ist. In dem Fall definiert ein Objekt einen minimum Wert welcher den falschen datentyp hat. Bitte wie üblich beim Adapter ein issue anlegen

apollon77

@amg_666 naja schau mal genau hin. Du hattest ein + vor dem npm Befehl und da kamen die bash Fehler her. Und nein funniest keine npm Updates machen ;-))

Thomas Braun

@apollon77

Edgy (node17/npm8) Testing meldet beim Upgrade von Adaptern:

RangeError: Maximum call stack size exceeded
Cannot upgrade: Maximum call stack size exceeded

echad@chet:~ $ iobroker update -u && iobroker upgrade all
Used repository: live-beta
Adapter    "socketio"     : 4.1.0    , installed 4.0.3  [Updatable]
Adapter    "web"          : 4.1.0    , installed 4.0.1  [Updatable]
Exception in PromiseRejectCallback:
/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:139
    };
    ^

RangeError: Maximum call stack size exceeded
Exception in PromiseRejectCallback:
/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupUpgrade.js:128
            await this.upgradeAdapterHelper(repo, sortedAdapters, forceDowngrade, autoConfirm);
                       ^

RangeError: Maximum call stack size exceeded
Cannot upgrade: Maximum call stack size exceeded
echad@chet:~ $

apollon77

@thomas-braun GitHub Issue im Controller bitte

Thomas Braun

@apollon77

Einzeln lief es jetzt durch:

iobroker upgrade web

war okay, danach war angeblich socketio auch aktualisiert.

arteck

@apollon77 das ist der
@thomas-braun

iobroker upgrade all

J:\source\ioBroker\SmartHome2>iobroker upgrade all
Exception in PromiseRejectCallback:
J:\source\ioBroker\SmartHome2\node_modules\iobroker.js-controller\lib\setup\setupUpgrade.js:139
    };
    ^

RangeError: Maximum call stack size exceeded
Exception in PromiseRejectCallback:
J:\source\ioBroker\SmartHome2\node_modules\iobroker.js-controller\lib\setup\setupUpgrade.js:128
            await this.upgradeAdapterHelper(repo, sortedAdapters, forceDowngrade, autoConfirm);
                       ^

RangeError: Maximum call stack size exceeded
Cannot upgrade: Maximum call stack size exceeded

J:\source\ioBroker\SmartHome2>

apollon77

@maik-0 Neue info Adapter Version auf GitHub (und auf dem Weg ins Repo) 1.9.18 sollte das fixen

apollon77

@thomas-braun sagte in Alpha Test js-controller 4.0:

war okay, danach war angeblich socketio auch aktualisiert.

Ja das liegt an internen dependencies. "unrelated"

apollon77

@thomas-braun @arteck Grund gefunden

NEWS

Alpha Test js-controller 4.0

Support us

817
Online

31.7k
Users

79.8k
Topics

1.3m
Posts

NEWS

Alpha Test js-controller 4.0

Support us

817Online

31.7kUsers

79.8kTopics

1.3mPosts

817
Online

31.7k
Users

79.8k
Topics

1.3m
Posts