js-controller 4.0 jetzt im BETA/LATEST!
-
@apollon77 Nur die eingehenden Events schnellen hoch. Das obere Diagramm mit >200 in Events war bei dem Update
Das untere Diagramm ist von heute morgen wo eigentlich keine Aktivitäten waren.
Loglevel ist auf info umgestellt. -
@diginix Wirklich "inputCount"?
-
@apollon77 Ja, system.host.iobroker.inputCount geht von normal ca 40 auf >200
Die Entprellzeit für die Erfassung war sogar 5000 ms. Habe nun mal 1000 eingestellt, falls es mal in unter 5 Sek hochschnellt, bekäme man es sonst gar nicht mit.
Nun würde mich ja mal brennend interessieren woher die inEvents kommen (können)?
-
@diginix sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Nun würde mich ja mal brennend interessieren woher die inEvents kommen (können)?
Magst du vielleicht noch die inputs/outputs für die bekannterweise etwas gesprächigeren Adapter aktivieren?
d.h. Javascript, Shelly (?), Influxdb, mihome-vacuum?mihome-vacuum hab ich zur Sicherheit mit drin, weil der es bei mir auch mal geschafft hat mit tausenden Logs meinen Pi zum Absturz zu bringen.
-
@diginix Ja ich denke es ist nicht direkt"diese Events" weil das sind viel zu wenige. Und die Zahl sagt auch nur das bei den (recht wenigen) States die der Controller selbst als Updates bekommt es mehr wurde ... Was nebenher ggf noch in der DB pot los ist ist damit nicht sichtbar.
Aber generell ists komisch, prüfe nochmal deine skripte ob davon ggf welche "spammen" könnten ... und ja die Idee mehr Adapterprozesse (alle?) mitzuloggen ist auch gut.
Setz nur das Reporting Interval nicht zu weit runter ...
-
@apollon77 Allein der iobroker Neustart wegen Loglevel Umstellung hat 10 Uhr auch wieder diese Anomalie:
Somit müsste es sich doch eigentlich auch bei euch mit meinen Dateien nachstellen lassen? Hat es ja aber anscheinend nicht.
-
@diginix Naja dann müsste man es mal schaffen es komplett nachzustellen - aber auch das tat ja bei dir letztens nicht ... Weil wenn du es nachstellen könntest dann wäre ne Idee mal unterschiedliche Adapter zu deaktivieren um zu schauen ob es passiert wenn mit denen was ist und und und
-
@apollon77 Für den Javascript Adapter hatte ich in/out Events schon mit in der history habe nun noch influx, shelly, mihome-vacuum dazu genommen.
Zumindest gibt es bei in/out beim javascript Adapter zeitliche Zusammenhänge:
Die Spitzen alle 15min muss ich noch prüfen. Da läuft mind. 1 Cron in einem Skript, aber warum da dann >3000 Events fliegen, verstehe ich gerade noch nicht. Habe den einzigen 15min Cron den ich finden konnte mal auskommentiert. Bin gespannt ob die Spitzen dann weg sind.
Ganz rechts sieht man auch noch eine "out" Spitze vom Skript Adapter mit >260 kurz nachdem alle Skripte wieder liefen nach iobroker restart.
-
@apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:
@moko Also nein kann damit nichts zu tun haben ... und ja Backitup 2.3.3 ist noch im Latest ... wie auch der controller 4
https://repo.iobroker.live/sources-dist.json (ist in iobroker als stable hinterlegt) zeigt mir auch die 2.3.3 an, iobroker selbst meint
"Installierte Instanzen: 1
Verfügbare Version: 2.2.3
Installierte Version: 2.2.3"
-
@moko Wo steht da 2.3.3?
-
@diginix latestVersion "2.3.3"
P.S. ich habe nicht behauptet dass die 2.3.3 als stable angezeigt wird.
Bei mir ist die letzte 2.2.3P.S. mein Fehler: habe latest mit stable verwechselt.
-
@moko Wenn du auf stable bist, wird dir keine latest Ver. angeboten.
-
@AlCalzone Ich bin nun schon die ganze Zeit auf der Suche nach der Ursache für die Eventspitzen beim Javascript Adapter.
Alle Skripte zusammen haben laut Logausgabe <80 subscriptions. Wenn ich die javascript Instanz starte und somit auch alle Skripte, gibt es schon mal eine Spitze von 263 Event ausgehend. Wie wird dieser Wert ermittelt bzw. was zählt da mit rein?Die Spitzen bei den eingehenden Events alle 15 min kann ich mir auch noch nicht erklären. Bin aber noch am Testen durch Deaktivieren von einzelnen Skripten die States von Adapter nutzen, die nur alle 15 min laufen (dwd, daswetter).
-
@diginix sagte in js-controller 4.0 jetzt im BETA/LATEST!:
Alle Skripte zusammen haben laut Logausgabe <80 subscriptions. Wenn ich die javascript Instanz starte und somit auch alle Skripte, gibt es schon mal eine Spitze von 263 Event ausgehend. Wie wird dieser Wert ermittelt bzw. was zählt da mit rein?
Jede State-Änderung jedes Wertes auf den du subscribest zählt da mit rein. By default subscribed der JS-Adapter aber alle States, selbst die die du nicht nutzt. So ermöglicht er, dass
getStateundsetStatetrotz asynchroner DB synchron sind.
Ich hab grade nochmal versucht das nachzustellen. Testinstanz mit latest controller, die Adapter Web/WS/VIS, ein Skript welches 1000 changes/s generiert (also 15000 in- und out-events), und dabei fleißig Adapter aktualisiert. Nix... Der Controller dümpelt auf 180 MB RAM herum.
-
@alcalzone Hm, ich werde mit meiner Analyse auch nicht schlauer.
Ich habe alle javascripte angehalten die ein "schedule" enthalten. Trotzdem habe ich weiterhin alle 15 min diese Spitzen.
Die gibt es wahrs. schon immer und machen auch keine direkten Probleme, aber nun habe ich mich durch das Erfassen der in/out Events bis dahin vorgearbeitet und wüsste gern den Ursprung.
Wenn ich den javascript Adapter anhalte kommt die ausgehende Spitze im Bild markiert. Sind aber nur 230, also ganz andere Skalierung. Meine Skripte schreiben beim Beenden keine states. Jedenfalls nicht wissentlich. -
So siehts aus.
pi@raspberrypi-display2:~ $ iobroker upgrade self internal/modules/cjs/loader.js:905 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15) at Function.Module._load (internal/modules/cjs/loader.js:746:27) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12) at internal/main/run_main_module.js:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } -
@e-i-k-e also jetzt ist dein Controller ganz weg. Dann Versuch den mal mit nem npm install zu installieren am besten fang bei der 3.3.22 an
-
Hallo,
ich habe ein Update von 3.3.22 auf 4.0.15 getätigt. Das mit den "unsupportet Meldungen" habe ich gelesen. Habe da noch ein paar andere Meldung während des Updates bekommen.
Beim Hochfahren der Adapter auch einige Meldungen von ideversen Adaptern "Error DB closed" bekommen.
Nach dem Anschein sind jetzt aber alle Adapter wieder hochgefahren. Habt Ihr das auch schon einmal gehabt ? Oder soll ich erst einmal zurück auf 3.3.22 ? Ist auf einem Proxmox LXC ConatinerUpdate js-controller from @3.3.22 to @4.0.15 NPM version: 6.14.16 npm install iobroker.js-controller@4.0.15 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call) Server Objects 127.0.0.1:38870 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"] Server States 127.0.0.1:36652 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"] Server Objects 127.0.0.1:38870 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"] Server States 127.0.0.1:36654 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"] Server Objects 127.0.0.1:38870 Error from InMemDB: Error: Unknown LUA script load Server Objects 127.0.0.1:38870 Error from InMemDB: Error: Unknown LUA script load Server Objects 127.0.0.1:38870 Error from InMemDB: Error: Unknown LUA script load Server Objects 127.0.0.1:38870 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}] Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}] -
@gelberlemmy Also dieses Upgrade log sieht aus wie erwartet. Zu den anderen Meldungen zeig doch mal ein Log
-
@apollon77 ich habe einmal die Errors heraus gezogen. Erst einmal nach einem Neustart von IOBroker :
admin.0 2022-02-22 20:31:13.713 error error shelly.0 2022-02-22 20:30:43.805 error DB closed shelly.0 2022-02-22 20:30:43.805 error Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/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.<anonymous> (net.js:686:12) shelly.0 2022-02-22 20:30:43.799 error unhandled promise rejection: DB closed shelly.0 2022-02-22 20:30:43.799 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). Zeile 562: 2022-02-22 03:16:28.032 - error: homeconnect.0 (1264) EventSource error: {"type":"error"} Zeile 562: 2022-02-22 03:16:28.032 - error: homeconnect.0 (1264) EventSource error: {"type":"error"} Zeile 564: 2022-02-22 03:16:28.085 - error: homeconnect.0 (1264) EventSource error: {"type":"error"} Zeile 564: 2022-02-22 03:16:28.085 - error: homeconnect.0 (1264) EventSource error: {"type":"error"} Zeile 566: 2022-02-22 03:16:29.218 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"} Zeile 566: 2022-02-22 03:16:29.218 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"} Zeile 567: 2022-02-22 03:16:29.219 - error: homeconnect.0 (1264) 401 Unauthorized Zeile 568: 2022-02-22 03:16:29.219 - error: homeconnect.0 (1264) Error (SIEMENS-HB678GBS6-68A40E16D548) Zeile 570: 2022-02-22 03:16:29.222 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"} Zeile 570: 2022-02-22 03:16:29.222 - error: homeconnect.0 (1264) EventSource error: {"type":"error","status":401,"message":"Unauthorized"} Zeile 571: 2022-02-22 03:16:29.223 - error: homeconnect.0 (1264) 401 Unauthorized Zeile 572: 2022-02-22 03:16:29.227 - error: homeconnect.0 (1264) Error (SIEMENS-SN658X06TE-68A40E1BED72) Zeile 1885: 2022-02-22 09:55:02.967 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1887: 2022-02-22 09:55:08.088 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1888: 2022-02-22 09:55:13.194 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1889: 2022-02-22 09:55:18.315 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1890: 2022-02-22 09:55:23.445 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1891: 2022-02-22 09:55:28.532 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1892: 2022-02-22 09:55:33.622 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1894: 2022-02-22 09:55:38.734 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1895: 2022-02-22 09:55:43.839 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1896: 2022-02-22 09:55:48.937 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1897: 2022-02-22 09:55:54.029 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 1898: 2022-02-22 09:55:59.118 - error: discovergy.0 (1203) Error retrieving information for : d8d935220f114f59bb4d2590966bd026 Zeile 2085: 2022-02-22 11:00:22.028 - warn: ical.0 (3185) get state error: Connection is closed. Zeile 3263: 2022-02-22 16:53:03.553 - error: admin.0 (302) failed connection to socket.io from ::ffff:192.168.171.68: Zeile 3264: 2022-02-22 16:53:03.558 - error: admin.0 (302) error Zeile 3440: 2022-02-22 17:00:29.873 - error: cloud.0 (1170) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud Zeile 3465: 2022-02-22 17:02:11.084 - error: cloud.0 (1170) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud Zeile 3482: 2022-02-22 17:02:12.295 - error: cloud.0 (1170) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud Zeile 4020: 2022-02-22 19:39:51.929 - error: admin.0 (3951) failed connection to socket.io from ::ffff:192.168.171.75: Zeile 4021: 2022-02-22 19:39:51.934 - error: admin.0 (3951) error Zeile 4200: 2022-02-22 20:00:36.184 - warn: ical.0 (4296) get state error: Connection is closed. Zeile 4201: 2022-02-22 20:00:36.193 - warn: ical.0 (4296) get state error: DB closed Zeile 4296: 2022-02-22 20:02:55.007 - error: mihome-vacuum.0 (535) Socket Close Zeile 4475: 2022-02-22 20:02:56.762 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4476: 2022-02-22 20:02:56.889 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4477: 2022-02-22 20:02:56.890 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4481: 2022-02-22 20:02:56.998 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#68C63AF991B6#1.Relay1.ChannelName for 192.168.171.7 (shellyswitch25 / shellyswitch25-68C63AF991B6 / SHSW-25#68C63AF991B6#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}" Zeile 4481: 2022-02-22 20:02:56.998 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#68C63AF991B6#1.Relay1.ChannelName for 192.168.171.7 (shellyswitch25 / shellyswitch25-68C63AF991B6 / SHSW-25#68C63AF991B6#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}" Zeile 4483: 2022-02-22 20:02:57.000 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4485: 2022-02-22 20:02:57.001 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4486: 2022-02-22 20:02:57.004 - error: shelly.0 (604) 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(). Zeile 4487: 2022-02-22 20:02:57.004 - error: shelly.0 (604) unhandled promise rejection: DB closed Zeile 4488: 2022-02-22 20:02:57.015 - error: shelly.0 (604) Error: DB closed Zeile 4488: 2022-02-22 20:02:57.015 - error: shelly.0 (604) Error: DB closed Zeile 4493: 2022-02-22 20:02:57.015 - error: shelly.0 (604) DB closed Zeile 4494: 2022-02-22 20:02:57.028 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.name for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"device":{"type":"SHSW-25","mac":"483FDA8DB8F7","hostname":"shellyswitch25-483FDA8DB8F7","num_outputs":2, "num_meters":2, "num_rollers":1},"wifi_ap":{"enabled":false,"ssid":"shellyswitch25-483FDA8DB8F7","key":""},"wifi_sta":{"enabled":true,"ssid":"Home_Lan","ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"ap_roaming":{"enabled":false,"threshold":-70},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellyswitch25-483FDA8DB8F7","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":true,"unprotected":false,"username":"gelberlemmy"},"pin_code":"","name":null,"fw":"20220209-093016/v1.11.8-g8c7bb8d","factory_reset_from_switch":true,"discoverable":true,"build_info":{"build_id":"20220209-093016/v1.11.8-g8c7bb8d","build_timestamp":"2022-02-09T09:30:16Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":"Europe/Berlin","lat":52.464722,"lng":13.395710,"tzautodetect":true,"tz_utc_offset":3600,"tz_dst":false,"tz_dst_auto":true,"time":"21:02","unixtime":1645560176,"led_status_disable":false,"debug_enable":false,"allow_cross_origin":false,"actions":{"active":false,"names":["btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","roller_open_url","roller_close_url","roller_stop_url"]},"hwinfo":{"hw_revision":"prod-191217", "batch_id":1},"mode":"roller","max_power":1840,"l ... Zeile 4494: 2022-02-22 20:02:57.028 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.name for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"device":{"type":"SHSW-25","mac":"483FDA8DB8F7","hostname":"shellyswitch25-483FDA8DB8F7","num_outputs":2, "num_meters":2, "num_rollers":1},"wifi_ap":{"enabled":false,"ssid":"shellyswitch25-483FDA8DB8F7","key":""},"wifi_sta":{"enabled":true,"ssid":"Home_Lan","ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"ap_roaming":{"enabled":false,"threshold":-70},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellyswitch25-483FDA8DB8F7","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":true,"unprotected":false,"username":"gelberlemmy"},"pin_code":"","name":null,"fw":"20220209-093016/v1.11.8-g8c7bb8d","factory_reset_from_switch":true,"discoverable":true,"build_info":{"build_id":"20220209-093016/v1.11.8-g8c7bb8d","build_timestamp":"2022-02-09T09:30:16Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":"Europe/Berlin","lat":52.464722,"lng":13.395710,"tzautodetect":true,"tz_utc_offset":3600,"tz_dst":false,"tz_dst_auto":true,"time":"21:02","unixtime":1645560176,"led_status_disable":false,"debug_enable":false,"allow_cross_origin":false,"actions":{"active":false,"names":["btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","btn_on_url","btn_off_url","longpush_url","shortpush_url","out_on_url","out_off_url","roller_open_url","roller_close_url","roller_stop_url"]},"hwinfo":{"hw_revision":"prod-191217", "batch_id":1},"mode":"roller","max_power":1840,"l ... Zeile 4496: 2022-02-22 20:02:57.130 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4498: 2022-02-22 20:02:57.130 - warn: shelly.0 (604) get state error: Connection is closed. Zeile 4499: 2022-02-22 20:02:57.220 - warn: zwave2.0 (1798) get state error: Connection is closed. Zeile 4500: 2022-02-22 20:02:57.236 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.Relay1.ChannelName for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}" Zeile 4500: 2022-02-22 20:02:57.236 - error: shelly.0 (604) [httpIoBrokerState] Error for state SHSW-25#483FDA8DB8F7#1.Relay1.ChannelName for 192.168.171.86 (shellyswitch25 / shellyswitch25-483FDA8DB8F7 / SHSW-25#483FDA8DB8F7#1): Error: Connection is closed. - value: "{"name":null,"appliance_type":"General","ison":false,"has_timer":false,"default_state":"switch","btn_type":"toggle","btn_reverse":0,"auto_on":0.00,"auto_off":0.00,"max_power":0,"schedule":false,"schedule_rules":[]}" Zeile 4502: 2022-02-22 20:02:57.256 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4504: 2022-02-22 20:02:57.269 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4506: 2022-02-22 20:02:57.270 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4508: 2022-02-22 20:02:57.270 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4510: 2022-02-22 20:02:57.271 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4512: 2022-02-22 20:02:57.272 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4514: 2022-02-22 20:02:57.272 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4516: 2022-02-22 20:02:57.273 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4518: 2022-02-22 20:02:57.274 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4520: 2022-02-22 20:02:57.290 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4522: 2022-02-22 20:02:57.291 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4524: 2022-02-22 20:02:57.292 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4526: 2022-02-22 20:02:57.292 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4528: 2022-02-22 20:02:57.293 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4530: 2022-02-22 20:02:57.294 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4532: 2022-02-22 20:02:57.294 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4534: 2022-02-22 20:02:57.295 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4536: 2022-02-22 20:02:57.296 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4538: 2022-02-22 20:02:57.296 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4540: 2022-02-22 20:02:57.297 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4542: 2022-02-22 20:02:57.297 - warn: device-reminder.0 (1188) get state error: Connection is closed. Zeile 4543: 2022-02-22 20:02:57.311 - error: device-reminder.0 (1188) 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(). Zeile 4544: 2022-02-22 20:02:57.311 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4545: 2022-02-22 20:02:57.314 - error: device-reminder.0 (1188) Error: DB closed Zeile 4545: 2022-02-22 20:02:57.314 - error: device-reminder.0 (1188) Error: DB closed Zeile 4553: 2022-02-22 20:02:57.315 - error: device-reminder.0 (1188) DB closed Zeile 4554: 2022-02-22 20:02:57.316 - error: device-reminder.0 (1188) 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(). Zeile 4555: 2022-02-22 20:02:57.317 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4556: 2022-02-22 20:02:57.338 - error: device-reminder.0 (1188) Error: DB closed Zeile 4556: 2022-02-22 20:02:57.338 - error: device-reminder.0 (1188) Error: DB closed Zeile 4564: 2022-02-22 20:02:57.339 - error: device-reminder.0 (1188) DB closed Zeile 4565: 2022-02-22 20:02:57.340 - error: device-reminder.0 (1188) 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(). Zeile 4566: 2022-02-22 20:02:57.340 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4567: 2022-02-22 20:02:57.341 - error: device-reminder.0 (1188) Error: DB closed Zeile 4567: 2022-02-22 20:02:57.341 - error: device-reminder.0 (1188) Error: DB closed Zeile 4575: 2022-02-22 20:02:57.341 - error: device-reminder.0 (1188) DB closed Zeile 4576: 2022-02-22 20:02:57.342 - error: device-reminder.0 (1188) 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(). Zeile 4577: 2022-02-22 20:02:57.342 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4578: 2022-02-22 20:02:57.470 - error: device-reminder.0 (1188) Error: DB closed Zeile 4578: 2022-02-22 20:02:57.470 - error: device-reminder.0 (1188) Error: DB closed Zeile 4586: 2022-02-22 20:02:57.471 - error: device-reminder.0 (1188) DB closed Zeile 4587: 2022-02-22 20:02:57.471 - error: device-reminder.0 (1188) 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(). Zeile 4588: 2022-02-22 20:02:57.472 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4589: 2022-02-22 20:02:57.472 - error: device-reminder.0 (1188) Error: DB closed Zeile 4589: 2022-02-22 20:02:57.472 - error: device-reminder.0 (1188) Error: DB closed Zeile 4597: 2022-02-22 20:02:57.473 - error: device-reminder.0 (1188) DB closed Zeile 4598: 2022-02-22 20:02:57.473 - error: device-reminder.0 (1188) 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(). Zeile 4599: 2022-02-22 20:02:57.478 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4600: 2022-02-22 20:02:57.480 - error: device-reminder.0 (1188) Error: DB closed Zeile 4600: 2022-02-22 20:02:57.480 - error: device-reminder.0 (1188) Error: DB closed Zeile 4608: 2022-02-22 20:02:57.480 - error: device-reminder.0 (1188) DB closed Zeile 4609: 2022-02-22 20:02:57.482 - error: device-reminder.0 (1188) 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(). Zeile 4610: 2022-02-22 20:02:57.482 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4611: 2022-02-22 20:02:57.483 - error: device-reminder.0 (1188) Error: DB closed Zeile 4611: 2022-02-22 20:02:57.483 - error: device-reminder.0 (1188) Error: DB closed Zeile 4619: 2022-02-22 20:02:57.483 - error: device-reminder.0 (1188) DB closed Zeile 4620: 2022-02-22 20:02:57.484 - error: device-reminder.0 (1188) 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(). Zeile 4621: 2022-02-22 20:02:57.484 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4622: 2022-02-22 20:02:57.485 - error: device-reminder.0 (1188) Error: DB closed Zeile 4622: 2022-02-22 20:02:57.485 - error: device-reminder.0 (1188) Error: DB closed Zeile 4630: 2022-02-22 20:02:57.485 - error: device-reminder.0 (1188) DB closed Zeile 4631: 2022-02-22 20:02:57.488 - error: device-reminder.0 (1188) 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(). Zeile 4632: 2022-02-22 20:02:57.488 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4633: 2022-02-22 20:02:57.495 - error: device-reminder.0 (1188) Error: DB closed Zeile 4633: 2022-02-22 20:02:57.495 - error: device-reminder.0 (1188) Error: DB closed Zeile 4641: 2022-02-22 20:02:57.495 - error: device-reminder.0 (1188) DB closed Zeile 4642: 2022-02-22 20:02:57.496 - error: device-reminder.0 (1188) 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(). Zeile 4643: 2022-02-22 20:02:57.496 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4644: 2022-02-22 20:02:57.497 - error: device-reminder.0 (1188) Error: DB closed Zeile 4644: 2022-02-22 20:02:57.497 - error: device-reminder.0 (1188) Error: DB closed Zeile 4652: 2022-02-22 20:02:57.497 - error: device-reminder.0 (1188) DB closed Zeile 4653: 2022-02-22 20:02:57.498 - error: device-reminder.0 (1188) 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(). Zeile 4654: 2022-02-22 20:02:57.498 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4655: 2022-02-22 20:02:57.500 - error: device-reminder.0 (1188) Error: DB closed Zeile 4655: 2022-02-22 20:02:57.500 - error: device-reminder.0 (1188) Error: DB closed Zeile 4663: 2022-02-22 20:02:57.500 - error: device-reminder.0 (1188) DB closed Zeile 4664: 2022-02-22 20:02:57.501 - error: device-reminder.0 (1188) 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(). Zeile 4665: 2022-02-22 20:02:57.501 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4666: 2022-02-22 20:02:57.502 - error: device-reminder.0 (1188) Error: DB closed Zeile 4666: 2022-02-22 20:02:57.502 - error: device-reminder.0 (1188) Error: DB closed Zeile 4674: 2022-02-22 20:02:57.502 - error: device-reminder.0 (1188) DB closed Zeile 4675: 2022-02-22 20:02:57.503 - error: device-reminder.0 (1188) 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(). Zeile 4676: 2022-02-22 20:02:57.503 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4677: 2022-02-22 20:02:57.504 - error: device-reminder.0 (1188) Error: DB closed Zeile 4677: 2022-02-22 20:02:57.504 - error: device-reminder.0 (1188) Error: DB closed Zeile 4685: 2022-02-22 20:02:57.504 - error: device-reminder.0 (1188) DB closed Zeile 4686: 2022-02-22 20:02:57.505 - error: device-reminder.0 (1188) 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(). Zeile 4687: 2022-02-22 20:02:57.505 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4688: 2022-02-22 20:02:57.506 - error: device-reminder.0 (1188) Error: DB closed Zeile 4688: 2022-02-22 20:02:57.506 - error: device-reminder.0 (1188) Error: DB closed Zeile 4696: 2022-02-22 20:02:57.507 - error: device-reminder.0 (1188) DB closed Zeile 4697: 2022-02-22 20:02:57.507 - error: device-reminder.0 (1188) 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(). Zeile 4698: 2022-02-22 20:02:57.508 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4699: 2022-02-22 20:02:57.509 - error: device-reminder.0 (1188) Error: DB closed Zeile 4699: 2022-02-22 20:02:57.509 - error: device-reminder.0 (1188) Error: DB closed Zeile 4707: 2022-02-22 20:02:57.509 - error: device-reminder.0 (1188) DB closed Zeile 4708: 2022-02-22 20:02:57.510 - error: device-reminder.0 (1188) 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(). Zeile 4709: 2022-02-22 20:02:57.510 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4710: 2022-02-22 20:02:57.511 - error: device-reminder.0 (1188) Error: DB closed Zeile 4710: 2022-02-22 20:02:57.511 - error: device-reminder.0 (1188) Error: DB closed Zeile 4718: 2022-02-22 20:02:57.511 - error: device-reminder.0 (1188) DB closed Zeile 4719: 2022-02-22 20:02:57.512 - error: device-reminder.0 (1188) 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(). Zeile 4720: 2022-02-22 20:02:57.512 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4721: 2022-02-22 20:02:57.513 - error: device-reminder.0 (1188) Error: DB closed Zeile 4721: 2022-02-22 20:02:57.513 - error: device-reminder.0 (1188) Error: DB closed Zeile 4729: 2022-02-22 20:02:57.514 - error: device-reminder.0 (1188) DB closed Zeile 4730: 2022-02-22 20:02:57.514 - error: device-reminder.0 (1188) 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(). Zeile 4731: 2022-02-22 20:02:57.515 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4732: 2022-02-22 20:02:57.516 - error: device-reminder.0 (1188) Error: DB closed Zeile 4732: 2022-02-22 20:02:57.516 - error: device-reminder.0 (1188) Error: DB closed Zeile 4740: 2022-02-22 20:02:57.516 - error: device-reminder.0 (1188) DB closed Zeile 4741: 2022-02-22 20:02:57.517 - error: device-reminder.0 (1188) 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(). Zeile 4742: 2022-02-22 20:02:57.517 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4743: 2022-02-22 20:02:57.518 - error: device-reminder.0 (1188) Error: DB closed Zeile 4743: 2022-02-22 20:02:57.518 - error: device-reminder.0 (1188) Error: DB closed Zeile 4751: 2022-02-22 20:02:57.518 - error: device-reminder.0 (1188) DB closed Zeile 4752: 2022-02-22 20:02:57.519 - error: device-reminder.0 (1188) 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(). Zeile 4753: 2022-02-22 20:02:57.519 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4754: 2022-02-22 20:02:57.520 - error: device-reminder.0 (1188) Error: DB closed Zeile 4754: 2022-02-22 20:02:57.520 - error: device-reminder.0 (1188) Error: DB closed Zeile 4762: 2022-02-22 20:02:57.521 - error: device-reminder.0 (1188) DB closed Zeile 4763: 2022-02-22 20:02:57.521 - error: device-reminder.0 (1188) 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(). Zeile 4764: 2022-02-22 20:02:57.522 - error: device-reminder.0 (1188) unhandled promise rejection: DB closed Zeile 4765: 2022-02-22 20:02:57.523 - error: device-reminder.0 (1188) Error: DB closed Zeile 4765: 2022-02-22 20:02:57.523 - error: device-reminder.0 (1188) Error: DB closed Zeile 4770: 2022-02-22 20:02:57.523 - error: device-reminder.0 (1188) DB closed Zeile 4870: 2022-02-22 20:06:58.836 - error: admin.0 (5100) error Zeile 5007: 2022-02-22 20:07:52.287 - error: javascript.0 (5145) In file included from ../src/binding.cc:1: Zeile 5070: 2022-02-22 20:08:07.578 - error: javascript.0 (5145) In file included from ../src/binding.cc:6: Zeile 5361: 2022-02-22 20:08:38.905 - error: cloud.0 (5901) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud Zeile 5375: 2022-02-22 20:08:46.490 - error: discovergy.0 (5932) State type : printedFullSerialNumber unknown, send this information to the developer ==> printedFullSerialNumber : "1ESY1161230212" Zeile 5610: 2022-02-22 20:09:09.158 - error: cloud.0 (5901) Cannot activate admin.0 for cloud, because authentication is enabled. Please create extra instance for cloud
