Beta Test js-controller Kiera (v6.0)

[mcm1957]

@homoran
Nö
Er hat einen Feature Request.
Derzeit startet iob fix das System nach dem Fixen. Er hätte gerne dass das nicht passiert da er typisch nach dem iob fix das Betriebssystem restartet u daher den iob eh stoppt

[Homoran]

@mcm1957 sagte in Beta Test js-controller Kiera (v6.0):

Er hat einen Feature Request.

also meint er

@uwerlp sagte in Beta Test js-controller Kiera (v6.0):

Wäre es möglich es so umzusetzen, dass dieses Kommando ioBroker nicht startet?

[Gaspode]

@uwerlp said in Beta Test js-controller Kiera (v6.0):

Wäre es möglich das dieses Kommando ioBroker nicht startet? Wenn ich den Aufrufe dann habe ich Wartungsarbeiten an Windows/Software durchgeführt und der Rechner wird im Nachgang neu gestartet dazu stoppe ich IOB erst wieder.

Beim Windows Neustart werden ja sowieso alle Services gestoppt, insofern schadet es nicht, wenn ioBroker läuft.

Warum "iob fix" unter Windows den Service startet, kann ich dir auch nicht beantworten, das hat @apollon77 seinerzeit so implementiert.

Ändern wäre imo suboptimal, da der GUI Installer davon ausgeht, dass fix den ioBroker startet. Würde man das ändern, würde am Ende von fix eine Fehlermeldung geworfen.

Ich plädiere also dafür, das zu lassen wie es ist.

[Feuersturm]

@foxriver76
Update vom Master mit Admin 7.0.9 und js-controller Update von 6.0.5 auf 6.0.6

Auch mit Admin 7.0.9 bleibt am Ende vom js-controller Update auf 6.0.6 das hier stehen:

Nach einiger Zeit startet Admin neu und das System fährt hoch.
Im Log steht noch folgendes:

