Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Backup/Restore von Raspberry auf Intel Nuc schlägt fehl

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Backup/Restore von Raspberry auf Intel Nuc schlägt fehl

    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      Belei last edited by

      Hallo ich versuche seit Tagen von meinem noch laufendem System ein Backup zu erstellen und es auf meinem neuen Intel Nuc unter Proxmox zum laufen zu bekommen. Auf dem Nuc läuft /proxmox/Debian

      Das Backup hab ich manuell erstellt (iobroker backup) oder auch schon per Backitup Adapter, beides scheint zu klappen. Das Backup kopiere ich dann auf den Nuc in verzeichniss opt/iobroker/backups und habe es umbenannt in io.tar.gz (war in einem anderen Thread die Lösung)

      der iobroker ist gestoppt und ich gebe folgendes ein:

      root@ioBrokerNuc:/opt/iobroker# iobroker restore /opt/iobroker/backups/io.tar.gz
      host.ioBrokerNuc Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json"
      
      

      Gleiches Ergebniss bei Restore 0

      Manchmal ist die Fehlermeldung auch länger aber ähnlich:

      root@ioBrokerNuc:/opt/iobroker# sudo iobroker restore io.tar.gz
      host.ioBrokerNuc Cannot find /opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../../../backups/io.tar.gz_backupiobroker.tar.gz
      
      

      Raspberry:

          Plattform: linux
          Die Architektur: arm
          CPUs: 4
          Geschwindigkeit: 1200 MHz
          Modell: ARMv7 Processor rev 4 (v7l)
          RAM: 927.3 MB
          System uptime: 00:19:20
          Node.js: v8.12.0
          NPM: 6.4.1
          Adapter zählen: 229
          Uptime: 00:56:25
      

      Intel Nuc:

      Platform: linux
      Architecture: x64
      CPUs: 4
      Speed: 1497 MHz
      Model: Common KVM processor
      RAM: 1.9 GB 
      System uptime: 00:42:41
      Node.js: v8.12.0
      adapters count: 229
      NPM: v6.4.1
      Uptime: 00:00:11
      
      1 Reply Last reply Reply Quote 0
      • simatec
        simatec Developer Most Active last edited by

        Erstelle mal ein Backup und benenne es nicht um.

        Danach dann auf deinem neuen System in /opt/iobrocker den Ordner backups erstellen, das backup dort ablegen und "sudo iobroker restore 0" ausführen.

        1 Reply Last reply Reply Quote 0
        • B
          Belei last edited by

          Hab ich schon probiert, aber gerade nochmal:

          ` > root@ioBrokerNuc:~# cd /opt/iobroker

          root@ioBrokerNuc:/opt/iobroker# sudo iobroker restore 0

          host.ioBrokerNuc Using backup file total_2018_11_06-03_00_18_backupiobroker.tar.gz

          host.ioBrokerNuc Cannot find extracted file from file "/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/backup.json" `

          Er findet das Backup aber bricht mit dem gleichen Fehler ab.

          1 Reply Last reply Reply Quote 0
          • T
            Turbo last edited by

            Bei mir hat es so funktioniert:

            • Manuelles Backup mit dem NUC erstellen

            • Backup vom Raspberry umbenennen mit Backup-Namen vom NUC

            • Backup von NUC löschen und Backup vom Raspberry reinkopieren

            • Restore

            Vielleicht klappts…

            1 Reply Last reply Reply Quote 0
            • B
              Belei last edited by

              Manuelles Backup einspielen mit namen ändern hat jetzt geklappt, war zwar nur paar MB groß? Aber er hat wenigsten mal was gemacht 😄

              Aber leider startet iobroker Weboberfläche jetzt nicht auf dem Nuc.

              Der Deamon läuft und JS Controller auch aber ich hab kein Zugriff?

              root@ioBrokerNuc:/opt/iobroker# ps -A | grep iobroker
                749 ?        00:00:02 iobroker.js-con
              
              
               node node_modules/iobroker.js-controller/controller.js --logs
               root@ioBrokerNuc:/opt/iobroker#  node node_modules/iobroker.js-controller/controller.js --logs
              
              2018-11-11 12:17:47.886  - info: host.ioBrokerNuc iobroker.js-controller version             1.4.2 js-controller starting
              2018-11-11 12:17:47.890  - info: host.ioBrokerNuc Copyright (c) 2014-2018 bluefo            x, 2014 hobbyquaker
              2018-11-11 12:17:47.891  - info: host.ioBrokerNuc hostname: ioBrokerNuc, node: v            8.12.0
              2018-11-11 12:17:47.894  - info: host.ioBrokerNuc ip addresses: 192.168.178.38 f            e80::30d2:24ff:fe74:ac79
              2018-11-11 12:17:48.288  - info: host.ioBrokerNuc  inMem-objects listening on po            rt 9001
              2018-11-11 12:17:48.301  - error: Another instance is running or some applicatio            n uses port!
              2018-11-11 12:17:48.301  - error: uncaught exception: listen EADDRINUSE 0.0.0.0:            9001
              2018-11-11 12:17:48.307  - info: iobroker _restart
              2018-11-11 12:17:48.398  - info: host.ioBrokerNuc InMemoryDB connected
              2018-11-11 12:17:48.420  - info: host.ioBrokerNuc 30 instances found
              host.ioBrokerNuc check instance "system.adapter.admin.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.discovery.0" for host "ioBrokerN            uc"
              host.ioBrokerNuc check instance "system.adapter.hm-rpc.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.hm-rega.0" for host "ioBrokerNuc            "
              host.ioBrokerNuc check instance "system.adapter.web.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.vis.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.history.0" for host "ioBrokerNuc            "
              host.ioBrokerNuc check instance "system.adapter.mobile.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.javascript.0" for host "ioBroker            Nuc"
              host.ioBrokerNuc check instance "system.adapter.hm-rpc.1" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.hm-rpc.3" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.fhem.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.cloud.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.rflink.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.pushover.0" for host "ioBrokerNu            c"
              host.ioBrokerNuc check instance "system.adapter.tr-064.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.tr-064.1" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.tr-064.2" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.amazon-dash.0" for host "ioBroke            rNuc"
              host.ioBrokerNuc check instance "system.adapter.alexa2.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.backitup.0" for host "ioBrokerNu            c"
              host.ioBrokerNuc check instance "system.adapter.feiertage.0" for host "ioBrokerN            uc"
              host.ioBrokerNuc check instance "system.adapter.fritzdect.0" for host "ioBrokerN            uc"
              host.ioBrokerNuc check instance "system.adapter.weatherunderground.0" for host "            ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.ble.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.radar.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.zigbee.0" for host "ioBrokerNuc"
              host.ioBrokerNuc check instance "system.adapter.vis-timeandweather.0" for host "            ioBrokerNuc"
              2018-11-11 12:17:48.443  - info: host.ioBrokerNuc starting 1 instance
              2018-11-11 12:17:48.454  - warn: host.ioBrokerNuc startInstance cannot find adap            ter "vis-timeandweather". Try to install it... 1 attempt
              2018-11-11 12:17:48.454  - info: iobroker install vis-timeandweather
              2018-11-11 12:17:48.480  - info: host.ioBrokerNuc instance system.adapter.admin.            0 started with pid 832
              2018-11-11 12:17:48.631  - info: iobroker Starting node restart.js
              2018-11-11 12:17:48.645  - info: iobroker exit 0
              [b]2018-11-11 12:17:51.010  - info: iobroker No connection to states 0.0.0.0:6379[redis][/b]
              2018-11-11 12:17:51.015  - info: iobroker exit 22
              
              
              1 Reply Last reply Reply Quote 0
              • simatec
                simatec Developer Most Active last edited by

                Du kannst mit dem Befehl sudo iobroker restore 0 kein total backup herstellen.

                Das geht nur mit dem minimal.

                Total sichert den kompletten iob Ordner in einem Archiv.

                Minimal ist das Standard Backup von iob.

                Gesendet von iPhone mit Tapatalk

                1 Reply Last reply Reply Quote 0
                • B
                  Belei last edited by

                  Achso! Ja super mit dem Minimal Backup klappt auch der Restore aber leider startet dann der Broker nicht mehr??

                  root@ioBrokerNuc:/opt/iobroker# iobroker start all
                  No connection to states 0.0.0.0:6379[redis]
                  root@ioBrokerNuc:/opt/iobroker# sudo iobroker start
                  Starting iobroker controller daemon...
                  iobroker controller daemon started. PID: 1114
                  
                  

                  Also gestartet wird er aber ich hab kein Zugriff auf die Weboberfläche

                  1 Reply Last reply Reply Quote 0
                  • H
                    holgerwolf last edited by

                    Das kann dauern, weil erst noch alle Adapter neu installiert/eingerichtet werden müssen.

                    Schau dir mal die Log Datei an. Da siehst du, was gerade passiert.

                    Gruß

                    Holger

                    1 Reply Last reply Reply Quote 0
                    • B
                      Belei last edited by

                      6 Stunden später immer noch nix….. kein zugriff auf adminpage(komplett Weboberfläche)

                      Hab den Log mal per ftp geöffnet: Folgende Fehlermeldung werden ausgegeben:

                      2018-11-14 17:04:14.922  - [32minfo[39m: host.debian instance system.adapter.admin.0 started with pid 1096
                      2018-11-14 17:04:17.550  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:17.563  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:18.565  - [33mwarn[39m: host.debian startInstance cannot find adapter "icons-ultimate-png". Try to install it... 1 attempt
                      2018-11-14 17:04:18.565  - [32minfo[39m: iobroker install icons-ultimate-png
                      2018-11-14 17:04:21.256  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:21.265  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:22.267  - [33mwarn[39m: host.debian startInstance cannot find adapter "hm-rpc". Try to install it... 1 attempt
                      2018-11-14 17:04:22.267  - [32minfo[39m: iobroker install hm-rpc
                      2018-11-14 17:04:24.959  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:24.967  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:25.969  - [33mwarn[39m: host.debian startInstance cannot find adapter "hm-rega". Try to install it... 1 attempt
                      2018-11-14 17:04:25.970  - [32minfo[39m: iobroker install hm-rega
                      2018-11-14 17:04:28.679  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:28.686  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:29.687  - [33mwarn[39m: host.debian startInstance cannot find adapter "web". Try to install it... 1 attempt
                      2018-11-14 17:04:29.688  - [32minfo[39m: iobroker install web
                      2018-11-14 17:04:32.388  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:32.396  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:33.398  - [33mwarn[39m: host.debian startInstance cannot find adapter "vis". Try to install it... 1 attempt
                      2018-11-14 17:04:33.398  - [32minfo[39m: iobroker install vis
                      2018-11-14 17:04:36.099  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:36.109  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:37.112  - [33mwarn[39m: host.debian startInstance cannot find adapter "history". Try to install it... 1 attempt
                      2018-11-14 17:04:37.113  - [32minfo[39m: iobroker install history
                      2018-11-14 17:04:39.800  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:39.810  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:40.812  - [33mwarn[39m: host.debian startInstance cannot find adapter "mobile". Try to install it... 1 attempt
                      2018-11-14 17:04:40.813  - [32minfo[39m: iobroker install mobile
                      2018-11-14 17:04:43.502  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:43.558  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:44.560  - [33mwarn[39m: host.debian startInstance cannot find adapter "javascript". Try to install it... 1 attempt
                      2018-11-14 17:04:44.561  - [32minfo[39m: iobroker install javascript
                      2018-11-14 17:04:47.250  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:47.259  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:48.261  - [33mwarn[39m: host.debian startInstance cannot find adapter "hm-rpc". Try to install it... 1 attempt
                      2018-11-14 17:04:48.262  - [32minfo[39m: iobroker install hm-rpc
                      2018-11-14 17:04:50.957  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:50.966  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:51.968  - [33mwarn[39m: host.debian startInstance cannot find adapter "hm-rpc". Try to install it... 1 attempt
                      2018-11-14 17:04:51.968  - [32minfo[39m: iobroker install hm-rpc
                      2018-11-14 17:04:54.659  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:54.713  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:55.716  - [33mwarn[39m: host.debian startInstance cannot find adapter "fhem". Try to install it... 1 attempt
                      2018-11-14 17:04:55.716  - [32minfo[39m: iobroker install fhem
                      2018-11-14 17:04:58.404  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:04:58.413  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:04:59.417  - [33mwarn[39m: host.debian startInstance cannot find adapter "cloud". Try to install it... 1 attempt
                      2018-11-14 17:04:59.417  - [32minfo[39m: iobroker install cloud
                      2018-11-14 17:05:02.111  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:02.125  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:03.126  - [33mwarn[39m: host.debian startInstance cannot find adapter "rflink". Try to install it... 1 attempt
                      2018-11-14 17:05:03.127  - [32minfo[39m: iobroker install rflink
                      2018-11-14 17:05:05.818  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:05.826  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:06.827  - [33mwarn[39m: host.debian startInstance cannot find adapter "pushover". Try to install it... 1 attempt
                      2018-11-14 17:05:06.828  - [32minfo[39m: iobroker install pushover
                      2018-11-14 17:05:09.522  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:09.531  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:10.534  - [33mwarn[39m: host.debian startInstance cannot find adapter "tr-064". Try to install it... 1 attempt
                      2018-11-14 17:05:10.534  - [32minfo[39m: iobroker install tr-064
                      2018-11-14 17:05:13.233  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:13.240  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:14.242  - [33mwarn[39m: host.debian startInstance cannot find adapter "tr-064". Try to install it... 1 attempt
                      2018-11-14 17:05:14.242  - [32minfo[39m: iobroker install tr-064
                      2018-11-14 17:05:16.934  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:16.944  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:17.946  - [33mwarn[39m: host.debian startInstance cannot find adapter "tr-064". Try to install it... 1 attempt
                      2018-11-14 17:05:17.946  - [32minfo[39m: iobroker install tr-064
                      2018-11-14 17:05:20.634  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:20.646  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:21.649  - [33mwarn[39m: host.debian startInstance cannot find adapter "amazon-dash". Try to install it... 1 attempt
                      2018-11-14 17:05:21.652  - [32minfo[39m: iobroker install amazon-dash
                      2018-11-14 17:05:24.362  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:24.370  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:25.372  - [33mwarn[39m: host.debian startInstance cannot find adapter "flot". Try to install it... 2 attempt
                      2018-11-14 17:05:25.372  - [32minfo[39m: iobroker install flot
                      2018-11-14 17:05:28.076  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:28.084  - [32minfo[39m: iobroker exit 22
                      2018-11-14 17:05:29.086  - [33mwarn[39m: host.debian startInstance cannot find adapter "alexa2". Try to install it... 1 attempt
                      2018-11-14 17:05:29.086  - [32minfo[39m: iobroker install alexa2
                      2018-11-14 17:05:31.783  - [32minfo[39m: iobroker No connection to states 0.0.0.0:6379[redis]
                      2018-11-14 17:05:31.791  - [32minfo[39m: iobroker exit 22
                      
                      
                      32minfo[39m: host.debian stopInstance system.adapter.fritzdect.0
                      2018-11-14 18:04:17.519  - [33mwarn[39m: host.debian stopInstance system.adapter.fritzdect.0 not running
                      2018-11-14 18:04:17.525  - [32minfo[39m: iobroker _restart
                      2018-11-14 18:04:17.533  - [31merror[39m: host.debian No redis connection!
                      2018-11-14 18:04:17.536  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.537  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.538  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.538  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.539  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.539  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.540  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.540  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.541  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.541  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.541  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.542  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.542  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.543  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.543  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.544  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.544  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.544  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.545  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.545  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.545  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.548  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.548  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.548  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.548  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.553  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.553  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.554  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.554  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.554  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      2018-11-14 18:04:17.554  - [33mwarn[39m: host.debian AbortError: Redis connection in broken state: connection timeout exceeded.
                      
                      
                      1 Reply Last reply Reply Quote 0
                      • arteck
                        arteck Developer Most Active last edited by

                        hast du Redis installiert.. so wie es aussieht nicht

                        host.debian No redis connection!
                        
                        1 Reply Last reply Reply Quote 0
                        • M
                          markuskobe last edited by

                          Hi, hast du es gelöst bekommen? Ich habe jetzt das gleiche Problem...und ich bin mir sicher, dass ich auf dem alten System kein REDIS hatte...laut Doku ist da auch kein REDIS drauf gewesen, siehe Bild
                          Anmerkung 2019-04-10 010215.jpg

                          Kann ich irgendwie per Kommandozeile prüfen, ob auf dem "Alt-System" doch REDIS installiert ist...

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          838
                          Online

                          31.8k
                          Users

                          80.0k
                          Topics

                          1.3m
                          Posts

                          6
                          11
                          3923
                          Loading More Posts
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes
                          Reply
                          • Reply as topic
                          Log in to reply
                          Community
                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                          The ioBroker Community 2014-2023
                          logo