js-controller 4.0 jetzt im BETA/LATEST!
-
@diginix Die Datenbank arbeitet generisch - die weiss also nicht ob ein echter Redis auf der gegenseite ist oder nur der "iobroker DB Server" (der Redis simuliert). Und der Simulator tut einfach so als ob er die Sets Migration mitmacht ... Von daher ... ignorieren
-
@apollon77 ist mir gerade eingefallen, der redis Server läuft noch in meiner VM, da ich aber vor langer Zeit auf jsonl umgestellt habe, wird dieser doch nicht mehr benötigt, oder?
unter anderem bin ich soeben auf v4.0.102022-02-16 10:00:38.466 - info: telegram.0 (23965) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.463 - info: telegram.1 (23984) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.468 - info: web.0 (26298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.466 - info: text2command.0 (25980) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:39.190 - warn: sonoff.0 (24255) get state error: DB closed 2022-02-16 10:00:39.296 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed. 2022-02-16 10:00:39.324 - warn: sonoff.0 (24255) redis get sonoff.0.Kaffeeautomat.alive, error - Connection is closed. 2022-02-16 10:00:39.347 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed. 2022-02-16 10:00:39.511 - warn: sonoff.0 (24255) get state error: Connection is closed. 2022-02-16 10:00:39.814 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM 2022-02-16 10:00:40.460 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM 2022-02-16 10:00:45.897 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM 2022-02-16 10:00:45.962 - warn: host.IoBroker instance system.adapter.email.0 terminated due to SIGTERM 2022-02-16 10:00:46.139 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM 2022-02-16 10:00:46.313 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM 2022-02-16 10:00:46.314 - warn: host.IoBroker instance system.adapter.zigbee.0 terminated due to SIGTERM 2022-02-16 10:00:46.374 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM 2022-02-16 10:00:46.485 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM 2022-02-16 10:00:46.634 - warn: host.IoBroker instance system.adapter.echarts.0 terminated due to SIGTERM 2022-02-16 10:00:46.635 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM 2022-02-16 10:00:46.736 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM 2022-02-16 10:00:46.803 - 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: 2022-02-16 10:00:46.804 - error: host.IoBroker Caught by controller[0]: Error: DB closed 2022-02-16 10:00:46.805 - error: host.IoBroker Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-02-16 10:00:46.805 - error: host.IoBroker Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-02-16 10:00:46.806 - error: host.IoBroker Caught by controller[0]: at Object.onceWrapper (events.js:520:26) 2022-02-16 10:00:46.806 - error: host.IoBroker Caught by controller[0]: at Socket.emit (events.js:400:28) 2022-02-16 10:00:46.807 - error: host.IoBroker Caught by controller[0]: at Socket.emit (domain.js:475:12) 2022-02-16 10:00:46.807 - error: host.IoBroker Caught by controller[0]: at TCP. (net.js:686:12) 2022-02-16 10:00:46.808 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM 2022-02-16 10:00:46.977 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM 2022-02-16 10:00:46.978 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM 2022-02-16 10:00:47.077 - warn: host.IoBroker instance system.adapter.backitup.0 terminated due to SIGTERM 2022-02-16 10:00:47.182 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM 2022-02-16 10:00:47.332 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM 2022-02-16 10:00:47.334 - warn: host.IoBroker instance system.adapter.fully-tablet-control.0 terminated due to SIGTERM 2022-02-16 10:00:47.405 - warn: host.IoBroker instance system.adapter.info.0 terminated due to SIGTERM 2022-02-16 10:00:48.164 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM -
@crunchip Alaso der Fehler hier mit "DB Closed" liegt wohl eher daran das der sonoff Adapter noch Dinge abarbeitet obwohl er schon damit hätte aufhören sollen weil er gestoppt wird. Das ist ein Adapter-Issue wert.
Ob Du jetzt Redis oder jsonl hast musst Du wissen ... aber wenn da ein Redis ist der nicht genutzt wird dann sollte der zwar RAM brauchen aber sich sonst mega langweilen
-
ble-build
main.js auf
else if (/NODE_MODULE_VERSION/.test(err.message) && ((_a = adapter.supportsFeature) === null || _a === void 0 ? void 0 : _a.call(adapter, "CONTROLLER_NPM_AUTO_REBUILD"))) { console.error(err.message); terminate("A dependency requires a rebuild.", 13); }geändert. Rebuild schaut nun so aus:
2022-02-16 10:29:20.525 - info: ble.0 (133617) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10 2022-02-16 10:29:20.625 - info: ble.0 (133617) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default 2022-02-16 10:29:20.627 - info: ble.0 (133617) enabled plugins: _default 2022-02-16 10:29:20.629 - info: ble.0 (133617) monitored services: 2022-02-16 10:29:20.632 - info: ble.0 (133617) starting scanner process... 2022-02-16 10:29:21.052 - error: ble.0 (133617) Terminating because A dependency requires a rebuild. 2022-02-16 10:29:21.138 - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node' 2022-02-16 10:29:21.139 - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using 2022-02-16 10:29:21.139 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires 2022-02-16 10:29:21.140 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing 2022-02-16 10:29:21.140 - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). 2022-02-16 10:29:21.141 - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done. 2022-02-16 10:29:21.141 - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards. 2022-02-16 10:29:21.146 - info: host.chet system.adapter.ble.0 will be rebuilt 2022-02-16 10:29:21.148 - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt 2022-02-16 10:29:21.148 - info: host.chet iobroker rebuild 2022-02-16 10:29:22.218 - info: host.chet iobroker npm-rebuild: Rebuilding native modules ... 2022-02-16 10:31:07.465 - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully 2022-02-16 10:31:07.500 - info: host.chet iobroker npm-rebuild: 2022-02-16 10:31:07.502 - info: host.chet iobroker npm-rebuild: Rebuilding native modules done 2022-02-16 10:31:08.515 - info: host.chet iobroker npm-rebuild: exit 0 2022-02-16 10:31:08.770 - info: host.chet instance system.adapter.ble.0 started with pid 134847 2022-02-16 10:31:10.403 - info: ble.0 (134847) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10 2022-02-16 10:31:10.474 - info: ble.0 (134847) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default 2022-02-16 10:31:10.476 - info: ble.0 (134847) enabled plugins: _default 2022-02-16 10:31:10.478 - info: ble.0 (134847) monitored services: 2022-02-16 10:31:10.482 - info: ble.0 (134847) starting scanner process... 2022-02-16 10:31:10.929 - error: ble.0 (134847) Terminating because A dependency requires a rebuild. 2022-02-16 10:31:11.016 - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node' 2022-02-16 10:31:11.017 - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using 2022-02-16 10:31:11.017 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires 2022-02-16 10:31:11.018 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing 2022-02-16 10:31:11.018 - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). 2022-02-16 10:31:11.018 - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done. 2022-02-16 10:31:11.019 - info: host.chet Adapter system.adapter.ble.0 needs rebuild of @abandonware/bluetooth-hci-socket and will be restarted afterwards. 2022-02-16 10:31:11.020 - info: host.chet system.adapter.ble.0 will be rebuilt (Args: {"path":"/opt/iobroker/node_modules/@abandonware","module":"@abandonware/bluetooth-hci-socket","version":"0.5.3-8"}) 2022-02-16 10:31:11.020 - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 2 attempt 2022-02-16 10:31:11.021 - info: host.chet iobroker rebuild @abandonware/bluetooth-hci-socket@0.5.3-8 --path /opt/iobroker/node_modules/@abandonware 2022-02-16 10:31:12.014 - info: host.chet iobroker npm-rebuild: Rebuilding native module "@abandonware/bluetooth-hci-socket@0.5.3-8" in /opt/iobroker/node_modules/@abandonware ... 2022-02-16 10:31:22.338 - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully 2022-02-16 10:31:22.384 - info: host.chet iobroker npm-rebuild: 2022-02-16 10:31:22.385 - info: host.chet iobroker npm-rebuild: Rebuilding native modules done 2022-02-16 10:31:23.401 - info: host.chet iobroker npm-rebuild: exit 0 2022-02-16 10:31:23.561 - info: host.chet instance system.adapter.ble.0 started with pid 134906 2022-02-16 10:31:25.124 - info: ble.0 (134906) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10 2022-02-16 10:31:25.195 - info: ble.0 (134906) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default 2022-02-16 10:31:25.197 - info: ble.0 (134906) enabled plugins: _default 2022-02-16 10:31:25.199 - info: ble.0 (134906) monitored services: 2022-02-16 10:31:25.202 - info: ble.0 (134906) starting scanner process... 2022-02-16 10:31:25.641 - error: ble.0 (134906) Terminating because A dependency requires a rebuild. 2022-02-16 10:31:25.729 - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node' 2022-02-16 10:31:25.730 - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using 2022-02-16 10:31:25.730 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires 2022-02-16 10:31:25.730 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing 2022-02-16 10:31:25.730 - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). 2022-02-16 10:31:25.731 - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done. 2022-02-16 10:31:25.731 - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards. 2022-02-16 10:31:25.731 - info: host.chet system.adapter.ble.0 will be rebuilt 2022-02-16 10:31:25.732 - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt 2022-02-16 10:31:25.732 - info: host.chet iobroker rebuild 2022-02-16 10:31:26.713 - info: host.chet iobroker npm-rebuild: Rebuilding native modules ... 2022-02-16 10:33:07.966 - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully 2022-02-16 10:33:08.004 - info: host.chet iobroker npm-rebuild: 2022-02-16 10:33:08.005 - info: host.chet iobroker npm-rebuild: Rebuilding native modules done 2022-02-16 10:33:09.020 - info: host.chet iobroker npm-rebuild: exit 0 2022-02-16 10:33:09.190 - info: host.chet instance system.adapter.ble.0 started with pid 136127 2022-02-16 10:33:10.749 - info: ble.0 (136127) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10 2022-02-16 10:33:10.842 - info: ble.0 (136127) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default 2022-02-16 10:33:10.843 - info: ble.0 (136127) enabled plugins: _default 2022-02-16 10:33:10.845 - info: ble.0 (136127) monitored services: 2022-02-16 10:33:10.849 - info: ble.0 (136127) starting scanner process... 2022-02-16 10:33:11.293 - error: ble.0 (136127) Terminating because A dependency requires a rebuild. 2022-02-16 10:33:11.387 - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node' 2022-02-16 10:33:11.388 - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using 2022-02-16 10:33:11.388 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires 2022-02-16 10:33:11.389 - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing 2022-02-16 10:33:11.389 - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). 2022-02-16 10:33:11.389 - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done. 2022-02-16 10:33:11.389 - info: host.chet Rebuild for adapter system.adapter.ble.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually. -
@thomas-braun sagte in js-controller 4.0 jetzt im BETA/LATEST!:
2022-02-16 10:31:11.021 - info: host.chet iobroker rebuild @abandonware/bluetooth-hci-socket@0.5.3-8 --path /opt/iobroker/node_modules/@abandonware
Die zeile wollte ich sehen ... cooollll. Danke
-
@apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Ob Du jetzt Redis oder jsonl hast musst Du wissen
ich schrieb ja, ich verwende jsonl, deswegen verwirren die redis Meldungen etwas. Dachte vllt es hat in irgendeiner Weise Einfluss, wenn der Redis Server zusätzlich läuft.
ging eher um die error Meldungen vom Hostissue für sonoff kann ich erstellen,
für shelly werd ich wohl auch eins erstellen müssen, dieser wirft auch Fehler beim beenden.2022-02-16 10:00:38.419 - error: shelly.0 (24062) 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(). 2022-02-16 10:00:38.439 - info: virtualpowermeter.0 (26009) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.420 - error: shelly.0 (24062) unhandled promise rejection: DB closed 2022-02-16 10:00:38.441 - error: shelly.0 (24062) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at TCP. (net.js:686:12) 2022-02-16 10:00:38.442 - error: shelly.0 (24062) DB closed 2022-02-16 10:00:38.460 - info: zigbee.0 (24311) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.464 - info: echarts.0 (24809) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.466 - info: telegram.0 (23965) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.463 - info: telegram.1 (23984) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.468 - info: web.0 (26298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:38.466 - info: text2command.0 (25980) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 10:00:39.190 - warn: sonoff.0 (24255) get state error: DB closed 2022-02-16 10:00:39.296 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed. 2022-02-16 10:00:39.324 - warn: sonoff.0 (24255) redis get sonoff.0.Kaffeeautomat.alive, error - Connection is closed. 2022-02-16 10:00:39.347 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed. 2022-02-16 10:00:39.511 - warn: sonoff.0 (24255) get state error: Connection is closed. 2022-02-16 10:00:39.814 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM 2022-02-16 10:00:40.460 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM -
@crunchip Ja bitte issues wenn es keine gibt. Am Ende ist es so: Wir nutzen das Redis Protokoll zur Kommunikation mit der DB ... egal ob echter oder unserer eigenen DB ...
-
Nur mal so für mich als Windows Onkel zur eigenen Beruhigung - die Meldungen sind unkritisch?
Beim Update non der 3.3 auf 4.0.9hatte ich in der Konsole ja einen ganzen Sack voll (Fehler)Meldungen - siehe weiter oben.
Jetzt auf die 4.0.10 sind es andere Meldunugen. Da aber alles läuft, scheint das unkritisch zu sein? Das was im Code als REMOVE angegeben ist, kann ich auch gefahrlos löschen?
> iobroker.js-controller@4.0.10 install C:\iobroker\GLT\node_modules\iobroker.js-controller > node iobroker.js setup first Successfully migrated 22812 objects to Redis Sets object _design/system updated The following notifications happened during sync: - Ignoring Directory "heatingcontrol.admin" because officially not created as meta object. Please remove directory! - Ignoring Directory "ping.admin" because officially not created as meta object. Please remove directory! - Ignoring Directory "vis-test" because officially not created as meta object. Please remove directory! { "defaultPrivate": "-----BEGIN RSA PRIVATE KEY-----Viel Key Code hierzwischen-----END RSA PRIVATE KEY-----\r\n", "defaultPublic": "-----BEGIN CERTIFICATE-----VIEL Code hier zwischen-----END CERTIFICATE-----\r\n" } Update certificate defaultPrivate The object "system.certificates" was updated successfully. Update certificate defaultPublic The object "system.certificates" was updated successfully. + iobroker.js-controller@4.0.10 removed 6 packages, updated 23 packages and audited 2522 packages in 67.268s 182 packages are looking for funding run `npm fund` for details found 182 vulnerabilities (18 low, 82 moderate, 76 high, 6 critical) run `npm audit fix` to fix them, or `npm audit` for details -
@apollon77 wie im anderen Thread erwähnt, bleibt meine CPU nun auch oben
deshalb habe ich nun mal iob gestoppt und die ganze VM neu gestartet
diesmal kam der nut Adapter noch dazukommen die Host error aufgrund der "fehlerhaften" Adapter, oder durch etwas anderes?
2022-02-16 11:36:07.841 - info: javascript.0 (14587) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.103 - info: history.0 (14352) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.133 - info: web.0 (16885) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.135 - info: virtualpowermeter.0 (16562) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.135 - info: telegram.1 (14621) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.141 - info: telegram.0 (14602) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.140 - info: zigbee.0 (14934) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.139 - info: text2command.0 (16491) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.137 - info: echarts.0 (15248) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-16 11:36:08.175 - error: shelly.0 (11928) 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(). 2022-02-16 11:36:08.177 - warn: nut.0 (14949) get state error: Connection is closed. 2022-02-16 11:36:08.179 - error: nut.0 (14949) 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(). 2022-02-16 11:36:08.177 - error: shelly.0 (11928) unhandled promise rejection: DB closed 2022-02-16 11:36:08.191 - error: shelly.0 (11928) Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at TCP. (net.js:686:12) 2022-02-16 11:36:08.192 - error: shelly.0 (11928) DB closed 2022-02-16 11:36:08.181 - error: nut.0 (14949) unhandled promise rejection: DB closed 2022-02-16 11:36:08.448 - error: nut.0 (14949) Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40) at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6485:35) 2022-02-16 11:36:08.451 - error: nut.0 (14949) DB closed 2022-02-16 11:36:08.571 - warn: radar2.0 (15633) get state error: Connection is closed. 2022-02-16 11:36:08.576 - warn: radar2.0 (15633) Error {} is setState for Galaxy-S10Janina._nHere with {"val":51,"ack":true,"from":"system.adapter.radar2.0","user":"system.user.admin"} 2022-02-16 11:36:10.059 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM 2022-02-16 11:36:14.590 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM 2022-02-16 11:36:14.795 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM 2022-02-16 11:36:14.888 - warn: host.IoBroker instance system.adapter.email.0 terminated due to SIGTERM 2022-02-16 11:36:14.963 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM 2022-02-16 11:36:15.167 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM 2022-02-16 11:36:15.581 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM 2022-02-16 11:36:15.642 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM 2022-02-16 11:36:15.649 - warn: host.IoBroker instance system.adapter.javascript.0 terminated due to SIGTERM 2022-02-16 11:36:15.714 - warn: host.IoBroker instance system.adapter.zigbee.0 terminated due to SIGTERM 2022-02-16 11:36:15.805 - 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: 2022-02-16 11:36:15.806 - error: host.IoBroker Caught by controller[0]: Error: DB closed 2022-02-16 11:36:15.807 - error: host.IoBroker Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) 2022-02-16 11:36:15.807 - error: host.IoBroker Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2022-02-16 11:36:15.808 - error: host.IoBroker Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40) 2022-02-16 11:36:15.808 - error: host.IoBroker Caught by controller[0]: at Adapter.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:6485:35) 2022-02-16 11:36:15.809 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM 2022-02-16 11:36:15.870 - warn: host.IoBroker instance system.adapter.backitup.0 terminated due to SIGTERM 2022-02-16 11:36:15.960 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM 2022-02-16 11:36:16.019 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM 2022-02-16 11:36:16.118 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM 2022-02-16 11:36:16.281 - warn: host.IoBroker instance system.adapter.echarts.0 terminated due to SIGTERM 2022-02-16 11:36:16.282 - warn: host.IoBroker instance system.adapter.fully-tablet-control.0 terminated due to SIGTERM 2022-02-16 11:36:16.385 - warn: host.IoBroker instance system.adapter.info.0 terminated due to SIGTERM 2022-02-16 11:36:16.452 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM 2022-02-16 11:36:16.613 - warn: host.IoBroker instance system.adapter.linux-control.0 terminated due to SIGTERM 2022-02-16 11:36:16.718 - warn: host.IoBroker instance system.adapter.logparser.0 terminated due to SIGTERM 2022-02-16 11:36:16.818 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM 2022-02-16 11:36:16.928 - warn: host.IoBroker instance system.adapter.jarvis.0 terminated due to SIGTERM 2022-02-16 11:36:17.071 - warn: host.IoBroker instance system.adapter.radar2.0 terminated due to SIGTERM 2022-02-16 11:36:17.073 - warn: host.IoBroker instance system.adapter.seq.0 terminated due to SIGTERM 2022-02-16 11:36:17.151 - warn: host.IoBroker instance system.adapter.shuttercontrol.0 terminated due to SIGTERM 2022-02-16 11:36:17.212 - warn: host.IoBroker instance system.adapter.simple-api.0 terminated due to SIGTERM 2022-02-16 11:36:17.344 - warn: host.IoBroker instance system.adapter.smartcontrol.0 terminated due to SIGTERM 2022-02-16 11:36:17.345 - warn: host.IoBroker instance system.adapter.sourceanalytix.0 terminated due to SIGTERM 2022-02-16 11:36:17.425 - warn: host.IoBroker instance system.adapter.tankerkoenig.0 terminated due to SIGTERM 2022-02-16 11:36:17.493 - warn: host.IoBroker instance system.adapter.text2command.0 terminated due to SIGTERM 2022-02-16 11:36:17.570 - warn: host.IoBroker instance system.adapter.trashschedule.0 terminated due to SIGTERM 2022-02-16 11:36:17.660 - warn: host.IoBroker instance system.adapter.unifi.0 terminated due to SIGTERM 2022-02-16 11:36:17.716 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM 2022-02-16 11:36:17.807 - warn: host.IoBroker instance system.adapter.wled.0 terminated due to SIGTERM 2022-02-16 11:36:17.873 - warn: host.IoBroker instance system.adapter.yeelight-2.0 terminated due to SIGTERM 2022-02-16 11:36:18.591 - warn: host.IoBroker instance system.adapter.web.0 terminated due to SIGTERM 2022-02-16 11:36:18.876 - error: host.IoBroker Caught by controller[1]: 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: 2022-02-16 11:36:18.877 - error: host.IoBroker Caught by controller[1]: Error: DB closed 2022-02-16 11:36:18.878 - error: host.IoBroker Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) 2022-02-16 11:36:18.879 - error: host.IoBroker Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) 2022-02-16 11:36:18.879 - error: host.IoBroker Caught by controller[1]: at Object.onceWrapper (events.js:520:26) 2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at Socket.emit (events.js:400:28) 2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at Socket.emit (domain.js:475:12) 2022-02-16 11:36:18.880 - error: host.IoBroker Caught by controller[1]: at TCP. (net.js:686:12) 2022-02-16 11:36:18.881 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM 2022-02-16 11:36:19.226 - warn: host.IoBroker instance system.adapter.wiffi-wz.0 terminated due to SIGTERM 2022-02-16 11:36:19.272 - warn: host.IoBroker instance system.adapter.socketio.0 terminated due to SIGTERM 2022-02-16 11:38:26.219 - info: admin.0 (691) starting. Version 5.3.0 in /opt/iobroker/node_modules/iobroker.admin, node: v14.19.0, js-controller: 4.0.10 2022-02-16 11:38:26.255 - info: admin.0 (691) requesting all states 2022-02-16 11:38:26.257 - info: admin.0 (691) requesting all objects 2022-02-16 11:38:30.081 - info: admin.0 (691) received all objects 2022-02-16 11:38:30.835 - info: email.0 (706) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.email, node: v14.19.0, js-controller: 4.0.10 2022-02-16 11:38:30.944 - info: admin.0 (691) Request actual repository... 2022-02-16 11:38:30.957 - info: admin.0 (691) http server listening on port 8081js-controller hat sich aktuell wieder eingependelt, seit dem Neustart
-
@jb_sullivan sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Nur mal so für mich als Windows Onkel zur eigenen Beruhigung - die Meldungen sind unkritisch?
Sieht alles ok auch, trotz Windows gg (sorry den haste so gewollt ;-))
Beim Update non der 3.3 auf 4.0.9hatte ich in der Konsole ja einen ganzen Sack voll (Fehler)Meldungen - siehe weiter oben.
Ja die kommen nur wenn du von <4 auf 4 kommst. Sobald du auf 4 bist sind die weg.
Jetzt auf die 4.0.10 sind es andere Meldunugen. Da aber alles läuft, scheint das unkritisch zu sein? Das was im Code als REMOVE angegeben ist, kann ich auch gefahrlos löschen?
Zu denen gilt: Wenn du die adapter wo er "*.admin" anmeckert noch hast mach mal ein ´iob upload all´ bzw upload von den betroffnen Adaptern ... vis-test müsstest Du wissen obs Weg kann. Es ist ein Verzeichnis im ioBroker storage was das System nicht kennt (Passiert falls DU da mal was manuell hinkopiert hast)
-
@crunchip sagte in js-controller 4.0 jetzt im BETA/LATEST!:
kommen die Host error aufgrund der "fehlerhaften" Adapter, oder durch etwas anderes?
Die Fehler haben mit Viel-CPU-Problemen nichts zu tun!! Das ist ok so, wundert mich ... bzw da mal schauen das auch letzte Versionen installiert sind und ggf issues anlegen wenn ja.
-
Update auf 4.0.10 ist problemlos durchgelaufen!
Anschließend habe ich Node-JS von v14.19.0 auf v16.14.0 aktualisiert. Der iobroker ist auch danach mit allen Adaptern problemlos gestartet.
Mir wurde dann ein Update für den hm-rpc-Adapter angeboten. Beim Versuch diesen über den Info-Tab zu aktualisieren, habe ich folgende Fehlermeldungen erhalten:
host.iobroker 2022-02-16 15:38:47.365 info iobroker Update hm-rpc from @1.15.5 to @1.15.6 host.iobroker 2022-02-16 15:38:48.141 info iobroker NPM version: 8.3.1 Installing iobroker.hm-rpc@1.15.6... (System call) host.iobroker 2022-02-16 15:40:09.693 error iobroker Cannot upgrade: Cannot find view "system" host.iobroker 2022-02-16 15:40:09.689 error iobroker Cannot set system.adapter.hm-rpc: DB closed host.iobroker 2022-02-16 15:40:09.663 error iobroker host.iobroker Cannot install iobroker.hm-rpc@1.15.6: 254Ein weiterer Aktualisierungsversuch über die Admin-Seite hat dann aber ohne Fehler geklappt. War ich evtl. einfach zu ungeduldig?
Ansonsten keine Fehlermeldungen oder Auffälligkeiten.
Gruß Marco
-
@lonsimbt Ist Info aktuell? Es gab mal nen Bug ion info was Adapter-Updates anging ...
-
Ich denke schon. Die 1.9.18 wird mir als verfügbar und installiert angezeigt.
-
@lonsimbt Dann bitte nochmal schauen ob ein anderen update (vllt ja noch was offen) auch solche fehler gibt und dann issue bitte anlegen)
-
Ich habe testweise mal den tr-064-Adapter eine Versionsnummer zurückgesetzt und anschließend über die Info-Seite wieder auf den aktuellen Stand gebracht. Das hat problemlos funktioniert. Ich habe allerdings den Eindruck, dass die Updates recht lange benötigen.
Falls der Fehler an anderer Stelle nochmal auftritt, sage ich Bescheid und lege ein issue an.
-
@lonsimbt sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Ich habe allerdings den Eindruck, dass die Updates recht lange benötigen.
Denke da musst du npm fragen
-
Habe jetzt auch mal 4.0.10 installiert. System war uptodate
Node.js ist auch richtig/usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.0 v14.19.0 6.14.16Bekomme aber folgende Meldungen am Anfang
System startet dann auch und bei beim status kommt folgende Warnung. Kann ich das ignorieren?schlippe@ioBroker-Test:~$ iobroker status (node:15326) Warning: Accessing non-existent property 'count' of module exports inside circular dependency (Use `node --trace-warnings ...` to show where the warning was created) (node:15326) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency (node:15326) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency (node:15326) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency iobroker is running on this host. Objects type: jsonl States type: jsonl -
Ich habe eben nochmal ein Win10 Update gemacht und dann den Broker automatisch neu starten lassen. Dabei poppte die folgende Meldung auf - hatte ich in der Form noch nie und auch die Einstellung 60 Sekunden ließ sich nicht einstellen. Dabei kam die Meldung am unteren Bildrand.
Habe dann Abrechen gedrückt, da ich in der Form eigentlich noch nie Probleme hatte. Waren wohl noch ein paar andere Windows Prozesse im Hintergrund am starten, oder so.....
Das nur mal am Rande.
-
@apollon77
Edit: Sehe gerade im ersten Beitrag, dass die Errors gewollt / ok sind.Ich hab gerade einmal mein Produktivsystem von js-controller 3.3.22 auf 4.0.10 aktualisiert und folgende Ausgabe erhalten:
proxmox@ioBroker:~$ iob stop proxmox@ioBroker:~$ iob upgrade self Update js-controller from @3.3.22 to @4.0.10 NPM version: 6.14.15 npm install iobroker.js-controller@4.0.10 --loglevel error --unsafe-perm --prefi x "/opt/iobroker" (System call) In file included from ../src/unix_dgram.cc:5: ../../nan/nan.h: In function 'void Nan::AsyncQueueWorker(Nan::AsyncWorker*)': ../../nan/nan.h:2294:62: warning: cast between incompatible function types from 'void (*)(uv_work_t*)' {aka 'void (*)(uv_work_s*)'} to 'uv_after_work_cb' {aka ' void (*)(uv_work_s*, int)'} [-Wcast-function-type] 2294 | , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete) | ^ In file included from ../../nan/nan.h:56, from ../src/unix_dgram.cc:5: ../src/unix_dgram.cc: At global scope: /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787:43: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>)' to ' node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::V alue>, void*)'} [-Wcast-function-type] 787 | (node::addon_register_func) (regfunc), \ | ^ /home/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expan sion of macro 'NODE_MODULE_X' 821 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_ usage) | ^~~~~~~~~~~~~ ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE' 404 | NODE_MODULE(unix_dgram, Initialize) | ^~~~~~~~~~~ Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na mespace cfg.: Data=["meta.objects.features.useSets"] Server States 127.0.0.1:34856 Error from InMemDB: Error: GET-UNSUPPORTED for nam espace meta.: Data=["meta.states.protocolVersion"] Server Objects 127.0.0.1:59728 Error from InMemDB: Error: GET-UNSUPPORTED for na mespace cfg.: Data=["meta.objects.protocolVersion"] Server States 127.0.0.1:34858 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"] Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa d Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa d Server Objects 127.0.0.1:59728 Error from InMemDB: Error: Unknown LUA script loa d Server Objects 127.0.0.1:59728 Error from InMemDB: Error: SET-UNSUPPORTED for na mespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49] }] Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for names pace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}] proxmox@ioBroker:~$Nach dem Update ergibt iob status folgendes:
proxmox@ioBroker:~$ iob status iobroker is not running on this host. Objects type: jsonl States type: jsonlproxmox@ioBroker:~$ node -v && nodejs -v && npm -v v14.18.2 v14.18.2 6.14.15