2024-07-02 20:47:42.171 - info: host.ioBrokerTestsystem instance system.adapter.radar-trap.0 terminated with code 0 (NO_ERROR)
2024-07-02 20:47:42.174 - info: host.ioBrokerTestsystem instance system.adapter.worx.0 terminated with code 0 (NO_ERROR)
2024-07-02 20:47:42.177 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:42.848 - warn: host.ioBrokerTestsystem instance system.adapter.hm-rega.0 terminated due to SIGKILL
2024-07-02 20:47:42.851 - info: host.ioBrokerTestsystem instance system.adapter.hm-rega.0 terminated with code null ()
2024-07-02 20:47:42.854 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:42.934 - warn: host.ioBrokerTestsystem instance system.adapter.hue.0 terminated due to SIGKILL
2024-07-02 20:47:42.937 - info: host.ioBrokerTestsystem instance system.adapter.hue.0 terminated with code null ()
2024-07-02 20:47:42.940 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:42.942 - warn: host.ioBrokerTestsystem instance system.adapter.samsung.0 terminated due to SIGKILL
2024-07-02 20:47:42.945 - info: host.ioBrokerTestsystem instance system.adapter.samsung.0 terminated with code null ()
2024-07-02 20:47:42.947 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:43.035 - warn: host.ioBrokerTestsystem instance system.adapter.web.0 terminated due to SIGKILL
2024-07-02 20:47:43.037 - info: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code null ()
2024-07-02 20:47:43.039 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:43.113 - warn: host.ioBrokerTestsystem instance system.adapter.echarts.0 terminated due to SIGKILL
2024-07-02 20:47:43.116 - info: host.ioBrokerTestsystem instance system.adapter.echarts.0 terminated with code null ()
2024-07-02 20:47:43.118 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:43.122 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: DB closed
2024-07-02 20:47:43.124 - error: host.ioBrokerTestsystem Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
2024-07-02 20:47:43.127 - error: host.ioBrokerTestsystem Caught by controller[0]: at Redis.setex (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
2024-07-02 20:47:43.129 - error: host.ioBrokerTestsystem Caught by controller[0]: at StateRedisClient.setSession (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1403:31)
2024-07-02 20:47:43.132 - error: host.ioBrokerTestsystem Caught by controller[0]: at Admin._setSession (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:1400:22)
2024-07-02 20:47:43.135 - error: host.ioBrokerTestsystem Caught by controller[0]: at Admin.setSession (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:1390:21)
2024-07-02 20:47:43.137 - error: host.ioBrokerTestsystem Caught by controller[0]: at AdapterStore.set (/opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/session.ts:73:26)
2024-07-02 20:47:43.140 - error: host.ioBrokerTestsystem Caught by controller[0]: at Session.save (/opt/iobroker/node_modules/express-session/session/session.js:72:25)
2024-07-02 20:47:43.143 - error: host.ioBrokerTestsystem Caught by controller[0]: at Session.save (/opt/iobroker/node_modules/express-session/index.js:414:15)
2024-07-02 20:47:43.146 - error: host.ioBrokerTestsystem Caught by controller[0]: at ServerResponse.end (/opt/iobroker/node_modules/express-session/index.js:343:21)
2024-07-02 20:47:43.149 - error: host.ioBrokerTestsystem Caught by controller[0]: at ServerResponse.send (/opt/iobroker/node_modules/express/lib/response.js:233:10)
2024-07-02 20:47:43.151 - warn: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated due to SIGKILL
2024-07-02 20:47:43.153 - info: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated with code null ()
2024-07-02 20:47:43.156 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-02 20:47:43.280 - info: host.ioBrokerTestsystem terminated
2024-07-02 20:47:47.578 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
2024-07-02 20:47:47.597 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
2024-07-02 20:49:06.766 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Final information delivered
2024-07-02 20:49:06.889 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
2024-07-02 20:49:11.056 - info: host.ioBrokerTestsystem iobroker.js-controller version 6.0.6 js-controller starting
2024-07-02 20:49:11.073 - info: host.ioBrokerTestsystem Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-07-02 20:49:11.078 - info: host.ioBrokerTestsystem hostname: ioBrokerTestsystem, node: v18.20.3
2024-07-02 20:49:11.083 - info: host.ioBrokerTestsystem ip addresses: 192.168.178.77 fe80::f854:cfff:fe5f:6c25
2024-07-02 20:49:15.013 - info: host.ioBrokerTestsystem connected to Objects and States
2024-07-02 20:49:15.058 - info: host.ioBrokerTestsystem added notifications configuration of host
2024-07-02 20:49:16.840 - info: host.ioBrokerTestsystem 65 instances found
2024-07-02 20:49:16.951 - info: host.ioBrokerTestsystem starting 33 instances

[UweRLP]

@gaspode sagte in Beta Test js-controller Kiera (v6.0):

@uwerlp said in Beta Test js-controller Kiera (v6.0):

Wäre es möglich das dieses Kommando ioBroker nicht startet? Wenn ich den Aufrufe dann habe ich Wartungsarbeiten an Windows/Software durchgeführt und der Rechner wird im Nachgang neu gestartet dazu stoppe ich IOB erst wieder.

Beim Windows Neustart werden ja sowieso alle Services gestoppt, insofern schadet es nicht, wenn ioBroker läuft.

Ich habe leider die Erfahrung machen müssen das ioBroker sich nicht immer vollständig beendet, zumindest mit iobroker stop, selbst mit js-controller 6.x besteht das Problem noch.
Wollen wir hoffen das es bei einem Neustart von Windows anderst ist

Ich plädiere also dafür, das zu lassen wie es ist.

Alles gut, war nur ne' Frage

[apollon77]

@uwerlp Hast Du dazu mehr Details? ALso unter Linux passiert das nicht. Wäre dann super mal ein Log davon zu sehen als Issue im GitHub mit der Info was denn noch lief

[UweRLP]

@apollon77 Leider nicht wirklich mehr Details.
Ich habe den Eindruck, dass der javascript Adapter (ja meine den Script Adapter) beendet wird bei iob stop aber dann wieder neu startet. Ist dies der Fall dann werden auch die anderen Adapter nicht gestoppt. Kann man sehr schön über den Windows Taskmanager verfolgen, die Auslastung des Systems geht dann auch hoch.
Wenn ich nach einem iob stop feststelle, dass sich ioBroker nicht beendet dann schicke ich einen iob stop javascript hinterher, dann werden auch alle anderen Adapter beendet.
Leider passiert das häufig aber nicht immer, gerade habe ich ioBroker gestoppt und dieser wurde einwandfrei beendet.
Welches Log ist dann für dich interessant? Wenn ich nächstes mal auf das Problem stoße werde ich in GitHub ein Issue auf machen.

[apollon77]

@uwerlp sagte in Beta Test js-controller Kiera (v6.0):

Welches Log ist dann für dich interessant? Wenn ich nächstes mal auf das Problem stoße werde ich in GitHub ein Issue auf machen.

Der Shutdown Prozess sollte an sich dinge loggen, also /opt/iobroker/log/...

[Gaspode]

@apollon77 said in Beta Test js-controller Kiera (v6.0):

Der Shutdown Prozess sollte an sich dinge loggen, also /opt/iobroker/log/...

Unter Windows wird da leider wenig bis nix gelogged, @mcm1957 hat dafür mal ein Issue geschrieben:
https://github.com/ioBroker/ioBroker.js-controller/issues/2764

Das Verhalten, dass da einzelne Adapter Prozesse wieder gestartet werden, kenne ich nicht. Es kommt jedoch sehr selten vor, dass die Node-Prozesse nicht gestoppt werden. Ich hab da aber noch keine Systematik erkannt.

mcm1957 created this issue in ioBroker/ioBroker.js-controller

closed [enhancement]: graceful shutdown on windows #2764

[UweRLP]

@apollon77 sagte in Beta Test js-controller Kiera (v6.0):

@uwerlp sagte in Beta Test js-controller Kiera (v6.0):

Welches Log ist dann für dich interessant? Wenn ich nächstes mal auf das Problem stoße werde ich in GitHub ein Issue auf machen.

Der Shutdown Prozess sollte an sich dinge loggen, also /opt/iobroker/log/...

Heute rein gestellt.
https://github.com/ioBroker/ioBroker.js-controller/issues/2834

UweRP created this issue in ioBroker/ioBroker.js-controller

closed [bug]: iob beendet sich nicht immer unter Windows #2834

[UweRLP]

@gaspode sagte in Beta Test js-controller Kiera (v6.0):

Das Verhalten, dass da einzelne Adapter Prozesse wieder gestartet werden, kenne ich nicht. Es kommt jedoch sehr selten vor, dass die Node-Prozesse nicht gestoppt werden. Ich hab da aber noch keine Systematik erkannt.

Beim javascript Adapter ist es bei mir halt auffällig da zum start des Adapters Blocklys gestartet werden.

[Feuersturm]

@foxriver76 Ich weiß nicht ob dieses Thema ein js-controller oder admin Thema ist.

Ich habe Admin heute auf 7.0.12 aktualisiert. Changelog von 7.0.12: " (bluefox) Changed a recommended node.js version from 18 to 20"
Durch Zufall hab ich auf der Übersichtsseite vom Admin diesen kleinen Updatebutton gefunden

Todesmutig draufgedrückt kommt die Meldung

Nach Bestätigung passiert Magie im Hintergrund. So sieht das log aus:

Spoiler

2024-07-10 20:30:23.899 - info: dwd.0 (16439) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.20.3, js-controller: 6.0.6
2024-07-10 20:30:24.529 - info: host.ioBrokerTestsystem instance system.adapter.ical.5 having pid 16378 terminated with code 0 (NO_ERROR)
2024-07-10 20:30:25.561 - info: dwd.0 (16439) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-07-10 20:30:26.233 - info: host.ioBrokerTestsystem instance system.adapter.dwd.0 having pid 16439 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-07-10 20:30:52.692 - info: host.ioBrokerTestsystem Restart js-controller because desired after package upgrade
2024-07-10 20:30:53.099 - info: host.ioBrokerTestsystem received SIGTERM
2024-07-10 20:30:53.183 - info: hm-rpc.0 (440) xmlrpc -> 192.168.178.84:2010/ init ["http://192.168.178.77:2010",""]
2024-07-10 20:30:53.166 - info: backitup.0 (400) cleaned everything up...
2024-07-10 20:30:53.236 - info: hm-rpc.0 (440) Disconnected
2024-07-10 20:30:53.261 - info: admin.0 (16303) terminating http server on port 8081
2024-07-10 20:30:53.225 - info: unifi.0 (517) cleaned everything up...
2024-07-10 20:30:53.329 - info: trashschedule.0 (594) cleaned everything up...
2024-07-10 20:30:53.319 - warn: web.0 (683) setTimeout called, but adapter is shutting down
2024-07-10 20:30:53.376 - info: javascript.0 (351) Stopping script script.js.Skripte.Kalender.muellkalender
2024-07-10 20:30:53.345 - info: vis-inventwo.0 (646) cleaned everything up...
2024-07-10 20:30:53.298 - info: valloxmv.0 (609) cleaned everything up...
2024-07-10 20:30:53.243 - info: device-watcher.0 (407) cleaned everything up...
2024-07-10 20:30:53.110 - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 (force=false, process=true)
2024-07-10 20:30:53.114 - info: host.ioBrokerTestsystem stopInstance system.adapter.influxdb.0 (force=false, process=true)
2024-07-10 20:30:53.120 - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 (force=false, process=true)
2024-07-10 20:30:53.125 - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 (force=false, process=true)
2024-07-10 20:30:53.128 - info: host.ioBrokerTestsystem stopInstance system.adapter.scheduler.0 (force=false, process=true)
2024-07-10 20:30:53.132 - info: host.ioBrokerTestsystem stopInstance system.adapter.telegram.0 (force=false, process=false)
2024-07-10 20:30:53.140 - info: host.ioBrokerTestsystem stopInstance system.adapter.backitup.0 (force=false, process=true)
2024-07-10 20:30:53.144 - info: host.ioBrokerTestsystem stopInstance system.adapter.device-watcher.0 (force=false, process=true)
2024-07-10 20:30:53.148 - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 (force=false, process=true)
2024-07-10 20:30:53.152 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rega.0 (force=false, process=true)
2024-07-10 20:30:53.156 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
2024-07-10 20:30:53.160 - info: host.ioBrokerTestsystem stopInstance system.adapter.hue.0 (force=false, process=true)
2024-07-10 20:30:53.166 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.0 (force=false, process=false)
2024-07-10 20:30:53.180 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.1 (force=false, process=false)
2024-07-10 20:30:53.399 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.2 (force=false, process=false)
2024-07-10 20:30:53.469 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.3 (force=false, process=false)
2024-07-10 20:30:53.517 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.4 (force=false, process=false)
2024-07-10 20:30:53.533 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.5 (force=false, process=false)
2024-07-10 20:30:53.556 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.5
2024-07-10 20:30:53.563 - info: host.ioBrokerTestsystem stopInstance system.adapter.mqtt.0 (force=false, process=false)
2024-07-10 20:30:53.571 - info: host.ioBrokerTestsystem stopInstance system.adapter.openweathermap.0 (force=false, process=false)
2024-07-10 20:30:53.574 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.openweathermap.0
2024-07-10 20:30:53.578 - info: host.ioBrokerTestsystem stopInstance system.adapter.proxmox.0 (force=false, process=true)
2024-07-10 20:30:53.583 - info: host.ioBrokerTestsystem stopInstance system.adapter.rainbird.0 (force=false, process=false)
2024-07-10 20:30:53.587 - info: host.ioBrokerTestsystem stopInstance system.adapter.spotify-premium.0 (force=false, process=false)
2024-07-10 20:30:53.591 - info: host.ioBrokerTestsystem stopInstance system.adapter.tr-064.0 (force=false, process=true)
2024-07-10 20:30:53.595 - info: host.ioBrokerTestsystem stopInstance system.adapter.unifi.0 (force=false, process=true)
2024-07-10 20:30:53.599 - info: host.ioBrokerTestsystem stopInstance system.adapter.worx.0 (force=false, process=true)
2024-07-10 20:30:53.604 - info: host.ioBrokerTestsystem stopInstance system.adapter.samsung.0 (force=false, process=true)
2024-07-10 20:30:53.608 - info: host.ioBrokerTestsystem stopInstance system.adapter.benchmark.0 (force=false, process=false)
2024-07-10 20:30:53.613 - info: host.ioBrokerTestsystem stopInstance system.adapter.daswetter.0 (force=false, process=false)
2024-07-10 20:30:53.619 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.daswetter.0
2024-07-10 20:30:53.623 - info: host.ioBrokerTestsystem stopInstance system.adapter.dwd.0 (force=false, process=false)
2024-07-10 20:30:53.627 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.dwd.0
2024-07-10 20:30:53.631 - info: host.ioBrokerTestsystem stopInstance system.adapter.fully-tablet-control.0 (force=false, process=false)
2024-07-10 20:30:53.636 - info: host.ioBrokerTestsystem stopInstance system.adapter.nina.0 (force=false, process=true)
2024-07-10 20:30:53.641 - info: host.ioBrokerTestsystem stopInstance system.adapter.sayit.0 (force=false, process=false)
2024-07-10 20:30:53.647 - info: host.ioBrokerTestsystem stopInstance system.adapter.simple-api.0 (force=false, process=false)
2024-07-10 20:30:53.652 - info: host.ioBrokerTestsystem stopInstance system.adapter.socketio.0 (force=false, process=false)
2024-07-10 20:30:53.657 - info: host.ioBrokerTestsystem stopInstance system.adapter.tankerkoenig.0 (force=false, process=true)
2024-07-10 20:30:53.662 - info: host.ioBrokerTestsystem stopInstance system.adapter.trashschedule.0 (force=false, process=true)
2024-07-10 20:30:53.671 - info: host.ioBrokerTestsystem stopInstance system.adapter.valloxmv.0 (force=false, process=true)
2024-07-10 20:30:53.676 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-energy.0 (force=false, process=false)
2024-07-10 20:30:53.684 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-gauges.0 (force=false, process=false)
2024-07-10 20:30:53.701 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-jaeger-design.0 (force=false, process=false)
2024-07-10 20:30:53.705 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-material.0 (force=false, process=false)
2024-07-10 20:30:53.711 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2.0 (force=false, process=true)
2024-07-10 20:30:53.718 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-fancyswitch.0 (force=false, process=false)
2024-07-10 20:30:53.724 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-google-fonts.0 (force=false, process=false)
2024-07-10 20:30:53.729 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-history.0 (force=false, process=false)
2024-07-10 20:30:53.733 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-inventwo.0 (force=false, process=true)
2024-07-10 20:30:53.748 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false)
2024-07-10 20:30:53.751 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-justgage.0 (force=false, process=false)
2024-07-10 20:30:53.759 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-map.0 (force=false, process=false)
2024-07-10 20:30:53.762 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false)
2024-07-10 20:30:53.764 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
2024-07-10 20:30:53.768 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis.0 (force=false, process=false)
2024-07-10 20:30:53.772 - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 (force=false, process=true)
2024-07-10 20:30:53.776 - info: host.ioBrokerTestsystem stopInstance system.adapter.echarts.0 (force=false, process=true)
2024-07-10 20:30:53.782 - info: host.ioBrokerTestsystem stopInstance system.adapter.device-manager.0 (force=false, process=true)
2024-07-10 20:30:53.785 - info: host.ioBrokerTestsystem stopInstance system.adapter.discovery.1 (force=false, process=true)
2024-07-10 20:30:53.794 - info: host.ioBrokerTestsystem stopInstance system.adapter.radar-trap.0 (force=false, process=true)
2024-07-10 20:30:54.130 - info: admin.0 (16303) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.169 - info: device-watcher.0 (407) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.168 - info: backitup.0 (400) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.132 - info: scenes.0 (362) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.193 - info: hm-rega.0 (425) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.200 - info: hm-rpc.0 (440) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.190 - info: fritzbox.0 (418) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.151 - info: scheduler.0 (393) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.215 - info: hue.0 (462) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.227 - info: worx.0 (524) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.263 - info: web.0 (683) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.223 - info: unifi.0 (517) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.260 - info: vis-inventwo.0 (646) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.249 - info: tankerkoenig.0 (587) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.230 - info: nina.0 (572) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.259 - info: valloxmv.0 (609) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.253 - info: trashschedule.0 (594) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.225 - info: samsung.0 (539) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.219 - info: tr-064.0 (506) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.259 - info: vis-2.0 (16265) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.211 - info: proxmox.0 (499) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.263 - info: echarts.0 (690) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.303 - info: device-manager.0 (701) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.350 - info: radar-trap.0 (715) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.333 - info: discovery.1 (708) Got terminate signal TERMINATE_YOURSELF
2024-07-10 20:30:54.618 - info: scenes.0 (362) terminating with timeout
2024-07-10 20:30:54.651 - info: scheduler.0 (393) terminating with timeout
2024-07-10 20:30:54.633 - info: scenes.0 (362) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.681 - info: fritzbox.0 (418) terminating with timeout
2024-07-10 20:30:54.679 - info: hm-rega.0 (425) terminating with timeout
2024-07-10 20:30:54.689 - info: fritzbox.0 (418) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.657 - info: scheduler.0 (393) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.726 - info: backitup.0 (400) terminating with timeout
2024-07-10 20:30:54.696 - info: hm-rega.0 (425) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.753 - info: fritzbox.0 (418) terminating
2024-07-10 20:30:54.753 - info: vis-inventwo.0 (646) terminating
2024-07-10 20:30:54.753 - info: scheduler.0 (393) terminating
2024-07-10 20:30:54.758 - info: fritzbox.0 (418) terminating
2024-07-10 20:30:54.768 - info: tankerkoenig.0 (587) terminating
2024-07-10 20:30:54.775 - info: valloxmv.0 (609) terminating
2024-07-10 20:30:54.767 - info: radar-trap.0 (715) terminating
2024-07-10 20:30:54.780 - info: unifi.0 (517) terminating
2024-07-10 20:30:54.786 - info: unifi.0 (517) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.763 - info: echarts.0 (690) terminating with timeout
2024-07-10 20:30:54.766 - info: hm-rpc.0 (440) terminating
2024-07-10 20:30:54.774 - info: tankerkoenig.0 (587) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.760 - info: scheduler.0 (393) terminating
2024-07-10 20:30:54.795 - info: unifi.0 (517) terminating
2024-07-10 20:30:54.795 - info: tankerkoenig.0 (587) terminating
2024-07-10 20:30:54.804 - info: tankerkoenig.0 (587) terminating with timeout
2024-07-10 20:30:54.783 - info: hm-rpc.0 (440) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.750 - info: worx.0 (524) terminating with timeout
2024-07-10 20:30:54.756 - info: device-watcher.0 (407) terminating
2024-07-10 20:30:54.790 - info: nina.0 (572) terminating with timeout
2024-07-10 20:30:54.817 - info: discovery.1 (708) terminating with timeout
2024-07-10 20:30:54.775 - info: vis-2.0 (16265) terminating
2024-07-10 20:30:54.770 - info: device-manager.0 (701) terminating
2024-07-10 20:30:54.745 - info: tr-064.0 (506) terminating with timeout
2024-07-10 20:30:54.778 - info: trashschedule.0 (594) terminating
2024-07-10 20:30:54.828 - info: discovery.1 (708) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.848 - info: web.0 (683) terminating with timeout
2024-07-10 20:30:54.816 - info: samsung.0 (539) terminating with timeout
2024-07-10 20:30:54.861 - info: web.0 (683) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.824 - info: nina.0 (572) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.801 - info: valloxmv.0 (609) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.874 - info: unifi.0 (517) terminating with timeout
2024-07-10 20:30:54.874 - info: hue.0 (462) terminating with timeout
2024-07-10 20:30:54.842 - info: vis-inventwo.0 (646) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.718 - info: proxmox.0 (499) terminating with timeout
2024-07-10 20:30:54.848 - info: worx.0 (524) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.919 - info: hm-rega.0 (425) terminating
2024-07-10 20:30:54.918 - info: vis-inventwo.0 (646) terminating
2024-07-10 20:30:54.850 - info: admin.0 (16303) terminating with timeout
2024-07-10 20:30:54.934 - info: discovery.1 (708) terminating
2024-07-10 20:30:54.902 - info: backitup.0 (400) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.941 - info: vis-inventwo.0 (646) terminating with timeout
2024-07-10 20:30:54.940 - info: discovery.1 (708) terminating
2024-07-10 20:30:54.880 - info: hue.0 (462) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.957 - info: influxdb.0 (340) terminating
2024-07-10 20:30:54.965 - warn: host.ioBrokerTestsystem instance system.adapter.javascript.0 terminated due to SIGTERM
2024-07-10 20:30:54.888 - info: proxmox.0 (499) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.971 - info: host.ioBrokerTestsystem instance system.adapter.javascript.0 terminated with code null ()
2024-07-10 20:30:54.993 - info: web.0 (683) terminating
2024-07-10 20:30:54.999 - info: valloxmv.0 (609) terminating with timeout
2024-07-10 20:30:54.936 - info: admin.0 (16303) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.907 - info: samsung.0 (539) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.922 - info: scenes.0 (362) terminating
2024-07-10 20:30:55.052 - info: backitup.0 (400) terminating
2024-07-10 20:30:54.974 - info: worx.0 (524) terminating
2024-07-10 20:30:54.914 - info: device-watcher.0 (407) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.883 - info: echarts.0 (690) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:55.048 - info: hue.0 (462) terminating
2024-07-10 20:30:54.995 - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 send kill signal
2024-07-10 20:30:55.011 - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 send kill signal
2024-07-10 20:30:55.018 - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 send kill signal
2024-07-10 20:30:55.024 - info: host.ioBrokerTestsystem stopInstance system.adapter.scheduler.0 send kill signal
2024-07-10 20:30:55.029 - info: host.ioBrokerTestsystem stopInstance system.adapter.backitup.0 send kill signal
2024-07-10 20:30:55.036 - info: host.ioBrokerTestsystem stopInstance system.adapter.device-watcher.0 send kill signal
2024-07-10 20:30:55.040 - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 send kill signal
2024-07-10 20:30:55.045 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rega.0 send kill signal
2024-07-10 20:30:55.049 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 send kill signal
2024-07-10 20:30:55.053 - info: host.ioBrokerTestsystem stopInstance system.adapter.hue.0 send kill signal
2024-07-10 20:30:55.031 - info: nina.0 (572) terminating
2024-07-10 20:30:55.057 - info: worx.0 (524) terminating
2024-07-10 20:30:55.056 - info: backitup.0 (400) terminating
2024-07-10 20:30:54.969 - info: influxdb.0 (340) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:55.091 - info: echarts.0 (690) terminating
2024-07-10 20:30:55.089 - info: device-watcher.0 (407) terminating with timeout
2024-07-10 20:30:55.218 - info: hm-rpc.0 (440) terminating with timeout
2024-07-10 20:30:54.887 - info: tr-064.0 (506) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.944 - info: tr-064.0 (506) terminating
2024-07-10 20:30:55.053 - info: tr-064.0 (506) terminating
2024-07-10 20:30:55.067 - info: scenes.0 (362) terminating
2024-07-10 20:30:55.108 - info: nina.0 (572) terminating
2024-07-10 20:30:54.894 - info: trashschedule.0 (594) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.977 - info: trashschedule.0 (594) terminating with timeout
2024-07-10 20:30:55.121 - info: trashschedule.0 (594) terminating
2024-07-10 20:30:55.269 - info: valloxmv.0 (609) terminating
2024-07-10 20:30:54.784 - info: radar-trap.0 (715) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.927 - info: radar-trap.0 (715) terminating with timeout
2024-07-10 20:30:55.078 - info: radar-trap.0 (715) terminating
2024-07-10 20:30:55.102 - info: host.ioBrokerTestsystem stopInstance system.adapter.proxmox.0 send kill signal
2024-07-10 20:30:55.109 - info: host.ioBrokerTestsystem stopInstance system.adapter.tr-064.0 send kill signal
2024-07-10 20:30:55.118 - info: host.ioBrokerTestsystem stopInstance system.adapter.unifi.0 send kill signal
2024-07-10 20:30:55.122 - info: host.ioBrokerTestsystem stopInstance system.adapter.worx.0 send kill signal
2024-07-10 20:30:55.125 - info: host.ioBrokerTestsystem stopInstance system.adapter.samsung.0 send kill signal
2024-07-10 20:30:55.129 - info: host.ioBrokerTestsystem stopInstance system.adapter.nina.0 send kill signal
2024-07-10 20:30:55.133 - info: host.ioBrokerTestsystem stopInstance system.adapter.tankerkoenig.0 send kill signal
2024-07-10 20:30:55.136 - info: host.ioBrokerTestsystem stopInstance system.adapter.trashschedule.0 send kill signal
2024-07-10 20:30:55.139 - info: host.ioBrokerTestsystem stopInstance system.adapter.valloxmv.0 send kill signal
2024-07-10 20:30:55.143 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2.0 send kill signal
2024-07-10 20:30:55.147 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-inventwo.0 send kill signal
2024-07-10 20:30:55.150 - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 send kill signal
2024-07-10 20:30:55.153 - info: host.ioBrokerTestsystem stopInstance system.adapter.echarts.0 send kill signal
2024-07-10 20:30:55.157 - info: host.ioBrokerTestsystem stopInstance system.adapter.device-manager.0 send kill signal
2024-07-10 20:30:55.160 - info: host.ioBrokerTestsystem stopInstance system.adapter.discovery.1 send kill signal
2024-07-10 20:30:55.164 - info: host.ioBrokerTestsystem stopInstance system.adapter.radar-trap.0 send kill signal
2024-07-10 20:30:55.030 - info: proxmox.0 (499) terminating
2024-07-10 20:30:55.136 - info: proxmox.0 (499) terminating
2024-07-10 20:30:54.836 - info: device-manager.0 (701) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.862 - info: device-manager.0 (701) terminating with timeout
2024-07-10 20:30:55.148 - info: device-manager.0 (701) terminating
2024-07-10 20:30:55.082 - info: samsung.0 (539) terminating
2024-07-10 20:30:55.086 - info: samsung.0 (539) terminating
2024-07-10 20:30:54.835 - info: vis-2.0 (16265) Terminated (NO_ERROR): Without reason
2024-07-10 20:30:54.984 - info: vis-2.0 (16265) terminating with timeout
2024-07-10 20:30:55.113 - info: vis-2.0 (16265) terminating
2024-07-10 20:30:55.015 - info: admin.0 (16303) terminating
2024-07-10 20:30:55.118 - info: admin.0 (16303) terminating
2024-07-10 20:30:55.691 - info: hm-rpc.0 (440) terminating
2024-07-10 20:30:55.704 - info: device-watcher.0 (407) terminating
2024-07-10 20:30:55.746 - info: hue.0 (462) cleaned everything up...
2024-07-10 20:30:55.788 - warn: hue.0 (462) get state error: Connection is closed.
2024-07-10 20:30:55.794 - info: hue.0 (462) terminating
2024-07-10 20:30:55.844 - warn: admin.0 (16303) redis get system.host.ioBrokerTestsystem.alive, error - Connection is closed.
2024-07-10 20:30:56.082 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.admin.0 killing pid 16303
2024-07-10 20:30:56.098 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.scenes.0 killing pid 362
2024-07-10 20:30:56.117 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.scheduler.0 killing pid 393
2024-07-10 20:30:56.120 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.backitup.0 killing pid 400
2024-07-10 20:30:56.148 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.device-watcher.0 killing pid 407
2024-07-10 20:30:56.158 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.fritzbox.0 killing pid 418
2024-07-10 20:30:56.168 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.hm-rega.0 killing pid 425
2024-07-10 20:30:56.172 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.hm-rpc.0 killing pid 440
2024-07-10 20:30:56.176 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.hue.0 killing pid 462
2024-07-10 20:30:56.229 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.proxmox.0 killing pid 499
2024-07-10 20:30:56.258 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.tr-064.0 killing pid 506
2024-07-10 20:30:56.300 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.unifi.0 killing pid 517
2024-07-10 20:30:56.305 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.worx.0 killing pid 524
2024-07-10 20:30:56.308 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.samsung.0 killing pid 539
2024-07-10 20:30:56.311 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.nina.0 killing pid 572
2024-07-10 20:30:56.315 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.tankerkoenig.0 killing pid 587
2024-07-10 20:30:56.318 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.trashschedule.0 killing pid 594
2024-07-10 20:30:56.322 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.valloxmv.0 killing pid 609
2024-07-10 20:30:56.338 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.vis-2.0 killing pid 16265
2024-07-10 20:30:56.346 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.vis-inventwo.0 killing pid 646
2024-07-10 20:30:56.357 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.web.0 killing pid 683
2024-07-10 20:30:56.372 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.echarts.0 killing pid 690
2024-07-10 20:30:56.390 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.device-manager.0 killing pid 701
2024-07-10 20:30:56.406 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.discovery.1 killing pid 708
2024-07-10 20:30:56.432 - info: host.ioBrokerTestsystem stopInstance timeout system.adapter.radar-trap.0 killing pid 715
2024-07-10 20:31:00.868 - warn: host.ioBrokerTestsystem instance system.adapter.scenes.0 terminated due to SIGKILL
2024-07-10 20:31:00.872 - info: host.ioBrokerTestsystem instance system.adapter.scenes.0 terminated with code null ()
2024-07-10 20:31:01.437 - warn: host.ioBrokerTestsystem instance system.adapter.scheduler.0 terminated due to SIGKILL
2024-07-10 20:31:01.447 - info: host.ioBrokerTestsystem instance system.adapter.scheduler.0 terminated with code null ()
2024-07-10 20:31:01.451 - warn: host.ioBrokerTestsystem instance system.adapter.backitup.0 terminated due to SIGKILL
2024-07-10 20:31:01.454 - info: host.ioBrokerTestsystem instance system.adapter.backitup.0 terminated with code null ()
2024-07-10 20:31:01.527 - warn: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated due to SIGKILL
2024-07-10 20:31:01.532 - info: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated with code null ()
2024-07-10 20:31:01.737 - warn: host.ioBrokerTestsystem instance system.adapter.device-watcher.0 terminated due to SIGKILL
2024-07-10 20:31:01.740 - info: host.ioBrokerTestsystem instance system.adapter.device-watcher.0 terminated with code null ()
2024-07-10 20:31:01.743 - warn: host.ioBrokerTestsystem instance system.adapter.fritzbox.0 terminated due to SIGKILL
2024-07-10 20:31:01.746 - info: host.ioBrokerTestsystem instance system.adapter.fritzbox.0 terminated with code null ()
2024-07-10 20:31:02.273 - warn: host.ioBrokerTestsystem instance system.adapter.hm-rega.0 terminated due to SIGKILL
2024-07-10 20:31:02.279 - info: host.ioBrokerTestsystem instance system.adapter.hm-rega.0 terminated with code null ()
2024-07-10 20:31:02.282 - warn: host.ioBrokerTestsystem instance system.adapter.hm-rpc.0 terminated due to SIGKILL
2024-07-10 20:31:02.288 - info: host.ioBrokerTestsystem instance system.adapter.hm-rpc.0 terminated with code null ()
2024-07-10 20:31:02.450 - warn: host.ioBrokerTestsystem instance system.adapter.hue.0 terminated due to SIGKILL
2024-07-10 20:31:02.453 - info: host.ioBrokerTestsystem instance system.adapter.hue.0 terminated with code null ()
2024-07-10 20:31:02.603 - warn: host.ioBrokerTestsystem instance system.adapter.proxmox.0 terminated due to SIGKILL
2024-07-10 20:31:02.606 - info: host.ioBrokerTestsystem instance system.adapter.proxmox.0 terminated with code null ()
2024-07-10 20:31:02.610 - warn: host.ioBrokerTestsystem instance system.adapter.tr-064.0 terminated due to SIGKILL
2024-07-10 20:31:02.614 - info: host.ioBrokerTestsystem instance system.adapter.tr-064.0 terminated with code null ()
2024-07-10 20:31:02.826 - warn: host.ioBrokerTestsystem instance system.adapter.unifi.0 terminated due to SIGKILL
2024-07-10 20:31:02.837 - info: host.ioBrokerTestsystem instance system.adapter.unifi.0 terminated with code null ()
2024-07-10 20:31:02.976 - warn: host.ioBrokerTestsystem instance system.adapter.worx.0 terminated due to SIGKILL
2024-07-10 20:31:02.979 - info: host.ioBrokerTestsystem instance system.adapter.worx.0 terminated with code null ()
2024-07-10 20:31:02.983 - warn: host.ioBrokerTestsystem instance system.adapter.samsung.0 terminated due to SIGKILL
2024-07-10 20:31:02.986 - info: host.ioBrokerTestsystem instance system.adapter.samsung.0 terminated with code null ()
2024-07-10 20:31:03.200 - warn: host.ioBrokerTestsystem instance system.adapter.nina.0 terminated due to SIGKILL
2024-07-10 20:31:03.205 - info: host.ioBrokerTestsystem instance system.adapter.nina.0 terminated with code null ()
2024-07-10 20:31:03.209 - warn: host.ioBrokerTestsystem instance system.adapter.trashschedule.0 terminated due to SIGKILL
2024-07-10 20:31:03.212 - info: host.ioBrokerTestsystem instance system.adapter.trashschedule.0 terminated with code null ()
2024-07-10 20:31:03.319 - warn: host.ioBrokerTestsystem instance system.adapter.valloxmv.0 terminated due to SIGKILL
2024-07-10 20:31:03.322 - info: host.ioBrokerTestsystem instance system.adapter.valloxmv.0 terminated with code null ()
2024-07-10 20:31:03.460 - warn: host.ioBrokerTestsystem instance system.adapter.vis-inventwo.0 terminated due to SIGKILL
2024-07-10 20:31:03.463 - info: host.ioBrokerTestsystem instance system.adapter.vis-inventwo.0 terminated with code null ()
2024-07-10 20:31:03.466 - warn: host.ioBrokerTestsystem instance system.adapter.web.0 terminated due to SIGKILL
2024-07-10 20:31:03.469 - info: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code null ()
2024-07-10 20:31:03.741 - warn: host.ioBrokerTestsystem instance system.adapter.echarts.0 terminated due to SIGKILL
2024-07-10 20:31:03.744 - info: host.ioBrokerTestsystem instance system.adapter.echarts.0 terminated with code null ()
2024-07-10 20:31:03.748 - warn: host.ioBrokerTestsystem instance system.adapter.device-manager.0 terminated due to SIGKILL
2024-07-10 20:31:03.753 - info: host.ioBrokerTestsystem instance system.adapter.device-manager.0 terminated with code null ()
2024-07-10 20:31:04.137 - warn: host.ioBrokerTestsystem instance system.adapter.discovery.1 terminated due to SIGKILL
2024-07-10 20:31:04.142 - info: host.ioBrokerTestsystem instance system.adapter.discovery.1 terminated with code null ()
2024-07-10 20:31:04.249 - warn: host.ioBrokerTestsystem instance system.adapter.vis-2.0 terminated due to SIGKILL
2024-07-10 20:31:04.252 - info: host.ioBrokerTestsystem instance system.adapter.vis-2.0 terminated with code null ()
2024-07-10 20:31:04.254 - warn: host.ioBrokerTestsystem instance system.adapter.tankerkoenig.0 terminated due to SIGKILL
2024-07-10 20:31:04.257 - info: host.ioBrokerTestsystem instance system.adapter.tankerkoenig.0 terminated with code null ()
2024-07-10 20:31:04.304 - warn: host.ioBrokerTestsystem instance system.adapter.radar-trap.0 terminated due to SIGKILL
2024-07-10 20:31:04.308 - info: host.ioBrokerTestsystem instance system.adapter.radar-trap.0 terminated with code null ()
2024-07-10 20:31:04.529 - info: host.ioBrokerTestsystem instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR)
2024-07-10 20:31:04.533 - info: host.ioBrokerTestsystem All instances are stopped.
2024-07-10 20:31:04.757 - info: host.ioBrokerTestsystem terminated
2024-07-10 20:31:12.212 - info: host.ioBrokerTestsystem iobroker.js-controller version 6.0.6 js-controller starting
2024-07-10 20:31:12.228 - info: host.ioBrokerTestsystem Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-07-10 20:31:12.234 - info: host.ioBrokerTestsystem hostname: ioBrokerTestsystem, node: v18.20.4
2024-07-10 20:31:12.238 - info: host.ioBrokerTestsystem ip addresses: 192.168.178.77 fe80::f854:cfff:fe5f:6c25
2024-07-10 20:31:17.237 - info: host.ioBrokerTestsystem connected to Objects and States
2024-07-10 20:31:17.322 - info: host.ioBrokerTestsystem added notifications configuration of host
2024-07-10 20:31:17.380 - info: host.ioBrokerTestsystem Node.js version has changed from 18.20.3 to 18.20.4
2024-07-10 20:31:17.597 - info: host.ioBrokerTestsystem Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2024-07-10 20:31:19.219 - info: host.ioBrokerTestsystem 65 instances found
2024-07-10 20:31:19.374 - info: host.ioBrokerTestsystem starting 33 instances
2024-07-10 20:31:20.799 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.nodeCurrent"
2024-07-10 20:31:21.096 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.nodeNewest"
2024-07-10 20:31:21.165 - info: host.ioBrokerTestsystem instance system.adapter.admin.0 started with pid 16660
2024-07-10 20:31:21.198 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.nodeNewestNext"
2024-07-10 20:31:21.264 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.npmCurrent"
2024-07-10 20:31:21.289 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.npmNewest"
2024-07-10 20:31:21.300 - info: host.ioBrokerTestsystem Delete state "system.host.ioBrokerTestsystem.versions.npmNewestNext"
2024-07-10 20:31:21.311 - info: host.ioBrokerTestsystem Some obsolete host states deleted.
2024-07-10 20:31:25.542 - info: host.ioBrokerTestsystem instance system.adapter.influxdb.0 started with pid 16667
2024-07-10 20:31:29.090 - info: host.ioBrokerTestsystem instance system.adapter.javascript.0 started with pid 16678
2024-07-10 20:31:33.159 - info: host.ioBrokerTestsystem instance system.adapter.scenes.0 started with pid 16689
2024-07-10 20:31:37.225 - info: host.ioBrokerTestsystem instance system.adapter.scheduler.0 started with pid 16700

