NEWS
Beta Test js-controller Kiera (v6.0)
Tester
331
Beiträge
39
Kommentatoren
84.8k
Aufrufe
42
Watching
-
@thomas-braun sagte in Beta Test js-controller Kiera (v6.0):
Eine Anzeige, das xxx Pakete veraltet sind und das Updates vorliegen mag ja noch sinnvoll sein, aber die Systempflege darf nicht über eine Smart Home Software erfolgen.
so eine Anzeige soll auch nicht nervig sein.. und richtig, Systempflege hat! nicht ueber eine Smart Home Software zu erfolgen.
So offtopic ist das hier auch garnicht, aber ich schlage das mal als Thema fuer das naechste DevMeeting vor..
Der iobroker darf eigentlich schon viel zu viel in dem System herumfuhrwerken, wenn das einem Security Audit unterzogen würde, der Auditor würde einen Herzinfarkt bekommen.
Edit: richtig, gerade, wenn noch andere Anwendungen auf dem gleichen Host laufen, und diese eine bestimmte Version von einem Package oder Nodejs brauchen..
-
Na ja
Wenn wir das Ziel haben ein System für 0815 User zu machen dann sollten wir nicht davon ausgehen dass die wissen wie man apt quellen pflegt. Och hätte auch keine Idee wie man node auf ne neuemajor aktualisiert ohne nod Update script. Dies wissen zu sollen fördert m.E. zu Recht die Aussagen ioBroker ist was für nerds.
In meinen Augen sollten updates so einfach wie möglich sein. Und da wir dank des tollen update scripts es eigentlich können sollten wir es auch anbieten. Oder uns nicht wundern dass User node 16 od älter verwenden bis es kracht
Ist m E. Halt die Frage ob ein System für nicht Linux admins oder ein System für Linux Kenner das Ziel ist.
Wird aber hier schon OT
Wenn du z. B. Reiter bist und dein Pferd mit einem Anhänger zu einem Turnier fährst, dann musst du z. B. auch schauen, das die Zugmaschine aufgetankt ist, den richtigen Reifendruck hat, der TÜV nicht abgelaufen ist und der Fahrer einen entsprechenden Führerschein für die ganze Fuhre besitzt.
Also musst du ein Auto-Nerd sein, um dein Pferd zu bewegen.
Der Anhänger oder gar das Pferd nimmt dir den ganzen Auto-technischen Kram nämlich auch nicht ab. -
Wenn du z. B. Reiter bist und dein Pferd mit einem Anhänger zu einem Turnier fährst, dann musst du z. B. auch schauen, das die Zugmaschine aufgetankt ist, den richtigen Reifendruck hat, der TÜV nicht abgelaufen ist und der Fahrer einen entsprechenden Führerschein für die ganze Fuhre besitzt.
Also musst du ein Auto-Nerd sein, um dein Pferd zu bewegen.
Der Anhänger oder gar das Pferd nimmt dir den ganzen Auto-technischen Kram nämlich auch nicht ab.@thomas-braun der vergleich stimmt mich mehr als gut!
pferdebesitzer, ehemaliger westernreiter und so weiter...:face_with_cowboy_hat: -
6.0.7 bringt mir folgenden Log, Iobroker startet nicht( iob fix hilft nicht):
2024-07-13 09:59:01.727 - info: host.iobroker iobroker.js-controller version 6.0.7 js-controller starting 2024-07-13 09:59:01.729 - info: host.iobroker Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-07-13 09:59:01.729 - info: host.iobroker hostname: iobroker, node: v20.15.1 2024-07-13 09:59:01.730 - info: host.iobroker ip addresses: 192.168.0.222 fe80::8c62:1cff:fe49:dd99 2024-07-13 09:59:01.779 - info: host.iobroker connected to Objects and States 2024-07-13 09:59:01.787 - info: host.iobroker added notifications configuration of host 2024-07-13 09:59:01.901 - info: host.iobroker 62 instances found 2024-07-13 09:59:01.919 - info: host.iobroker starting 51 instances 2024-07-13 09:59:02.046 - info: host.iobroker instance system.adapter.admin.0 in version "7.0.13" started with pid 2920 2024-07-13 09:59:02.053 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext" 2024-07-13 09:59:02.055 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent" 2024-07-13 09:59:02.056 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent" 2024-07-13 09:59:02.057 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext" 2024-07-13 09:59:02.058 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest" 2024-07-13 09:59:02.059 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest" 2024-07-13 09:59:02.060 - info: host.iobroker Some obsolete host states deleted. 2024-07-13 09:59:02.745 - error: admin.0 (2920) 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(). 2024-07-13 09:59:02.745 - error: admin.0 (2920) unhandled promise rejection: callback is not a function 2024-07-13 09:59:02.746 - error: admin.0 (2920) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:02.747 - error: admin.0 (2920) callback is not a function 2024-07-13 09:59:03.253 - warn: admin.0 (2920) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:03.783 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:03.783 - error: host.iobroker instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:03.783 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled 2024-07-13 09:59:06.013 - info: host.iobroker instance system.adapter.email.0 in version "1.3.1" started with pid 2935 2024-07-13 09:59:06.457 - error: email.0 (2935) 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(). 2024-07-13 09:59:06.458 - error: email.0 (2935) unhandled promise rejection: callback is not a function 2024-07-13 09:59:06.459 - error: email.0 (2935) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:06.459 - error: email.0 (2935) callback is not a function 2024-07-13 09:59:06.967 - warn: email.0 (2935) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:07.492 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:07.493 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:07.493 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:07.493 - error: host.iobroker instance system.adapter.email.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:07.493 - info: host.iobroker Restart adapter system.adapter.email.0 because enabled 2024-07-13 09:59:10.014 - info: host.iobroker instance system.adapter.javascript.0 in version "8.6.0" started with pid 2964 2024-07-13 09:59:10.732 - error: javascript.0 (2964) An error happened which is most likely from one of your scripts, but the originating script could not be detected. 2024-07-13 09:59:10.733 - error: javascript.0 (2964) Error: callback is not a function 2024-07-13 09:59:10.733 - error: javascript.0 (2964) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:14.009 - info: host.iobroker instance system.adapter.pushover.0 in version "3.0.6" started with pid 2979 2024-07-13 09:59:14.454 - error: pushover.0 (2979) 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(). 2024-07-13 09:59:14.455 - error: pushover.0 (2979) unhandled promise rejection: callback is not a function 2024-07-13 09:59:14.456 - error: pushover.0 (2979) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:14.456 - error: pushover.0 (2979) callback is not a function 2024-07-13 09:59:14.965 - warn: pushover.0 (2979) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:15.490 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:15.490 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:15.490 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:15.490 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:15.490 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2024-07-13 09:59:18.033 - info: host.iobroker instance system.adapter.pushover.1 in version "3.0.6" started with pid 2994 2024-07-13 09:59:18.473 - error: pushover.1 (2994) 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(). 2024-07-13 09:59:18.474 - error: pushover.1 (2994) unhandled promise rejection: callback is not a function 2024-07-13 09:59:18.476 - error: pushover.1 (2994) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:18.476 - error: pushover.1 (2994) callback is not a function 2024-07-13 09:59:18.984 - warn: pushover.1 (2994) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:19.509 - error: host.iobroker instance system.adapter.pushover.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:19.510 - info: host.iobroker Restart adapter system.adapter.pushover.1 because enabled 2024-07-13 09:59:22.012 - info: host.iobroker instance system.adapter.pushover.2 in version "3.0.6" started with pid 3009 2024-07-13 09:59:22.451 - error: pushover.2 (3009) 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(). 2024-07-13 09:59:22.452 - error: pushover.2 (3009) unhandled promise rejection: callback is not a function 2024-07-13 09:59:22.453 - error: pushover.2 (3009) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:22.454 - error: pushover.2 (3009) callback is not a function 2024-07-13 09:59:22.503 - info: pushover.2 (3009) starting. Version 3.0.6 in /opt/iobroker/node_modules/iobroker.pushover, node: v20.15.1, js-controller: 6.0.7 2024-07-13 09:59:22.960 - info: pushover.2 (3009) terminating 2024-07-13 09:59:22.961 - warn: pushover.2 (3009) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:23.487 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:23.487 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:23.487 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:23.487 - error: host.iobroker instance system.adapter.pushover.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:23.487 - info: host.iobroker Restart adapter system.adapter.pushover.2 because enabled 2024-07-13 09:59:26.012 - info: host.iobroker instance system.adapter.telegram.0 in version "3.7.1" started with pid 3024 2024-07-13 09:59:26.609 - error: telegram.0 (3024) 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(). 2024-07-13 09:59:26.610 - error: telegram.0 (3024) unhandled promise rejection: callback is not a function 2024-07-13 09:59:26.611 - error: telegram.0 (3024) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:26.612 - error: telegram.0 (3024) callback is not a function 2024-07-13 09:59:27.118 - warn: telegram.0 (3024) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:27.645 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:27.645 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:27.645 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:27.645 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:27.645 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-07-13 09:59:28.745 - info: host.iobroker instance system.adapter.telegram.0 in version "3.7.1" started with pid 3039 2024-07-13 09:59:29.351 - error: telegram.0 (3039) 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(). 2024-07-13 09:59:29.351 - error: telegram.0 (3039) unhandled promise rejection: callback is not a function 2024-07-13 09:59:29.353 - error: telegram.0 (3039) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:29.353 - error: telegram.0 (3039) callback is not a function 2024-07-13 09:59:29.861 - warn: telegram.0 (3039) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:29.999 - info: host.iobroker instance system.adapter.telegram.1 in version "3.7.1" started with pid 3054 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:30.391 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:30.391 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-07-13 09:59:30.593 - error: telegram.1 (3054) 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(). 2024-07-13 09:59:30.593 - error: telegram.1 (3054) unhandled promise rejection: callback is not a function 2024-07-13 09:59:30.595 - error: telegram.1 (3054) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:30.595 - error: telegram.1 (3054) callback is not a function 2024-07-13 09:59:31.103 - warn: telegram.1 (3054) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:31.500 - info: host.iobroker instance system.adapter.telegram.0 in version "3.7.1" started with pid 3069 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:31.632 - error: host.iobroker instance system.adapter.telegram.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:31.632 - info: host.iobroker Restart adapter system.adapter.telegram.1 because enabled 2024-07-13 09:59:32.136 - error: telegram.0 (3069) 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(). 2024-07-13 09:59:32.136 - error: telegram.0 (3069) unhandled promise rejection: callback is not a function 2024-07-13 09:59:32.138 - error: telegram.0 (3069) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:32.138 - error: telegram.0 (3069) callback is not a function 2024-07-13 09:59:32.645 - warn: telegram.0 (3069) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:32.721 - info: host.iobroker instance system.adapter.telegram.1 in version "3.7.1" started with pid 3084 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:33.173 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:33.173 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-07-13 09:59:33.173 - warn: host.iobroker Do not restart adapter system.adapter.telegram.0 because restart loop detected 2024-07-13 09:59:33.321 - error: telegram.1 (3084) 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(). 2024-07-13 09:59:33.321 - error: telegram.1 (3084) unhandled promise rejection: callback is not a function 2024-07-13 09:59:33.323 - error: telegram.1 (3084) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:33.323 - error: telegram.1 (3084) callback is not a function 2024-07-13 09:59:33.831 - warn: telegram.1 (3084) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:33.874 - info: host.iobroker instance system.adapter.admin.0 in version "7.0.13" started with pid 3099 2024-07-13 09:59:34.004 - info: host.iobroker instance system.adapter.telegram.2 in version "3.7.1" started with pid 3106 2024-07-13 09:59:34.362 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:34.362 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a functionMit proxmox Backup wieder zurück auf 6.0.6
https://github.com/ioBroker/ioBroker.js-controller/issues/2837
-
6.0.7 bringt mir folgenden Log, Iobroker startet nicht( iob fix hilft nicht):
2024-07-13 09:59:01.727 - info: host.iobroker iobroker.js-controller version 6.0.7 js-controller starting 2024-07-13 09:59:01.729 - info: host.iobroker Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-07-13 09:59:01.729 - info: host.iobroker hostname: iobroker, node: v20.15.1 2024-07-13 09:59:01.730 - info: host.iobroker ip addresses: 192.168.0.222 fe80::8c62:1cff:fe49:dd99 2024-07-13 09:59:01.779 - info: host.iobroker connected to Objects and States 2024-07-13 09:59:01.787 - info: host.iobroker added notifications configuration of host 2024-07-13 09:59:01.901 - info: host.iobroker 62 instances found 2024-07-13 09:59:01.919 - info: host.iobroker starting 51 instances 2024-07-13 09:59:02.046 - info: host.iobroker instance system.adapter.admin.0 in version "7.0.13" started with pid 2920 2024-07-13 09:59:02.053 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext" 2024-07-13 09:59:02.055 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent" 2024-07-13 09:59:02.056 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent" 2024-07-13 09:59:02.057 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext" 2024-07-13 09:59:02.058 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest" 2024-07-13 09:59:02.059 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest" 2024-07-13 09:59:02.060 - info: host.iobroker Some obsolete host states deleted. 2024-07-13 09:59:02.745 - error: admin.0 (2920) 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(). 2024-07-13 09:59:02.745 - error: admin.0 (2920) unhandled promise rejection: callback is not a function 2024-07-13 09:59:02.746 - error: admin.0 (2920) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:02.747 - error: admin.0 (2920) callback is not a function 2024-07-13 09:59:03.253 - warn: admin.0 (2920) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:03.782 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:03.783 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:03.783 - error: host.iobroker instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:03.783 - info: host.iobroker Restart adapter system.adapter.admin.0 because enabled 2024-07-13 09:59:06.013 - info: host.iobroker instance system.adapter.email.0 in version "1.3.1" started with pid 2935 2024-07-13 09:59:06.457 - error: email.0 (2935) 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(). 2024-07-13 09:59:06.458 - error: email.0 (2935) unhandled promise rejection: callback is not a function 2024-07-13 09:59:06.459 - error: email.0 (2935) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:06.459 - error: email.0 (2935) callback is not a function 2024-07-13 09:59:06.967 - warn: email.0 (2935) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:07.492 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:07.493 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:07.493 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:07.493 - error: host.iobroker instance system.adapter.email.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:07.493 - info: host.iobroker Restart adapter system.adapter.email.0 because enabled 2024-07-13 09:59:10.014 - info: host.iobroker instance system.adapter.javascript.0 in version "8.6.0" started with pid 2964 2024-07-13 09:59:10.732 - error: javascript.0 (2964) An error happened which is most likely from one of your scripts, but the originating script could not be detected. 2024-07-13 09:59:10.733 - error: javascript.0 (2964) Error: callback is not a function 2024-07-13 09:59:10.733 - error: javascript.0 (2964) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:14.009 - info: host.iobroker instance system.adapter.pushover.0 in version "3.0.6" started with pid 2979 2024-07-13 09:59:14.454 - error: pushover.0 (2979) 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(). 2024-07-13 09:59:14.455 - error: pushover.0 (2979) unhandled promise rejection: callback is not a function 2024-07-13 09:59:14.456 - error: pushover.0 (2979) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:14.456 - error: pushover.0 (2979) callback is not a function 2024-07-13 09:59:14.965 - warn: pushover.0 (2979) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:15.490 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:15.490 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:15.490 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:15.490 - error: host.iobroker instance system.adapter.pushover.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:15.490 - info: host.iobroker Restart adapter system.adapter.pushover.0 because enabled 2024-07-13 09:59:18.033 - info: host.iobroker instance system.adapter.pushover.1 in version "3.0.6" started with pid 2994 2024-07-13 09:59:18.473 - error: pushover.1 (2994) 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(). 2024-07-13 09:59:18.474 - error: pushover.1 (2994) unhandled promise rejection: callback is not a function 2024-07-13 09:59:18.476 - error: pushover.1 (2994) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:18.476 - error: pushover.1 (2994) callback is not a function 2024-07-13 09:59:18.984 - warn: pushover.1 (2994) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:19.509 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:19.509 - error: host.iobroker instance system.adapter.pushover.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:19.510 - info: host.iobroker Restart adapter system.adapter.pushover.1 because enabled 2024-07-13 09:59:22.012 - info: host.iobroker instance system.adapter.pushover.2 in version "3.0.6" started with pid 3009 2024-07-13 09:59:22.451 - error: pushover.2 (3009) 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(). 2024-07-13 09:59:22.452 - error: pushover.2 (3009) unhandled promise rejection: callback is not a function 2024-07-13 09:59:22.453 - error: pushover.2 (3009) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:22.454 - error: pushover.2 (3009) callback is not a function 2024-07-13 09:59:22.503 - info: pushover.2 (3009) starting. Version 3.0.6 in /opt/iobroker/node_modules/iobroker.pushover, node: v20.15.1, js-controller: 6.0.7 2024-07-13 09:59:22.960 - info: pushover.2 (3009) terminating 2024-07-13 09:59:22.961 - warn: pushover.2 (3009) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:23.487 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:23.487 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:23.487 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:23.487 - error: host.iobroker instance system.adapter.pushover.2 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:23.487 - info: host.iobroker Restart adapter system.adapter.pushover.2 because enabled 2024-07-13 09:59:26.012 - info: host.iobroker instance system.adapter.telegram.0 in version "3.7.1" started with pid 3024 2024-07-13 09:59:26.609 - error: telegram.0 (3024) 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(). 2024-07-13 09:59:26.610 - error: telegram.0 (3024) unhandled promise rejection: callback is not a function 2024-07-13 09:59:26.611 - error: telegram.0 (3024) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:26.612 - error: telegram.0 (3024) callback is not a function 2024-07-13 09:59:27.118 - warn: telegram.0 (3024) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:27.645 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:27.645 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:27.645 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:27.645 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:27.645 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-07-13 09:59:28.745 - info: host.iobroker instance system.adapter.telegram.0 in version "3.7.1" started with pid 3039 2024-07-13 09:59:29.351 - error: telegram.0 (3039) 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(). 2024-07-13 09:59:29.351 - error: telegram.0 (3039) unhandled promise rejection: callback is not a function 2024-07-13 09:59:29.353 - error: telegram.0 (3039) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:29.353 - error: telegram.0 (3039) callback is not a function 2024-07-13 09:59:29.861 - warn: telegram.0 (3039) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:29.999 - info: host.iobroker instance system.adapter.telegram.1 in version "3.7.1" started with pid 3054 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:30.391 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:30.391 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:30.391 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-07-13 09:59:30.593 - error: telegram.1 (3054) 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(). 2024-07-13 09:59:30.593 - error: telegram.1 (3054) unhandled promise rejection: callback is not a function 2024-07-13 09:59:30.595 - error: telegram.1 (3054) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:30.595 - error: telegram.1 (3054) callback is not a function 2024-07-13 09:59:31.103 - warn: telegram.1 (3054) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:31.500 - info: host.iobroker instance system.adapter.telegram.0 in version "3.7.1" started with pid 3069 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:31.632 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:31.632 - error: host.iobroker instance system.adapter.telegram.1 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:31.632 - info: host.iobroker Restart adapter system.adapter.telegram.1 because enabled 2024-07-13 09:59:32.136 - error: telegram.0 (3069) 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(). 2024-07-13 09:59:32.136 - error: telegram.0 (3069) unhandled promise rejection: callback is not a function 2024-07-13 09:59:32.138 - error: telegram.0 (3069) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:32.138 - error: telegram.0 (3069) callback is not a function 2024-07-13 09:59:32.645 - warn: telegram.0 (3069) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:32.721 - info: host.iobroker instance system.adapter.telegram.1 in version "3.7.1" started with pid 3084 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a function 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: at runNextTicks (node:internal/process/task_queues:60:5) 2024-07-13 09:59:33.172 - error: host.iobroker Caught by controller[1]: at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:33.173 - error: host.iobroker instance system.adapter.telegram.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2024-07-13 09:59:33.173 - info: host.iobroker Restart adapter system.adapter.telegram.0 because enabled 2024-07-13 09:59:33.173 - warn: host.iobroker Do not restart adapter system.adapter.telegram.0 because restart loop detected 2024-07-13 09:59:33.321 - error: telegram.1 (3084) 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(). 2024-07-13 09:59:33.321 - error: telegram.1 (3084) unhandled promise rejection: callback is not a function 2024-07-13 09:59:33.323 - error: telegram.1 (3084) TypeError: callback is not a function at /opt/iobroker/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:449:9) 2024-07-13 09:59:33.323 - error: telegram.1 (3084) callback is not a function 2024-07-13 09:59:33.831 - warn: telegram.1 (3084) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-07-13 09:59:33.874 - info: host.iobroker instance system.adapter.admin.0 in version "7.0.13" started with pid 3099 2024-07-13 09:59:34.004 - info: host.iobroker instance system.adapter.telegram.2 in version "3.7.1" started with pid 3106 2024-07-13 09:59:34.362 - error: host.iobroker Caught by controller[0]: 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(). The promise rejected with the reason: 2024-07-13 09:59:34.362 - error: host.iobroker Caught by controller[1]: TypeError: callback is not a functionMit proxmox Backup wieder zurück auf 6.0.6
https://github.com/ioBroker/ioBroker.js-controller/issues/2837
@shadowhunter23 Bei mir das gleiche verhalten, bin auch wieder auf Version 6.0.6 zurück.
-
Unter js-controller 6.0.6 werden mir vom hs100 Adapter restart Loops gemeldet und der Adapter deaktiviert.
-
@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@uwerlp said in Beta Test js-controller Kiera (v6.0):
@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.
Da es sich dabei nicht um ein Problem des aktuellen Beta-Tests handelt, geht es damit hier weiter:
https://forum.iobroker.net/post/1180037 -
@shadowhunter23 Bei mir das gleiche verhalten, bin auch wieder auf Version 6.0.6 zurück.
@knoddel
6.0.8 funktioniert wieder. -
Aktualisierung von 6.0.6 auf 6.0.8 auf meinem Master Slave Testsystem ist im Log beim herunterfahren und vor dem Update dieser Error im Log
2024-07-13 18:32:03.964 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: DB closed 2024-07-13 18:32:03.969 - error: host.ioBrokerTestsystem Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2024-07-13 18:32:03.972 - error: host.ioBrokerTestsystem Caught by controller[0]: at Redis.setex (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2024-07-13 18:32:03.976 - 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-13 18:32:03.981 - 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-13 18:32:03.985 - 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-13 18:32:03.989 - 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-13 18:32:03.993 - error: host.ioBrokerTestsystem Caught by controller[0]: at Session.save (/opt/iobroker/node_modules/express-session/session/session.js:72:25) 2024-07-13 18:32:03.995 - error: host.ioBrokerTestsystem Caught by controller[0]: at Session.save (/opt/iobroker/node_modules/express-session/index.js:414:15) 2024-07-13 18:32:03.998 - error: host.ioBrokerTestsystem Caught by controller[0]: at ServerResponse.end (/opt/iobroker/node_modules/express-session/index.js:343:21) 2024-07-13 18:32:04.001 - error: host.ioBrokerTestsystem Caught by controller[0]: at ServerResponse.send (/opt/iobroker/node_modules/express/lib/response.js:233:10)größeres Log:
Das System ist aber ohne Probleme gestartet.
Slave lies sich ohne Probleme aktualisieren. -
Aktualisierung von 6.0.6 auf 6.0.8 auf meinem Master Slave Testsystem ist im Log beim herunterfahren und vor dem Update dieser Error im Log
2024-07-13 18:32:03.964 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: DB closed 2024-07-13 18:32:03.969 - error: host.ioBrokerTestsystem Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2024-07-13 18:32:03.972 - error: host.ioBrokerTestsystem Caught by controller[0]: at Redis.setex (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2024-07-13 18:32:03.976 - 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-13 18:32:03.981 - 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-13 18:32:03.985 - 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-13 18:32:03.989 - 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-13 18:32:03.993 - error: host.ioBrokerTestsystem Caught by controller[0]: at Session.save (/opt/iobroker/node_modules/express-session/session/session.js:72:25) 2024-07-13 18:32:03.995 - error: host.ioBrokerTestsystem Caught by controller[0]: at Session.save (/opt/iobroker/node_modules/express-session/index.js:414:15) 2024-07-13 18:32:03.998 - error: host.ioBrokerTestsystem Caught by controller[0]: at ServerResponse.end (/opt/iobroker/node_modules/express-session/index.js:343:21) 2024-07-13 18:32:04.001 - error: host.ioBrokerTestsystem Caught by controller[0]: at ServerResponse.send (/opt/iobroker/node_modules/express/lib/response.js:233:10)größeres Log:
Das System ist aber ohne Probleme gestartet.
Slave lies sich ohne Probleme aktualisieren.Beim Update auf Windows wird mir folgendes im admin UI angezeigt
'see changelog' ist m.E. wenig hilfreich für den 0815 User der ev. gar nicht weiß wo auf Github er diese Datei finden kann. Optimaler Weise sollte dort ein klickbarer Link stehen, minimal eine textuale url zum Kopieren in den Browser.
Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
Support Repositoryverwaltung.Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker
-
Beim Update auf Windows wird mir folgendes im admin UI angezeigt
'see changelog' ist m.E. wenig hilfreich für den 0815 User der ev. gar nicht weiß wo auf Github er diese Datei finden kann. Optimaler Weise sollte dort ein klickbarer Link stehen, minimal eine textuale url zum Kopieren in den Browser.
@mcm1957 und Admin ist in Version? https://github.com/ioBroker/ioBroker.admin?tab=readme-ov-file#7011-2024-07-03
Hier könnt ihr mich unterstützen.
-
Beim Update auf Windows wird mir folgendes im admin UI angezeigt
'see changelog' ist m.E. wenig hilfreich für den 0815 User der ev. gar nicht weiß wo auf Github er diese Datei finden kann. Optimaler Weise sollte dort ein klickbarer Link stehen, minimal eine textuale url zum Kopieren in den Browser.
-
@mcm1957 und Admin ist in Version? https://github.com/ioBroker/ioBroker.admin?tab=readme-ov-file#7011-2024-07-03
@foxriver76 said in Beta Test js-controller Kiera (v6.0):
@mcm1957 und Admin ist in Version? https://github.com/ioBroker/ioBroker.admin?tab=readme-ov-file#7011-2024-07-03
Nö - war noch admin 6
Mit admin 7 siehts gut aus:
Nachtrag:
Abgesehen von "Aktualisiseren "null" auf 6.0.8 ...
Admin Issue? Oder ... ? -
Hi, beim aktuellen Update vom js-controller erhalte ich folgende Fehlermeldung:
Update js-controller from @6.0.7 to @6.0.8 Stopped Objects DB Stopped States DB NPM version: 10.7.0 Installing iobroker.js-controller@6.0.8... (System call) npm error code 6 npm error path /opt/iobroker/node_modules/iobroker.js-controller npm error command failed npm error command sh -c node iobroker.js setup first npm error Uncaught Rejection: TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error 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(). The promise rejected with the reason: npm error TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-07-17T15_07_38_698Z-debug-0.log host.iob10 Cannot install iobroker.js-controller@6.0.8: 6- Adaptername: iobroker.js-controller
- Link zu Adapterrepository: www.github.com...
- Adapterversion: 6.0.8
- js-controller Version: 6.0.7
- Admin Version: 7.0.17
- Hardwaresystem: lxc with PROXMOX on NUC
- Arbeitsspeicher: 32GB
- Festplattenart: SSD
- Betriebssystem: Debian
- Nodejs-Version: 20.15.1
- NPM-Version: 10.7.0
- Installationsart: Skript und Manuell
- Image, Docker genutzt: Nein
- Ort, Name der Imagedatei: ...
Linux User bitte hier den Output von iob diag einfügen.
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iob10 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.8.8-2-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 0 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v20.15.1 /usr/bin/node v20.15.1 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.1 Recommended versions are nodejs 20.15.1 and npm 10.7.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.2G 1.9G 310M 163K 1.1G 1.4G Swap: 0B 0B 0B Total: 3.2G 1.9G 310M Active iob-Instances: 37 Upgrade policy: none ioBroker Core: js-controller 6.0.7 admin 7.0.17 ioBroker Status: iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : iob - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : iob10 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 13975 States: 10431 Size of iob-Database: 5.8M /opt/iobroker/iobroker-data/objects.json.bak 5.8M /opt/iobroker/iobroker-data/objects.json 1.4M /opt/iobroker/iobroker-data/states.json.bak 1.4M /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ==================== -
Hi, beim aktuellen Update vom js-controller erhalte ich folgende Fehlermeldung:
Update js-controller from @6.0.7 to @6.0.8 Stopped Objects DB Stopped States DB NPM version: 10.7.0 Installing iobroker.js-controller@6.0.8... (System call) npm error code 6 npm error path /opt/iobroker/node_modules/iobroker.js-controller npm error command failed npm error command sh -c node iobroker.js setup first npm error Uncaught Rejection: TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error 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(). The promise rejected with the reason: npm error TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-07-17T15_07_38_698Z-debug-0.log host.iob10 Cannot install iobroker.js-controller@6.0.8: 6- Adaptername: iobroker.js-controller
- Link zu Adapterrepository: www.github.com...
- Adapterversion: 6.0.8
- js-controller Version: 6.0.7
- Admin Version: 7.0.17
- Hardwaresystem: lxc with PROXMOX on NUC
- Arbeitsspeicher: 32GB
- Festplattenart: SSD
- Betriebssystem: Debian
- Nodejs-Version: 20.15.1
- NPM-Version: 10.7.0
- Installationsart: Skript und Manuell
- Image, Docker genutzt: Nein
- Ort, Name der Imagedatei: ...
Linux User bitte hier den Output von iob diag einfügen.
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iob10 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.8.8-2-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 0 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v20.15.1 /usr/bin/node v20.15.1 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.1 Recommended versions are nodejs 20.15.1 and npm 10.7.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.2G 1.9G 310M 163K 1.1G 1.4G Swap: 0B 0B 0B Total: 3.2G 1.9G 310M Active iob-Instances: 37 Upgrade policy: none ioBroker Core: js-controller 6.0.7 admin 7.0.17 ioBroker Status: iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : iob - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : iob10 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 13975 States: 10431 Size of iob-Database: 5.8M /opt/iobroker/iobroker-data/objects.json.bak 5.8M /opt/iobroker/iobroker-data/objects.json 1.4M /opt/iobroker/iobroker-data/states.json.bak 1.4M /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ====================@gui sagte in Fehler bei Update js-controller 6.0.7 auf 6.0.8:
den Output von iob diag einfügen
die Langfassung wäre hier jetzt sinnvoller.
@gui sagte in Fehler bei Update js-controller 6.0.7 auf 6.0.8:
Admin Version: 7.0.17
sonst noch mehr Beta-Versionen?
@gui sagte in Fehler bei Update js-controller 6.0.7 auf 6.0.8:
beim aktuellen Update vom js-controller
wie durchgeführt?
und aktuell ist ebenfalls relativ
auch das ist Beta!
-
Hi, beim aktuellen Update vom js-controller erhalte ich folgende Fehlermeldung:
Update js-controller from @6.0.7 to @6.0.8 Stopped Objects DB Stopped States DB NPM version: 10.7.0 Installing iobroker.js-controller@6.0.8... (System call) npm error code 6 npm error path /opt/iobroker/node_modules/iobroker.js-controller npm error command failed npm error command sh -c node iobroker.js setup first npm error Uncaught Rejection: TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error 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(). The promise rejected with the reason: npm error TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-07-17T15_07_38_698Z-debug-0.log host.iob10 Cannot install iobroker.js-controller@6.0.8: 6- Adaptername: iobroker.js-controller
- Link zu Adapterrepository: www.github.com...
- Adapterversion: 6.0.8
- js-controller Version: 6.0.7
- Admin Version: 7.0.17
- Hardwaresystem: lxc with PROXMOX on NUC
- Arbeitsspeicher: 32GB
- Festplattenart: SSD
- Betriebssystem: Debian
- Nodejs-Version: 20.15.1
- NPM-Version: 10.7.0
- Installationsart: Skript und Manuell
- Image, Docker genutzt: Nein
- Ort, Name der Imagedatei: ...
Linux User bitte hier den Output von iob diag einfügen.
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iob10 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.8.8-2-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 0 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v20.15.1 /usr/bin/node v20.15.1 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.1 Recommended versions are nodejs 20.15.1 and npm 10.7.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.2G 1.9G 310M 163K 1.1G 1.4G Swap: 0B 0B 0B Total: 3.2G 1.9G 310M Active iob-Instances: 37 Upgrade policy: none ioBroker Core: js-controller 6.0.7 admin 7.0.17 ioBroker Status: iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : iob - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : iob10 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 13975 States: 10431 Size of iob-Database: 5.8M /opt/iobroker/iobroker-data/objects.json.bak 5.8M /opt/iobroker/iobroker-data/objects.json 1.4M /opt/iobroker/iobroker-data/states.json.bak 1.4M /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ====================@gui ich hab das mal zum Betatester Thread hinzugefügt
-
@foxriver76 js-controller 6.0.9 lies sich ohne Probleme auf meinen Testsystemen installieren und es gibt keine Auffälligkeiten
-
Hi, beim aktuellen Update vom js-controller erhalte ich folgende Fehlermeldung:
Update js-controller from @6.0.7 to @6.0.8 Stopped Objects DB Stopped States DB NPM version: 10.7.0 Installing iobroker.js-controller@6.0.8... (System call) npm error code 6 npm error path /opt/iobroker/node_modules/iobroker.js-controller npm error command failed npm error command sh -c node iobroker.js setup first npm error Uncaught Rejection: TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error 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(). The promise rejected with the reason: npm error TypeError: callback is not a function npm error at /opt/iobroker/node_modules/iobroker.js-controller/node_modules/@iobroker/plugin-base/lib/PluginBase.js:310:17 npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-07-17T15_07_38_698Z-debug-0.log host.iob10 Cannot install iobroker.js-controller@6.0.8: 6- Adaptername: iobroker.js-controller
- Link zu Adapterrepository: www.github.com...
- Adapterversion: 6.0.8
- js-controller Version: 6.0.7
- Admin Version: 7.0.17
- Hardwaresystem: lxc with PROXMOX on NUC
- Arbeitsspeicher: 32GB
- Festplattenart: SSD
- Betriebssystem: Debian
- Nodejs-Version: 20.15.1
- NPM-Version: 10.7.0
- Installationsart: Skript und Manuell
- Image, Docker genutzt: Nein
- Ort, Name der Imagedatei: ...
Linux User bitte hier den Output von iob diag einfügen.
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iob10 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.8.8-2-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 0 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v20.15.1 /usr/bin/node v20.15.1 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.1 Recommended versions are nodejs 20.15.1 and npm 10.7.0 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.2G 1.9G 310M 163K 1.1G 1.4G Swap: 0B 0B 0B Total: 3.2G 1.9G 310M Active iob-Instances: 37 Upgrade policy: none ioBroker Core: js-controller 6.0.7 admin 7.0.17 ioBroker Status: iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : iob - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.admin.1 : admin : iob10 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iob - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 13975 States: 10431 Size of iob-Database: 5.8M /opt/iobroker/iobroker-data/objects.json.bak 5.8M /opt/iobroker/iobroker-data/objects.json 1.4M /opt/iobroker/iobroker-data/states.json.bak 1.4M /opt/iobroker/iobroker-data/states.json =================== END OF SUMMARY ====================Bitte NICHT als root im LXC herumturnen.
-
Bitte NICHT als root im LXC herumturnen.
Hi @thomas-braun, ich werde das mal nicht weiter kommentieren, und nehme einfach an, dass es ein allgemeiner guter Ratschlag war.
Ich habe es als erstes über die Weboberfläche gemacht, mit dem selben Ergebnis, und die läuft nicht unter root.
Support us
745
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge