NEWS
Server Cannot start inMem-objects on port 9001
-
@karl-1 sagte in Server Cannot start inMem-objects on port 9001:
Wo die Daten gepeichert werden, sollte der Struktur egal sein.
aber wenn du sie in einem nicht zulässigen Systemverzeichnis speicherst kann es sein, dass sie bei einem Update gelöscht werden.
@karl-1 sagte in Server Cannot start inMem-objects on port 9001:
ich habe das Backup im ioBroker mit dem Adapter backitup gemacht.
und wohin genau?
Standard ist /opt/iobroker/backupsUnd nichts anderes
-
@thomas-braun
Um die Backup Daten extern zu speichern habe ich einen USB Stick gemountet.pi@raspberrypi:/media $ ls usb usb0 usb1 usb2 usb3 usb4 usb5 usb6 usb7 usbstick
Von der Konsole aus kann ich darauf zugreifen und Files dort auch abspeichern!
Der ioBroker verweigert aber den Zugriff:
started iobroker ... [DEBUG] [iobroker] - host.raspberrypi 716 states saved [DEBUG] [iobroker] - host.raspberrypi 924 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_01_05-16_13_41_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [cifs] - used copy path: /media/usbstick [DEBUG] [cifs] - Copy iobroker_2023_01_05-16_13_41_backupiobroker.tar.gz... [ERROR] [cifs] - Error: EACCES: permission denied, open '/media/usbstick/iobroker_2023_01_05-16_13_41_backupiobroker.tar.gz' [DEBUG] [cifs] - done [ERROR] [clean] - Backup files not deleted from /opt/iobroker/backups because some errors. [DEBUG] [clean] - done
Ich habe trotz intensiver Suche im Internet nichts gefunden, was mir weiterhilft!
-
@karl-1 iobroker läuft als user "iobroker" ...darf der da zugreifen?
-
Warum dann per cifs, wenn der schon herkömmlich gemountet ist?
Mit welchen Optionen wird das Dateisystem des Sticks (welches ist es?) gemountet? -
@apollon77
Ich denke schon:pi@raspberrypi:/media $ ls -l total 36 lrwxrwxrwx 1 root root 4 Jan 4 12:00 usb -> usb0 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb0 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb1 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb2 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb3 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb4 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb5 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb6 drwxr-xr-x 2 root root 4096 Jan 4 12:00 usb7 drwxr-xr-x 2 root root 4096 Jan 5 16:27 usbstick
-
@thomas-braun
Das Dateisystem des Sticks ist exFAT
cifs wir auch beim internen Speichern verwendet:Started iobroker ... [DEBUG] [iobroker] - host.raspberrypi 732 states saved [DEBUG] [iobroker] - host.raspberrypi 943 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2023_01_05-17_21_31_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [cifs] - used copy path: /opt/iobroker/backups [DEBUG] [cifs] - Copy iobroker_2023_01_05-17_21_31_backupiobroker.tar.gz... [DEBUG] [cifs] - done [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [EXIT] 0
-
@karl-1 Also ich lese die Rechte so: Root darf alles, grou darf nur lesen, other darf nur lesen ... Das würde erklären das der User "iobroker" (aka "other") da nichts zum schreiben öffnen darf-. EIn symlonk hatt immer "alles" weil der egal ist
-
-
@thomas-braun
Problem mit fehlenden Berechtigungen ist gelöst!
Besten Dank! -
Und was hast du jetzt gemacht?
Hilft vielleicht anderen. -
@apollon77
Besten Dank für den Support!
Problem ist gelöst, habe die Rechte angepasst! -
@karl-1 sagte in Server Cannot start inMem-objects on port 9001:
habe die Rechte angepasst!
Was genau?
-
Hallo zusammen,
ich habe am 02. Januar eine Stromausfall gehabt und seitdem läuft mein iobroker nicht mehr. ich bekomen keine Verbindung zum Port 9001, bzw.
der port ist einfach nicht mehr offen. Ich bekommen immer nur die Fehlermeldung:Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!
oder
No connection to databases possible ...
Bin u.a. nach diesem Thread vorgegangen:
https://forum.iobroker.net/topic/54757/no-connection-to-databases-possibleHabe den iobroker ein Update, als auch ein upgrade self durchführen lassen.
Habe ein Backup vom 31.12.2022 einspielen lassen, was auch kein Erfolg brachteeinzige Auffällige , ist eine 1,6 GB große objects.jsonl Datei
admin@server03:/opt/iobroker/iobroker-data$ ls -la /opt/iobroker/iobroker-data total 1603736 drwxrwxrwx+ 7 iobroker iobroker 4096 Jan 7 11:03 . drwxrwxr-x+ 6 iobroker iobroker 4096 Jan 7 10:53 .. drwxrwxrwx+ 2 iobroker iobroker 12288 Jan 4 19:31 backup-objects drwxrwxrwx+ 14 iobroker iobroker 4096 Feb 21 2022 files -rwxrwxrwx+ 1 iobroker iobroker 5091 Jan 7 10:47 iobroker.json -rwxrwxrwx+ 1 iobroker iobroker 3 Nov 22 23:29 notifications.json -rwxrwxrwx+ 1 iobroker iobroker 1642010661 Jan 6 20:50 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 Jan 7 11:03 objects.jsonl.lock drwxrwxrwx+ 2 iobroker iobroker 4096 Feb 20 2022 sqlite -rwxrwxrwx+ 1 iobroker iobroker 0 Apr 4 2022 states.json.broken -rw-rw-r--+ 1 iobroker iobroker 127506 Jan 7 10:53 states.jsonl drwxrwxrwx+ 2 iobroker iobroker 28672 Jan 4 19:50 zigbee_0
In der iobroker.json habe ich auch schon unter Object den connectTimeout auf 600000 gesetzt
Ohne jeden Erfolg.{ "system": { "memoryLimitMB": 0, "hostname": "", "statisticsInterval": 15000, "statisticsIntervalComment": "Interval how often the counters for input/output in adapters and controller will be updated", "checkDiskInterval": 300000, "checkDiskIntervalComment": "Interval how often the disk size will be checked", "instanceStartInterval": 2000, "noChmodComment": "Flag to test new feature with no chmod call. Must be deleted later and noChmod must be mainline (2018.06.04)", "compact": false, "compactComment": "Controller will try to start the instances as a part of the same process. No spawn will be done. Only by adapters that support it and have flag compact flag in io-package.json", "allowShellCommands": false, "allowShellCommandsComment": "Allow execution of \"shell\" sendToHost commands", "memLimitWarn": 100, "memLimitWarnComment": "If the available RAM is below this threshold on adapter start, a warning will be logged.", "memLimitError": 50, "memLimitErrorComment": "If the available RAM is below this threshold on adapter start, an error will be logged." }, "multihostService": { "enabled": false, "secure": true, "password": "" }, "objects": { "type": "jsonl", "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].", "host": "127.0.0.1", "port": 9001, "noFileCache": false, "maxQueue": 1000, "connectTimeout": 600000, "writeFileInterval": 5000,
Ich persönlich weiß nicht mehr weiter.
Würde mich freuen, wenn einer noch eine Idee hat, ansonsten bleibt mir nicht ürbig , den iobroker neu aufzusetzen.Viele Grüße nettekov
P.S. Mein iobroker als Linux in der VM auf einer Synology NAS -
-
@thomas-braun said in Server Cannot start inMem-objects on port 9001:
ls -lAh /opt/iobroker/iobroker-data/backup-objects
total 67M -rwxrwxrwx+ 1 iobroker iobroker 170K Apr 10 2022 2022-04-09_22-26_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 197K Apr 10 2022 2022-04-10_10-52_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 10 2022 2022-04-10_13-31_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 10 2022 2022-04-10_20-21_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 11 2022 2022-04-11_20-21_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 12 2022 2022-04-12_09-25_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 13 2022 2022-04-13_09-35_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 13 2022 2022-04-13_18-35_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 14 2022 2022-04-14_01-25_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 14 2022 2022-04-14_06-46_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 14 2022 2022-04-14_11-16_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 14 2022 2022-04-14_13-16_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 14 2022 2022-04-14_14-48_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 14 2022 2022-04-14_16-49_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 14 2022 2022-04-14_18-49_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 14 2022 2022-04-14_20-49_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-14_22-49_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_00-50_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_02-50_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_04-50_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_06-51_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_08-51_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_10-52_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_12-52_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_14-52_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_16-53_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_18-53_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_20-53_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_21-49_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 15 2022 2022-04-15_21-55_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-15_22-09_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-15_22-09_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-15_22-21_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-15_22-26_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-15_22-34_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-15_22-41_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-15_22-41_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_00-42_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_02-42_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_04-42_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_06-42_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_08-22_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_08-43_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_10-22_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_10-23_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_10-45_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-16_10-46_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-16_10-47_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-16_10-49_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-16_10-52_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_10-53_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-16_10-53_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_10-54_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 17K Apr 16 2022 2022-04-16_10-54_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_11-35_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_11-35_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 201K Apr 16 2022 2022-04-16_11-43_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_11-43_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 1,2M Apr 16 2022 2022-04-16_12-58_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_12-58_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 1,2M Apr 16 2022 2022-04-16_13-56_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 1,2M Apr 16 2022 2022-04-16_13-57_objects.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_13-57_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 18K Apr 16 2022 2022-04-16_13-58_states.json.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 2 21:31 2023-01-02_21-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 2 21:31 2023-01-02_21-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 2 23:31 2023-01-02_23-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 2 23:31 2023-01-02_23-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 01:31 2023-01-03_01-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 01:31 2023-01-03_01-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 03:31 2023-01-03_03-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 14K Jan 3 03:31 2023-01-03_03-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 05:31 2023-01-03_05-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 05:31 2023-01-03_05-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 07:31 2023-01-03_07-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 07:31 2023-01-03_07-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 09:31 2023-01-03_09-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 09:31 2023-01-03_09-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 11:31 2023-01-03_11-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 14K Jan 3 11:31 2023-01-03_11-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 13:31 2023-01-03_13-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 14K Jan 3 13:31 2023-01-03_13-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 15:31 2023-01-03_15-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 15:31 2023-01-03_15-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 17:31 2023-01-03_17-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 17:31 2023-01-03_17-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 19:31 2023-01-03_19-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 19:31 2023-01-03_19-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 21:31 2023-01-03_21-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 21:31 2023-01-03_21-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 3 23:31 2023-01-03_23-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 3 23:31 2023-01-03_23-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 01:31 2023-01-04_01-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 01:31 2023-01-04_01-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 03:31 2023-01-04_03-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 03:31 2023-01-04_03-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 05:31 2023-01-04_05-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 05:31 2023-01-04_05-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 07:31 2023-01-04_07-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 07:31 2023-01-04_07-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 09:31 2023-01-04_09-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 09:31 2023-01-04_09-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 11:31 2023-01-04_11-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 11:31 2023-01-04_11-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 13:31 2023-01-04_13-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 13:31 2023-01-04_13-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 15:31 2023-01-04_15-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 15:31 2023-01-04_15-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 17:31 2023-01-04_17-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 17:31 2023-01-04_17-31_states.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 4 19:31 2023-01-04_19-31_objects.jsonl.gz -rwxrwxrwx+ 1 iobroker iobroker 13K Jan 4 19:31 2023-01-04_19-31_states.jsonl.gz
-
Dann spiel mal eine von denen statt der explodierten Datei ein.
Geht prinzipiell so:
Halt bei jsonl mit anderen Dateinamen.
-
@nettekov said in Server Cannot start inMem-objects on port 9001:
Zum Beispiel:
Zeile 66 (ist die Älteste):-rwxrwxrwx+ 1 iobroker iobroker 2,5M Jan 2 21:31 2023-01-02_21-31_objects.jsonl.gz
Und dann so?
cd /opt/iobroker/iobroker-data/backup-objects gunzip -ck 2023-01-02_21-31_objects.jsonl.gz > /opt/iobroker/iobroker-data/objects.jsonl
-
Ja. ioBroker zuvor auf Eis legen.
-
Sieh schon besser aus
total 8772 drwxrwxrwx+ 6 iobroker iobroker 4096 Jan 7 17:00 . drwxrwxr-x+ 6 iobroker iobroker 4096 Jan 7 10:53 .. drwxrwxrwx+ 2 iobroker iobroker 12288 Jan 4 19:31 backup-objects drwxrwxrwx+ 14 iobroker iobroker 4096 Feb 21 2022 files -rwxrwxrwx+ 1 iobroker iobroker 5091 Jan 7 10:47 iobroker.json -rwxrwxrwx+ 1 iobroker iobroker 6020 Jan 7 16:41 iobroker.json.save -rwxrwxrwx+ 1 iobroker iobroker 3 Nov 22 23:29 notifications.json -rwxrwxrwx+ 1 iobroker iobroker 8765468 Jan 7 17:00 objects.jsonl drwxrwxrwx+ 2 iobroker iobroker 4096 Feb 20 2022 sqlite -rwxrwxrwx+ 1 iobroker iobroker 0 Apr 4 2022 states.json.broken -rw-rw-r--+ 1 iobroker iobroker 127506 Jan 7 10:53 states.jsonl drwxrwxrwx+ 2 iobroker iobroker 28672 Jan 4 19:50 zigbee_0
iobroker wieder starten?
-