Ich sehe hier u.a. folgendes:

...
2024-07-10 20:30:52.692 - info: host.ioBrokerTestsystem Restart js-controller because desired after package upgrade
2024-07-10 20:30:53.099 - info: host.ioBrokerTestsystem received SIGTERM
...
2024-07-10 20:31:17.380 - info: host.ioBrokerTestsystem Node.js version has changed from 18.20.3 to 18.20.4

Ich hätte mit dem Changelog Eintrag vom Admin erwartet, das das System von nodejs 18 auf 20 aktualisiert wird. Was sagst du?

Kannst du sagen, warum der Updatebutton so versteckt ist? Ich hätte eine entsprechenden Button / Updatemöglichkeit im Host Menü erwartet. Ich kann dazu mal ein admin issue erstellen (https://github.com/ioBroker/ioBroker.admin/issues/2543).

Feuer-sturm created this issue in ioBroker/ioBroker.admin

open [enhancement]: Provide button for nodejs update in admin host menu #2543

[Thomas Braun]

@feuersturm sagte in Beta Test js-controller Kiera (v6.0):

Ich hätte mit dem Changelog Eintrag vom Admin erwartet, das das System von nodejs 18 auf 20 aktualisiert wird.

Jein. Im Changelog geht es darum, das im Admin noch die Version 18 hardcoded drin stand. Hat dann z. B. bei iob nodejs-update zu widersprüchlichen Meldungen geführt.

Der Update-Button den du da jetzt gefunden hast aktualisiert nur auf die aktuellste Version, die auch über den Paketmanager 'apt' verfügbar ist. Ein Release-Wechsel ist damit nicht möglich. Sollte es auch imho nicht sein. Die Verwaltung der OS-Pakete und der entsprechenden Quellen sollte dem Paketmanager vorbehalten bleiben.

[Feuersturm]

@thomas-braun Dann ist die Information in der Kachel und und in dem Popup aber noch nicht ausreichend. Ich hätte jetzt auf Basis der sichtbaren Informationen erwartet, dass auf nodejs 20.x aktualisiert wird und nicht auf die aktuelle Minor/Patch Version im aktuellen Major Strang (in diesem Fall 18).

[Thomas Braun]

@feuersturm

Deswegen steht ja auch 'in den konfigurierten apt-Quellen' dabei.

[Feuersturm]

@thomas-braun Ich hab daraus gelesen, dass die Paketquellen Quellen auch im Hintergrund aktualisiert werden in dem Fall auf nodejs 20

[mcm1957]

@thomas-braun
Sorry - Aber das verstehen 90% der User nicht.
Denen sagt apt quellen nix. Auch ich weiss nur sehr ca. Um was es sa geht. Anpassen / ändern könnt ich da nix.

Und warum sollte node nicht auf die empfohlene Version aktualisiert werden? Das node Update script macht es ja auch?

[Thomas Braun]

@mcm1957 sagte in Beta Test js-controller Kiera (v6.0):

Das node Update script macht es ja auch?

Ja, das hat sich aber aus einem nodejs-fix heraus entwickelt, das genau das tun sollte. Verfummelte Paketquellen wieder gerade rücken. Das macht es dann auch (z. T. auch mit der Brechstange).

Dann müsste man im Grunde zwei Buttons haben:

nodejs update -> Update auf die aktuellste Version aus dem derzeitig aktiven Major-Tree
nodejs upgrade -> Upgrade (wenn nötig mit geändertem Repo) auf die aktuell empfohlene Version

[Thomas Braun]

@mcm1957 sagte in Beta Test js-controller Kiera (v6.0):

Denen sagt apt quellen nix.

Da ist aber Schade, denn das sind absolute Basics im Umgang mit einem Linux. Der Paketmanager ist das Herz und Hirn der Software- und Update-Verwaltung. Ohne mindestens in den Grundzügen das Konzept verstanden zu haben wirst du dich auf ewig mit deiner Distribution schwer tun.

[Feuersturm]

@thomas-braun Wir können ja eine entsprechende Doku beilegen / verlinken