PINE Rock64 bootet nicht mehr
-
-
-
@thomas-braun sagte in PINE Rock64 bootet nicht mehr:
iobroker update
pi@rock64:~$ iobroker update Used repository: stable hash unchanged, use cached sources update done Adapter "admin" : 5.1.23 , installed 5.1.23 Adapter "alexa2" : 3.9.3 , installed 3.9.3 Adapter "backitup" : 2.1.13 , installed 2.1.13 Adapter "cloud" : 4.1.0 , installed 4.1.0 Adapter "daswetter" : 3.0.7 , installed 3.0.7 Adapter "discovery" : 2.7.0 , installed 2.7.0 Adapter "dwd" : 2.7.7 , installed 2.7.7 Adapter "flot" : 1.10.6 , installed 1.10.6 Adapter "fritzbox" : 0.2.1 , installed 0.2.1 Adapter "fritzdect" : 2.1.15 , installed 2.1.15 Adapter "fullybrowser" : 2.0.8 , installed 2.0.8 Adapter "history" : 1.9.13 , installed 1.9.13 Adapter "hm-rega" : 3.0.29 , installed 3.0.29 Adapter "hm-rpc" : 1.14.43 , installed 1.14.43 Adapter "ical" : 1.11.2 , installed 1.11.2 Adapter "icons-addictive-flavour-png": 0.1.0 , installed 0.1.0 Adapter "icons-fatcow-hosting": 0.1.0 , installed 0.1.0 Adapter "icons-icons8" : 0.0.1 , installed 0.0.1 Adapter "icons-material-png": 0.1.0 , installed 0.1.1 Adapter "icons-material-svg": 0.1.0 , installed 0.1.1 Adapter "icons-mfd-svg" : 1.0.2 , installed 1.0.2 Adapter "icons-open-icon-library-png": 0.1.2 , installed 0.1.2 Adapter "icons-ultimate-png": 1.0.1 , installed 1.0.1 Adapter "info" : 1.9.8 , installed 1.9.8 Adapter "iot" : 1.8.22 , installed 1.8.22 Adapter "jarvis" : 2.2.1 , installed 2.2.1 Adapter "javascript" : 5.2.8 , installed 5.2.8 Controller "js-controller" : 3.3.15 , installed 3.3.15 Adapter "luftdaten" : 1.0.3 , installed 1.0.3 Adapter "material" : 1.0.4 , installed 0.13.9 [Updateable] Adapter "melcloud" : 1.1.4 , installed 1.1.4 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "mqtt-client" : 1.4.0 , installed 1.4.0 Adapter "net-tools" : 0.1.5 , installed 0.1.5 Adapter "octoprint" : 1.1.1 , installed 1.1.1 Adapter "owntracks" : 1.0.0 , installed 1.0.0 Adapter "parser" : 1.0.7 , installed 1.0.7 Adapter "ping" : 1.5.0 , installed 1.5.0 Adapter "places" : 1.0.0 , installed 1.0.0 Adapter "pushover" : 2.0.5 , installed 2.0.5 Adapter "rickshaw" : 1.0.0 , installed 1.0.0 Adapter "samsung" : 0.2.9 , installed 0.2.9 Adapter "sayit" : 1.12.3 , installed 1.12.3 Adapter "scenes" : 2.3.6 , installed 2.3.6 Adapter "shelly" : 4.0.7 , installed 4.0.7 Adapter "simple-api" : 2.6.1 , installed 2.6.1 Adapter "socketio" : 3.1.4 , installed 3.1.4 Adapter "synology" : 1.0.0 , installed 1.0.0 Adapter "telegram" : 1.10.0 , installed 1.10.0 Adapter "text2command" : 2.1.1 , installed 2.1.1 Adapter "tr-064" : 4.2.14 , installed 4.2.14 Adapter "tvspielfilm" : 1.0.4 , installed 1.0.4 Adapter "vis" : 1.4.3 , installed 1.4.3 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 0.1.5 , installed 0.1.5 Adapter "vis-colorpicker": 1.2.0 , installed 1.2.0 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-google-fonts": 0.1.0 , installed 0.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets" : 1.1.7 , installed 1.1.7 Adapter "vis-inventwo" : 3.0.11 , installed 3.0.11 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-justgage" : 1.0.2 , installed 1.0.2 Adapter "vis-keyboard" : 0.0.2 , installed 0.0.2 Adapter "vis-lcars" : 1.0.4 , installed 1.0.4 Adapter "vis-map" : 1.0.4 , installed 1.0.4 Adapter "vis-material-advanced": 1.7.0 , installed 1.7.0 Adapter "vis-metro" : 1.1.2 , installed 1.1.2 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.1.7 , installed 1.1.7 Adapter "vw-connect" : 0.0.39 , installed 0.0.39 A -
@derrapf
Da fehlt noch ein Teil.iobroker upgrade iobroker upload allDann sollte soweit alles konsistent sein.
-
Ok. Läuft
dreiviertel Stunde später: Läuft immer noch...
Fertig:
Hier das Log log.txt
Der Js-Controller ist immer noch daIch lass das aber erstmal so, denn er tut mir ja nicht weh, und so wie es aussieht geht erstmal wieder alles. Juhu.
Gruss Ralf -
Ich brauche leider nochmal Eure Hilfe
Seit meinem letzten Post lief der iobroker wieder. Gestern fiel mir auf dass er keine Befehle über Alexa mehr ausführt. Heute hab ich mal nachgeschaut und festgestellt, dass die objects.json und states.json 0Byte gross waren
Habe ihn angehalten und die beiden Dateien aus euinem Backup zurück kopiert. Geht aber immer noch nicht.
irgendwas stimmt mot der redis DB wohl nicht:redis-cli Could not connect to Redis at 127.0.0.1:6379: Connection refusedund
iobroker list instances No connection to states 127.0.0.1:6379[redis]Auch im Log sieht man das
2021-09-08 18:58:21.040 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controller starting 2021-09-08 18:58:21.055 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 18:58:21.057 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 18:58:21.059 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596 2021-09-08 18:58:51.114 - error: host.rock64 No connection to databases possible, restart 2021-09-08 18:58:51.140 - info: host.rock64 iobroker _restart 2021-09-08 18:58:54.786 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controller starting 2021-09-08 18:58:54.802 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 18:58:54.804 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 18:58:54.806 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596Auch im Syslog sieht man das:
Sep 8 15:32:41 rock64 systemd[1]: Started ioBroker Server. Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 1. Sep 8 15:32:41 rock64 systemd[1]: Stopped Advanced key-value store. Sep 8 15:32:41 rock64 systemd[1]: Starting Advanced key-value store... Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Sep 8 15:32:41 rock64 systemd[1]: Started Advanced key-value store. Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:32:41 rock64 systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 2. Sep 8 15:32:41 rock64 systemd[1]: Stopped Advanced key-value store. Sep 8 15:32:41 rock64 systemd[1]: Starting Advanced key-value store... Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Sep 8 15:32:42 rock64 systemd[1]: Started Advanced key-value store. Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 3. Sep 8 15:32:42 rock64 systemd[1]: Stopped Advanced key-value store. Sep 8 15:32:42 rock64 systemd[1]: Starting Advanced key-value store... Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Sep 8 15:32:42 rock64 systemd[1]: Started Advanced key-value store. Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:32:42 rock64 systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 4. Sep 8 15:32:42 rock64 systemd[1]: Stopped Advanced key-value store. Sep 8 15:32:42 rock64 systemd[1]: Starting Advanced key-value store... Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Sep 8 15:32:43 rock64 systemd[1]: Started Advanced key-value store. Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5. Sep 8 15:32:43 rock64 systemd[1]: Stopped Advanced key-value store. Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Start request repeated too quickly. Sep 8 15:32:43 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:32:43 rock64 systemd[1]: Failed to start Advanced key-value store. Sep 8 15:32:49 rock64 systemd[1]: Started Session 10 of user pi. Sep 8 15:33:14 rock64 systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:33:14 rock64 systemd[1]: iobroker.service: Failed with result 'exit-code'. Sep 8 15:33:14 rock64 systemd[1]: iobroker.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:33:14 rock64 systemd[1]: iobroker.service: Scheduled restart job, restart counter is at 7. Sep 8 15:33:14 rock64 systemd[1]: Stopped ioBroker Server. Sep 8 15:33:14 rock64 systemd[1]: Starting Advanced key-value store... Sep 8 15:33:14 rock64 systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory Sep 8 15:33:14 rock64 systemd[1]: Started Advanced key-value store. Sep 8 15:33:14 rock64 systemd[1]: Started ioBroker Server. Sep 8 15:33:14 rock64 systemd[1]: redis-server.service: Main process exited, code=exited, status=1/FAILURE Sep 8 15:33:14 rock64 systemd[1]: redis-server.service: Failed with result 'exit-code'. Sep 8 15:33:14 rock64 systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart. Sep 8 15:33:14 rock64 systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 1. Sep 8 15:33:14 rock64 systemd[1]: Stopped Advanced key-value store. Sep 8 15:33:14 rock64 systemd[1]: Starting Advanced key-value store...Kann man da noch was retten oder muss ich wieder von vorne anfangen??
Gruss Ralf
-
Versuch mal:
iobroker stop sudo systemctl stop redis sudo apt update sudo apt install redis --reinstall -
@thomas-braun
Danke
Sieht aber nicht so gut aus:root@rock64:~# sudo apt update Hit:1 http://security.debian.org buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Hit:4 https://deb.nodesource.com/node_12.x buster InRelease Hit:5 http://deb.debian.org/debian buster-backports InRelease Hit:6 http://armbian.systemonachip.net/apt buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done 11 packages can be upgraded. Run 'apt list --upgradable' to see them. root@rock64:~# root@rock64:~# sudo apt install redis --reinstall Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 11 not upgraded. Need to get 45.3 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://deb.debian.org/debian buster/main arm64 redis all 5:5.0.3-4+deb10u3 [45.3 kB] Fetched 45.3 kB in 0s (686 kB/s) (Reading database ... 49692 files and directories currently installed.) Preparing to unpack .../redis_5%3a5.0.3-4+deb10u3_all.deb ... Unpacking redis (5:5.0.3-4+deb10u3) over (5:5.0.3-4+deb10u3) ... Setting up redis (5:5.0.3-4+deb10u3) ... root@rock64:~# iobroker start root@rock64:~# tail -f /opt/iobroker/log/iobroker.current.log 2021-09-08 19:36:00.111 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controlle r starting 2021-09-08 19:36:00.125 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 19:36:00.126 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 19:36:00.128 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1 :f596 2021-09-08 19:36:30.182 - error: host.rock64 No connection to databases possible, restart 2021-09-08 19:36:30.208 - info: host.rock64 iobroker _restart 2021-09-08 19:36:33.852 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controller starting 2021-09-08 19:36:33.867 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 19:36:33.869 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 19:36:33.871 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596 2021-09-08 19:37:03.926 - error: host.rock64 No connection to databases possible, restart 2021-09-08 19:37:03.952 - info: host.rock64 iobroker _restart 2021-09-08 19:37:07.596 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controller starting 2021-09-08 19:37:07.612 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 19:37:07.614 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 19:37:07.616 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596 -
@derrapf Hatten wir das Thema root nicht schon?
Ich bin dann damit auch raus.
-
@thomas-braun
Oh, Mist. Das war keine Absicht.
War wohl noch als Default im Putty eingetragen. Da hab ich nicht aufgepasst.Soll ich mich nochmal als User "Pi" anmelden und das Ganze nochmal machen?
Würde das was an der Situation ändern?Gruss Ralf
-
Ich habe mich jetz als User "pi" angemeldet und Deine Befehlsfolge nochmal ausgeführt.
pi@rock64:~$ iobroker stop pi@rock64:~$ iobroker start pi@rock64:~$ sudo systemctl stop redis [sudo] Passwort für pi: pi@rock64:~$ sudo apt update OK:1 http://security.debian.org buster/updates InRelease OK:2 http://deb.debian.org/debian buster InRelease OK:3 http://deb.debian.org/debian buster-updates InRelease OK:4 http://deb.debian.org/debian buster-backports InRelease OK:5 https://deb.nodesource.com/node_12.x buster InRelease Holen:6 http://armbian.12z.eu/apt buster InRelease [18,3 kB] Holen:7 http://armbian.12z.eu/apt buster/main arm64 Packages [258 kB] Holen:8 http://armbian.12z.eu/apt buster/main armhf Packages [219 kB] Holen:9 http://armbian.12z.eu/apt buster/main arm64 Contents (deb) [18,3 MB] Holen:10 http://armbian.12z.eu/apt buster/buster-utils arm64 Packages [137 kB] Holen:11 http://armbian.12z.eu/apt buster/buster-utils armhf Packages [98,8 kB] Es wurden 19,1 MB in 21 s geholt (894 kB/s). Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Aktualisierung für 11 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen. pi@rock64:~$ pi@rock64:~$ sudo apt install redis --reinstall Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig 0 aktualisiert, 0 neu installiert, 1 erneut installiert, 0 zu entfernen und 11 nicht aktualisiert. Es müssen 45,3 kB an Archiven heruntergeladen werden. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Holen:1 http://deb.debian.org/debian buster/main arm64 redis all 5:5.0.3-4+deb10u3 [45,3 kB] Es wurden 45,3 kB in 0 s geholt (646 kB/s). (Lese Datenbank ... 49692 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../redis_5%3a5.0.3-4+deb10u3_all.deb ... Entpacken von redis (5:5.0.3-4+deb10u3) über (5:5.0.3-4+deb10u3) ... redis (5:5.0.3-4+deb10u3) wird eingerichtet ... pi@rock64:~$ iobroker start pi@rock64:~$ tail -f /opt/iobroker/log/iobroker iobroker.2021-09-08.log iobroker-audit.json iobroker.current.log pi@rock64:~$ tail -f /opt/iobroker/log/iobroker/iobroker.current.log tail: '/opt/iobroker/log/iobroker/iobroker.current.log' kann nicht zum Lesen geöffnet werden: Datei oder Verzeichnis nicht gefunden tail: Keine Dateien mehr übrig pi@rock64:~$ tail -f /opt/iobroker/log/iobroker iobroker.2021-09-08.log iobroker-audit.json iobroker.current.log pi@rock64:~$ tail -f /opt/iobroker/log/iobroker. iobroker.2021-09-08.log iobroker.current.log pi@rock64:~$ tail -f /opt/iobroker/log/iobroker. iobroker.2021-09-08.log iobroker.current.log pi@rock64:~$ tail -f /opt/iobroker/log/iobroker.current.log 2021-09-08 19:48:18.362 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 19:48:18.364 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596 2021-09-08 19:48:48.419 - error: host.rock64 No connection to databases possible, restart 2021-09-08 19:48:48.446 - info: host.rock64 iobroker _restart 2021-09-08 19:48:52.095 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controller starting 2021-09-08 19:48:52.111 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 19:48:52.113 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 19:48:52.114 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596 2021-09-08 19:49:22.171 - error: host.rock64 No connection to databases possible, restart 2021-09-08 19:49:22.197 - info: host.rock64 iobroker _restart 2021-09-08 19:49:25.837 - info: host.rock64 iobroker.js-controller version 3.3.15 js-controller starting 2021-09-08 19:49:25.854 - info: host.rock64 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-09-08 19:49:25.856 - info: host.rock64 hostname: rock64, node: v12.22.5 2021-09-08 19:49:25.857 - info: host.rock64 ip addresses: 192.168.111.176 fd5a:a2c9:3d75::239 2003:f4:4f06:7500:be0d:7f9f:c058:cf84 fd5a:a2c9:3d75:0:2ce4:cbc2:54ae:52c4 fe80::93b6:5418:55b1:f596Leider kommt die Meldung " No connection to databases possible, restart" immer noch.
Ich weiss nicht ob es hilft aber ich habe noch eine redis-server.log gefunden in dem ab heute 15:17 Nur noch die Einträge "Internal error in RDB reading function at rdb.c:1797 -> Unknown RDB encoding type 45"
kommen:1307:M 07 Sep 2021 23:46:03.010 * Background saving terminated with success 1307:M 07 Sep 2021 23:49:42.238 * 10000 changes in 60 seconds. Saving... 1307:M 07 Sep 2021 23:49:42.240 * Background saving started by pid 32190 32190:C 07 Sep 2021 23:49:42.570 * DB saved on disk 32190:C 07 Sep 2021 23:49:42.573 * RDB: 1 MB of memory used by copy-on-write 1307:M 07 Sep 2021 23:49:42.643 * Background saving terminated with success 1307:M 07 Sep 2021 23:53:19.268 * 10000 changes in 60 seconds. Saving... 1307:M 07 Sep 2021 23:53:19.271 * Background saving started by pid 6594 6594:C 07 Sep 2021 23:53:19.583 * DB saved on disk 6594:C 07 Sep 2021 23:53:19.585 * RDB: 1 MB of memory used by copy-on-write 1307:M 07 Sep 2021 23:53:19.674 * Background saving terminated with success 1307:M 07 Sep 2021 23:56:55.963 * 10000 changes in 60 seconds. Saving... 1307:M 07 Sep 2021 23:56:55.965 * Background saving started by pid 13505 13505:C 07 Sep 2021 23:56:56.297 * DB saved on disk 13505:C 07 Sep 2021 23:56:56.300 * RDB: 1 MB of memory used by copy-on-write 1307:M 07 Sep 2021 23:56:56.368 * Background saving terminated with success 1307:M 08 Sep 2021 00:00:36.412 * 10000 changes in 60 seconds. Saving... 1307:M 08 Sep 2021 00:00:36.415 * Background saving started by pid 20492 20492:C 08 Sep 2021 00:00:36.825 * DB saved on disk 20492:C 08 Sep 2021 00:00:36.827 * RDB: 1 MB of memory used by copy-on-write 1307:M 08 Sep 2021 00:00:36.919 * Background saving terminated with success 1266:C 08 Sep 2021 15:17:10.814 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1266:C 08 Sep 2021 15:17:10.815 # Redis version=5.0.3, bits=64, commit=00000000, modified=0, pid=1266, just started 1266:C 08 Sep 2021 15:17:10.815 # Configuration loaded _._ _.-``__ ''-._ _.-`` `. `_. ''-._ Redis 5.0.3 (00000000/0) 64 bit .-`` .-```. ```\/ _.,_ ''-._ ( ' , .-` | `, ) Running in standalone mode |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379 | `-._ `._ / _.-' | PID: 1311 `-._ `-._ `-./ _.-' _.-' |`-._`-._ `-.__.-' _.-'_.-'| | `-._`-._ _.-'_.-' | http://redis.io `-._ `-._`-.__.-'_.-' _.-' |`-._`-._ `-.__.-' _.-'_.-'| | `-._`-._ _.-'_.-' | `-._ `-._`-.__.-'_.-' _.-' `-._ `-.__.-' _.-' `-._ _.-' `-.__.-' 1311:M 08 Sep 2021 15:17:10.840 # Server initialized 1311:M 08 Sep 2021 15:17:10.840 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1311:M 08 Sep 2021 15:17:10.840 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. 1311:M 08 Sep 2021 15:17:11.118 # Internal error in RDB reading function at rdb.c:1797 -> Unknown RDB encoding type 45 1346:C 08 Sep 2021 15:17:11.528 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1346:C 08 Sep 2021 15:17:11.528 # Redis version=5.0.3, bits=64, commit=00000000, modified=0, pid=1346, just started 1346:C 08 Sep 2021 15:17:11.528 # Configuration loadedWelches File ist denn genau die redis Datenbank? Kann es sein, dass das auch korrupt ist? Die objects.json und states.json hatten ja auf einmal - quasi über Nacht - 0 Bytes. Ev. ist ja auch das Datenbankfile betroffen. Leider kenn ich mich zu wenig aus um das beurteilen zu können.
Gruss Ralf
-
Ich habe jetzt, weil es nicht funktioniert hat, einfach über
iobroker setup customredis deaktiviert.
Jetzt läuft der iobroker wieder.Die interessante Frage dabei ist: Was hat die Dateien zerissen?
Die letzte Aktion die ich gemacht habe war die VIS View zu editieren.Ich lasse jetzt erst mal redis abgeschaltet, oder sollte man redis so bald wie möglich wieder aktivieren?
Dazu müsste ich es wahrscheinlich erst komplett deinstallieren und wieder installieren da ja der reinstall nicht geklappt hat, oder?
Gruss Ralf
