Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Migration Pi4 > Synology Docker

    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

    Migration Pi4 > Synology Docker

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

      @glasfaser auf dem Pi:

      pi@iobrokerpi:~ $ sudo redis-server -v
      Redis server v=5.0.14 sha=00000000:0 malloc=libc bits=32 build=ddd3b1f304a7d4d5
      

      In dem Container:

      root@iobrokerpi:/opt/iobroker# redis-server -v                                                        
      bash: redis-server: command not found
      
      Glasfaser 1 Reply Last reply Reply Quote 0
      • Glasfaser
        Glasfaser @Basti81 last edited by

        @basti81

        https://github.com/buanet/ioBroker.docker/issues/136#issuecomment-710220772

        N1tan created this issue in buanet/ioBroker.docker

        closed Iobroker don’t start with Redis #136

        B 1 Reply Last reply Reply Quote 0
        • B
          Basti81 @Glasfaser last edited by

          @glasfaser den Container habe ich über die GUI aktiviert und das gibt es nur diese ENV:
          Unbenannt.png

          Glasfaser 1 Reply Last reply Reply Quote 0
          • Glasfaser
            Glasfaser @Basti81 last edited by

            @basti81 sagte in Migration Pi4 > Synology Docker:

            das gibt es nur diese ENV:

            Ja das ist der Standart ,

            extras siehe hier unter :

            Configuration via environment variables

            https://hub.docker.com/r/buanet/iobroker

            B 1 Reply Last reply Reply Quote 0
            • B
              Basti81 @Glasfaser last edited by

              @glasfaser wir kommen der Sache näher 🙂

              -------------------------------------------------
              -----             Step 3 of 5: Checking ioBroker installation              -----
              --------------------------------------------------------------------------------
               
              (Re)setting permissions (This might take a while! Please be patient!)... Done.
               
              Fixing "sudo-bug" by replacing sudo with gosu... Done.
               
              [DEBUG] Checking multihost settings... 
              [DEBUG] No multihost settings detected.
              [DEBUG] Done.
               
              Configuring custom objects db...
              IOB_OBJECTSDB_TYPE is available and value meets detected ioBroker installation.
              IOB_OBJECTSDB_HOST is available and value meets detected ioBroker installation.
              IOB_OBJECTSDB_PORT is available and value meets detected ioBroker installation.
              Done.
               
              Configuring custom states db...
              IOB_STATESDB_TYPE is available and value meets detected ioBroker installation.
              IOB_STATESDB_HOST is available and value meets detected ioBroker installation.
              IOB_STATESDB_PORT is available but value is different from detected ioBroker installation.
              Setting port of states db to "9000"... Done.
              Done.
               
              Checking Database connection... Failed.
              [DEBUG] Error message: 
              [DEBUG] No connection to objects 127.0.0.1:9001[redis]
              Please check your configuration and try again.
              For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
               
              [DEBUG] Debug mode prevents the container from exiting on errors.
              [DEBUG] This enables you to investigate or fix your issue on the command line.
              [DEBUG] If you want to stop or restart your container you have to do it manually.
              [DEBUG] IoBroker is not running!
              

              Unbenannt2.png

              Glasfaser 2 Replies Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @Basti81 last edited by Glasfaser

                @basti81 sagte in Migration Pi4 > Synology Docker:

                No connection to objects 127.0.0.1:9001[redis]

                Warum 9001

                @basti81 sagte in Migration Pi4 > Synology Docker:
                [DEBUG] No connection to states 0.0.0.0:6379[redis]

                B 1 Reply Last reply Reply Quote 0
                • Glasfaser
                  Glasfaser @Basti81 last edited by

                  @basti81

                  zu Redis auch :

                  https://smarthome.buanet.de/2020/12/iobroker-docker-container-mit-redis-db-verbinden/

                  1 Reply Last reply Reply Quote 0
                  • B
                    Basti81 @Glasfaser last edited by

                    @glasfaser hab jetzt den 6379 versucht und ich bekomme den gleichen Fehler:

                    -----------------------------------------------
                    -----             Step 3 of 5: Checking ioBroker installation              -----
                    --------------------------------------------------------------------------------
                     
                    (Re)setting permissions (This might take a while! Please be patient!)... Done.
                     
                    Fixing "sudo-bug" by replacing sudo with gosu... Done.
                     
                    [DEBUG] Checking multihost settings... 
                    [DEBUG] No multihost settings detected.
                    [DEBUG] Done.
                     
                    Configuring custom objects db...
                    IOB_OBJECTSDB_TYPE is available and value meets detected ioBroker installation.
                    IOB_OBJECTSDB_HOST is available and value meets detected ioBroker installation.
                    IOB_OBJECTSDB_PORT is available but value is different from detected ioBroker installation.
                    Setting port of objects db to "6379"... Done.
                    Done.
                     
                    Configuring custom states db...
                    IOB_STATESDB_TYPE is available and value meets detected ioBroker installation.
                    IOB_STATESDB_HOST is available and value meets detected ioBroker installation.
                    IOB_STATESDB_PORT is available but value is different from detected ioBroker installation.
                    Setting port of states db to "6379"... Done.
                    Done.
                     
                    Checking Database connection... Failed.
                    [DEBUG] Error message: 
                    [DEBUG] No connection to objects 127.0.0.1:6379[redis]
                    Please check your configuration and try again.
                    For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
                     
                    [DEBUG] Debug mode prevents the container from exiting on errors.
                    [DEBUG] This enables you to investigate or fix your issue on the command line.
                    [DEBUG] If you want to stop or restart your container you have to do it manually.
                    [DEBUG] IoBroker is not running!
                    

                    Soll ich mal:
                    apt-get install redis-sentinel

                    im Container ausführen? Mich wundert das hier im Container:

                    root@iobrokerpi:/opt/iobroker# redis-server -v                                                        
                    bash: redis-server: command not found
                    
                    Glasfaser 1 Reply Last reply Reply Quote 0
                    • Glasfaser
                      Glasfaser @Basti81 last edited by Glasfaser

                      @basti81 sagte in Migration Pi4 > Synology Docker:

                      im Container ausführen?

                      kannst du machen ... aber beim nächsten Image wechsel ist er weg !

                      siehe meinen Link , da ist redis seperat als Container !

                      B 1 Reply Last reply Reply Quote 0
                      • B
                        Basti81 @Glasfaser last edited by

                        @glasfaser danke dir. Habe die Container sauber neu aufgesetzt wie hier erläutert:
                        https://smarthome.buanet.de/2020/12/iobroker-docker-container-mit-redis-db-verbinden/

                        Alles läuft nun wie es soll und der Restore hat geklappt da die redis Verbindung von Anfang an funktionierte. Bridged Network war hier der Schlüssel. Mit Host network hat es nicht geklappt.

                        Danke dir!!!

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

                        Support us

                        ioBroker
                        Community Adapters
                        Donate
                        FAQ Cloud / IOT
                        HowTo: Node.js-Update
                        HowTo: Backup/Restore
                        Downloads
                        BLOG

                        803
                        Online

                        31.7k
                        Users

                        79.8k
                        Topics

                        1.3m
                        Posts

                        3
                        21
                        1532
                        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