Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Fehler bei der Migration von jsonl zu redis

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    2.0k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    927

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.2k

Fehler bei der Migration von jsonl zu redis

Scheduled Pinned Locked Moved Error/Bug
redis migration
14 Posts 3 Posters 1.3k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    DLehmann
    wrote on last edited by
    #4

    redis ist im gleich lxc installiert wie iobroker, Standardkonfiguration ohne Änderungen und läuft auch, ist mit redis-cli erreichbar.

    Gestartet habe ich die Migration mit "iobroker setup custom", dort habe ich die notwendige Angaben gemacht (hauptsächlich mit Enter bestätigt, da keine Änderungen notwendig waren)

    Oben genannte Meldung war dann der Abschluss von "iobroker setuo custom".

    Wie ich die Fehlermeldung verstehe, kommen wir gar nicht bis redis sondern brechen bereits vorher ab.

    Ro75R 1 Reply Last reply
    0
    • D DLehmann

      redis ist im gleich lxc installiert wie iobroker, Standardkonfiguration ohne Änderungen und läuft auch, ist mit redis-cli erreichbar.

      Gestartet habe ich die Migration mit "iobroker setup custom", dort habe ich die notwendige Angaben gemacht (hauptsächlich mit Enter bestätigt, da keine Änderungen notwendig waren)

      Oben genannte Meldung war dann der Abschluss von "iobroker setuo custom".

      Wie ich die Fehlermeldung verstehe, kommen wir gar nicht bis redis sondern brechen bereits vorher ab.

      Ro75R Offline
      Ro75R Offline
      Ro75
      wrote on last edited by
      #5

      @dlehmann bitte alle Eingaben zeigen.

      Ro75.

      SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

      D 1 Reply Last reply
      0
      • Ro75R Ro75

        @dlehmann bitte alle Eingaben zeigen.

        Ro75.

        D Offline
        D Offline
        DLehmann
        wrote on last edited by
        #6

        @ro75

        Current configuration:
        - Objects database:
          - Type: jsonl
          - Host/Unix Socket: 127.0.0.1
          - Port: 9001
        - States database:
          - Type: jsonl
          - Host/Unix Socket: 127.0.0.1
          - Port: 9000
        - Data Directory: ../../iobroker-data/
        
        Type of objects DB [(j)sonl, (f)ile, (r)edis, ...], default [jsonl]: r
        
        When Objects and Files are stored in a Redis database please consider the following:
        1. All data will be stored in RAM, make sure to have enough free RAM available!
        2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss!
        3. The Redis persistence files can get big, make sure not to use an SD card to store them.
        
        Host / Unix Socket of objects DB(redis), default[127.0.0.1]: 
        Port of objects DB(redis), default[6379]: 
        Do you use a TLS connection for your "objects" redis-server? [y/N]:
        Type of states DB [(j)sonl, (f)file, (r)edis, ...], default [redis]: 
        Host / Unix Socket of states DB (redis), default[127.0.0.1]: 
        Port of states DB (redis), default[6379]: 
        Do you use a TLS connection for your "states" redis-server? [y/N]:
        Host name of this machine [iobroker]: 
        Please choose if this is a Master/single host (enter "m") or a Slave host (enter "S") you are about to edit. For Slave hosts the data migration will be skipped. [S/m]: m
        
        Important: Using redis for the Objects database is only supported
        with js-controller 2.0 or higher!
        When your system consists of multiple hosts please make sure to have
        js-controller 2.0 or higher installed on ALL hosts *before* continuing!
        
        
        Important #2: If you already did the migration on an other host
        please *do not* migrate again! This can destroy your system!
        
        
        Important #3: The process will migrate all files that were officially
        uploaded into the ioBroker system. If you have manually copied files into
        iobroker-data/files/... into own directories then these files will NOT be
        migrated! Make sure all files are in adapter directories inside the files
        directory!
        
        
        Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y/N]: y
        
        Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y
        
        Connecting to previous DB "jsonl/jsonl"...
        Creating backup ...
        This can take some time ... please be patient!
        host.iobroker 15067 objects saved
        host.iobroker 12330 states saved
        host.iobroker Validating backup ...
        host.iobroker Backup not created: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
        Uncaught Rejection: IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
            at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
            at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36
        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(). The promise rejected with the reason:
        IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
            at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
            at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36
        
        Ro75R 1 Reply Last reply
        0
        • D DLehmann

          @ro75

          Current configuration:
          - Objects database:
            - Type: jsonl
            - Host/Unix Socket: 127.0.0.1
            - Port: 9001
          - States database:
            - Type: jsonl
            - Host/Unix Socket: 127.0.0.1
            - Port: 9000
          - Data Directory: ../../iobroker-data/
          
          Type of objects DB [(j)sonl, (f)ile, (r)edis, ...], default [jsonl]: r
          
          When Objects and Files are stored in a Redis database please consider the following:
          1. All data will be stored in RAM, make sure to have enough free RAM available!
          2. Make sure to check Redis persistence options to make sure a Redis problem will not cause data loss!
          3. The Redis persistence files can get big, make sure not to use an SD card to store them.
          
          Host / Unix Socket of objects DB(redis), default[127.0.0.1]: 
          Port of objects DB(redis), default[6379]: 
          Do you use a TLS connection for your "objects" redis-server? [y/N]:
          Type of states DB [(j)sonl, (f)file, (r)edis, ...], default [redis]: 
          Host / Unix Socket of states DB (redis), default[127.0.0.1]: 
          Port of states DB (redis), default[6379]: 
          Do you use a TLS connection for your "states" redis-server? [y/N]:
          Host name of this machine [iobroker]: 
          Please choose if this is a Master/single host (enter "m") or a Slave host (enter "S") you are about to edit. For Slave hosts the data migration will be skipped. [S/m]: m
          
          Important: Using redis for the Objects database is only supported
          with js-controller 2.0 or higher!
          When your system consists of multiple hosts please make sure to have
          js-controller 2.0 or higher installed on ALL hosts *before* continuing!
          
          
          Important #2: If you already did the migration on an other host
          please *do not* migrate again! This can destroy your system!
          
          
          Important #3: The process will migrate all files that were officially
          uploaded into the ioBroker system. If you have manually copied files into
          iobroker-data/files/... into own directories then these files will NOT be
          migrated! Make sure all files are in adapter directories inside the files
          directory!
          
          
          Do you want to migrate objects and states from "jsonl/jsonl" to "redis/redis" [y/N]: y
          
          Migrating the objects database will overwrite all objects! Are you sure that this is not a slave host and you want to migrate the data? [y/N]: y
          
          Connecting to previous DB "jsonl/jsonl"...
          Creating backup ...
          This can take some time ... please be patient!
          host.iobroker 15067 objects saved
          host.iobroker 12330 states saved
          host.iobroker Validating backup ...
          host.iobroker Backup not created: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
          Uncaught Rejection: IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
              at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
              at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36
          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(). The promise rejected with the reason:
          IoBrokerError: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/tmp/backup/config.json'
              at BackupRestore.createBackup (file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupBackup.ts:382:19)
              at file:///opt/iobroker/node_modules/@iobroker/js-controller-cli/src/lib/setup/setupSetup.ts:597:36
          
          Ro75R Offline
          Ro75R Offline
          Ro75
          wrote on last edited by
          #7

          @dlehmann ioBroker zuvor gestoppt? Und das Custom Setup nicht als oder mit root oder sudo gestartet?

          Ro75.

          SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

          D 1 Reply Last reply
          0
          • Ro75R Ro75

            @dlehmann ioBroker zuvor gestoppt? Und das Custom Setup nicht als oder mit root oder sudo gestartet?

            Ro75.

            D Offline
            D Offline
            DLehmann
            wrote on last edited by
            #8

            @ro75 jawohl

            Ro75R 1 Reply Last reply
            0
            • D DLehmann

              @ro75 jawohl

              Ro75R Offline
              Ro75R Offline
              Ro75
              wrote on last edited by
              #9

              @dlehmann wie kommst du auf

              js-controller           7.0.0
              

              ???

              Ro75.

              SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

              D 1 Reply Last reply
              0
              • Ro75R Ro75

                @dlehmann wie kommst du auf

                js-controller           7.0.0
                

                ???

                Ro75.

                D Offline
                D Offline
                DLehmann
                wrote on last edited by
                #10

                @ro75 ist aktuell im Beta

                Ro75R HomoranH 2 Replies Last reply
                0
                • D DLehmann

                  @ro75 ist aktuell im Beta

                  Ro75R Offline
                  Ro75R Offline
                  Ro75
                  wrote on last edited by
                  #11

                  @dlehmann Sorry, aber für meine Begriffe macht man solche Sachen nicht mit Beta.

                  Ro75.

                  SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                  1 Reply Last reply
                  1
                  • D DLehmann

                    @ro75 ist aktuell im Beta

                    HomoranH Do not disturb
                    HomoranH Do not disturb
                    Homoran
                    Global Moderator Administrators
                    wrote on last edited by Homoran
                    #12

                    @dlehmann sagte in Fehler bei der Migration von jsonl zu redis:

                    ist aktuell im Beta

                    dann melde das mal im Tester-Thread und nicht hier als Bug
                    Deswegen ist die Version ja noch Beta!

                    kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                    D 1 Reply Last reply
                    0
                    • HomoranH Homoran

                      @dlehmann sagte in Fehler bei der Migration von jsonl zu redis:

                      ist aktuell im Beta

                      dann melde das mal im Tester-Thread und nicht hier als Bug
                      Deswegen ist die Version ja noch Beta!

                      D Offline
                      D Offline
                      DLehmann
                      wrote on last edited by
                      #13

                      @homoran getan

                      HomoranH 1 Reply Last reply
                      0
                      • D DLehmann

                        @homoran getan

                        HomoranH Do not disturb
                        HomoranH Do not disturb
                        Homoran
                        Global Moderator Administrators
                        wrote on last edited by
                        #14

                        @dlehmann sagte in Fehler bei der Migration von jsonl zu redis:

                        @homoran getan

                        Dann mach ich hier zu!

                        kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

                        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        783

                        Online

                        32.6k

                        Users

                        82.2k

                        Topics

                        1.3m

                        Posts
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                        ioBroker Community 2014-2025
                        logo
                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Home
                        • Recent
                        • Tags
                        • Unread 0
                        • Categories
                        • Unreplied
                        • Popular
                        • GitHub
                        • Docu
                        • Hilfe