Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [HowTo] ioBroker Restore unter Linux durchführen

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    [HowTo] ioBroker Restore unter Linux durchführen

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

      @ronny-gerndt
      Ich hatte das gleiche Problem und bei mir lag es am admin Adapter. Bei der Version 6.2.22 war es das Problem, dass man Datenpunkte nicht löschen konnte. Es sollte aber mit der 6.2.23 behoben sein.

      1 Reply Last reply Reply Quote 0
      • C
        chris299 @simatec last edited by

        @simatec vielen Dank für die Anleitung zum Restore.

        Im Folgenden meine Erfahrungen beim Restore auf einem anderen Host mit einem anderen Betriebssystem (von einer multi-Host Installation mit Mac Mini als Master auf einen Ubuntu Server single-host).
        Ein paar Hinweise für dieses Szenario sollten evtl. in die Anleitung aufgenommen werden.

        1. Problem
          restore setzt die IP des multihost master in die single host installation mit dem Ergebnis, dass nichts geschrieben werden kann.
          Lösung: multihost umgebung wieder zu single host machen und die IP der JSON wieder auf 127.0.0.1 und neues Backup machen....

        2. Problem
          die Adapter installation läuft für VIS auf Fehler (aber solche tickets findet man erst nachher):
          https://forum.iobroker.net/topic/57645/fehler-bei-vis-installation-nach-restore
          Lösung: VIS via alte Version installieren & updaten, restore nochmal starten

        3. Problem
          alte Adapter Versionen werden installiert, warum auch immer... 🤔
          Lösung: adapter manuell updaten vor deren start

        4. Problem
          neue usb modem adressen für Zwave- und Zigbee-Dongle (Mac anders als Ubuntu)
          neu:
          /dev/ttyACM0
          /dev/ttyUSB0
          aber welche ist welche?
          Lösung: manuell ausprobieren, und bei Fehler wie dem folgenden, die andere versuchen, weil das dropdown in den adaptern dafür nicht geht. vermutlich weil die ja noch nie gestartet wurden...

        Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200) at Driver.sendMessage (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:4001:23) at ZWaveController.identify (/opt/iobroker/node_modules/zwave-js/src/lib/controller/Controller.ts:776:33) at Driver.initializeControllerAndNodes (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1265:26) at Immediate.<anonymous> (/opt/iobroker/node_modules/zwave-js/src/lib/driver/Driver.ts:1072:16) (ZW0100)

        1. Problem
          "history" Datei-Pfad auf Mac anders und restore versucht den alten Pfad zu erzeugen, was natürlich nicht geht. (der wurde mit dem restore in der adapter konfig wiederhergestellt)
          Lösung: die History dateien manuell in den neuen history Pfad kopieren und Dateirechte für iobroker user setzen. evtl. hätte aber auch eine Korrektur des Pfades in der Backitup-konfiguration gereicht (habe ich aber nicht mehr versucht)

        2. Problem
          neue mqtt server ip für alle shelly devices nötig, da neuer Host mit neuer IP
          Lösung: in jedem manuell ändern... 😞

        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @chris299 last edited by

          @chris299 sagte in [HowTo] ioBroker Restore unter Linux durchführen:

          Problem
          neue usb modem adressen für Zwave- und Zigbee-Dongle (Mac anders als Ubuntu)
          neu:
          /dev/ttyACM0
          /dev/ttyUSB0
          aber welche ist welche?
          Lösung: manuell ausprobieren, und bei Fehler wie dem folgenden, die andere versuchen, weil das dropdown in den adaptern dafür nicht geht. vermutlich weil die ja noch nie gestartet wurden...

          Bessere Lösung: Die Links zu den Dateien aus /dev/serial/by-id nehmen. Die passen nämlich immer.

          C 1 Reply Last reply Reply Quote 0
          • C
            chris299 @Thomas Braun last edited by

            @thomas-braun danke für den Tipp. Allerdings sind die sehr lang bei mir:

            ~$ sudo ls -al /dev/serial/by-id
drwxr-xr-x 2 root root 80 Apr 20 14:13 .
drwxr-xr-x 4 root root 80 Apr 19 22:48 ..
lrwxrwxrwx 1 root root 13 Apr 20 14:13 usb-0658_0200-if00 -> ../../ttyACM0
lrwxrwxrwx 1 root root 13 Apr 19 22:52 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_a45c4ee898c9eb11b94d914f1d69213e-if00-port0 -> ../../ttyUSB0
~$ sudo ls /dev/serial/by-id
usb-0658_0200-if00  usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_a45c4ee898c9eb11b94d914f1d69213e-if00-port0
            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @chris299 last edited by

              @chris299

              Ja, aber macht doch nix? Copy Paste und drin ist der Kram. Der Vorteil ist wie gesagt, dass das Linkziel vom Kernel immer richtig gesetzt wird.

              1 Reply Last reply Reply Quote 0
              • S
                Sebi_7_6 last edited by

                Hallo,

                hab heute mein Raspi neu installiert und IoBroker drauf gemacht. Wollte mein Backup einspiele und er sagt Wiederherstellung wird gestartet dann dreht sich der Kreis und dann ist IoBroker Offline und muss den Dienst erst wieder neustarten! Aber er hat nichts wiederhergestellt?
                Wo liegt hier das Problem?

                Thomas Braun 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Sebi_7_6 last edited by

                  @sebi_7_6 sagte in [HowTo] ioBroker Restore unter Linux durchführen:

                  Wo liegt hier das Problem?

                  Keine Ahnung. Log File sagt?

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    Sebi_7_6 @Thomas Braun last edited by Sebi_7_6

                    @thomas-braun

                    Nix.

                    backitup.0
2023-04-22 18:13:34.853 info [iobroker] backup was activated at 02:40 every 1 day(s)
backitup.0
2023-04-22 18:13:34.561 info starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24
backitup.0
2023-04-22 17:58:20.510 info Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
backitup.0
2023-04-22 17:58:20.476 info Got terminate signal TERMINATE_YOURSELF
backitup.0
2023-04-22 17:58:20.342 info cleaned everything up...
                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Sebi_7_6 last edited by

                      @sebi_7_6
                      Schau per

                      iob logs --watch | uniq

                      dem Backup in der Konsole zu.

                      S 1 Reply Last reply Reply Quote 0
                      • S
                        Sebi_7_6 @Thomas Braun last edited by Sebi_7_6

                        @thomas-braun said in [HowTo] ioBroker Restore unter Linux durchführen:

                        iob logs --watch | uniq

                        irgendwie stoppt er nur alles...Ab 18:23:30 habe ich die Wiederherstellung gestartet.

                        
2023-04-22 18:23:30.999  - info: bring.0 (10071) [END] Stopping Bring! adapter...
2023-04-22 18:23:31.013  - info: host.raspberrypi received SIGTERM
2023-04-22 18:23:31.019  - info: backitup.0 (9766) cleaned everything up...
2023-04-22 18:23:30.999  - info: trashschedule.0 (9969) cleaned everything up...
2023-04-22 18:23:31.033  - info: admin.0 (9373) terminating http server on port 8081
2023-04-22 18:23:31.034  - info: wled.0 (10341) cleaned everything up...
2023-04-22 18:23:31.025  - info: accuweather.0 (9854) cleaned everything up...
2023-04-22 18:23:31.022  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
2023-04-22 18:23:31.025  - info: host.raspberrypi stopInstance system.adapter.alexa2.0 (force=false, process=true)
2023-04-22 18:23:31.028  - info: host.raspberrypi stopInstance system.adapter.ical.0 (force=false, process=false)
2023-04-22 18:23:31.030  - info: host.raspberrypi stopInstance system.adapter.tuya.0 (force=false, process=true)
2023-04-22 18:23:31.033  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
2023-04-22 18:23:31.035  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
2023-04-22 18:23:31.037  - info: host.raspberrypi stopInstance system.adapter.accuweather.0 (force=false, process=true)
2023-04-22 18:23:31.040  - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false)
2023-04-22 18:23:31.047  - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 (force=false, process=true)
2023-04-22 18:23:31.049  - info: host.raspberrypi stopInstance system.adapter.bring.0 (force=false, process=true)
2023-04-22 18:23:31.050  - info: host.raspberrypi stopInstance system.adapter.daswetter.0 (force=false, process=false)
2023-04-22 18:23:31.053  - info: host.raspberrypi stopInstance canceled schedule system.adapter.daswetter.0
2023-04-22 18:23:31.054  - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=true)
2023-04-22 18:23:31.056  - info: host.raspberrypi stopInstance system.adapter.habpanel.0 (force=false, process=false)
2023-04-22 18:23:31.057  - info: host.raspberrypi stopInstance system.adapter.wled.0 (force=false, process=true)
2023-04-22 18:23:31.160  - info: bring.0 (10071) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.182  - info: alexa2.0 (9495) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.188  - info: admin.0 (9373) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.200  - info: backitup.0 (9766) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.202  - info: accuweather.0 (9854) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.208  - info: bring.0 (10071) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.195  - info: tuya.0 (9601) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.205  - info: trashschedule.0 (9969) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.192  - info: alexa2.0 (9495) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.230  - info: web.0 (10270) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.220  - info: wled.0 (10341) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.237  - info: admin.0 (9373) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.224  - info: discovery.0 (9680) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.244  - info: backitup.0 (9766) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.244  - info: wled.0 (10341) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.253  - info: trashschedule.0 (9969) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.276  - info: discovery.0 (9680) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.286  - info: accuweather.0 (9854) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.289  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
2023-04-22 18:23:31.305  - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal
2023-04-22 18:23:31.307  - info: host.raspberrypi stopInstance system.adapter.tuya.0 send kill signal
2023-04-22 18:23:31.309  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
2023-04-22 18:23:31.310  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
2023-04-22 18:23:31.311  - info: host.raspberrypi stopInstance system.adapter.accuweather.0 send kill signal
2023-04-22 18:23:31.312  - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 send kill signal
2023-04-22 18:23:31.313  - info: host.raspberrypi stopInstance system.adapter.bring.0 send kill signal
2023-04-22 18:23:31.314  - info: host.raspberrypi stopInstance system.adapter.web.0 send kill signal
2023-04-22 18:23:31.315  - info: host.raspberrypi stopInstance system.adapter.wled.0 send kill signal
2023-04-22 18:23:31.496  - info: web.0 (10270) terminated http server on port 8082
2023-04-22 18:23:31.510  - info: web.0 (10270) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.808  - info: host.raspberrypi instance system.adapter.bring.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:31.917  - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.107  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.115  - info: host.raspberrypi instance system.adapter.wled.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.227  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.229  - info: host.raspberrypi instance system.adapter.accuweather.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.231  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.272  - info: host.raspberrypi instance system.adapter.trashschedule.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.349  - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:30.999  - info: bring.0 (10071) [END] Stopping Bring! adapter...
2023-04-22 18:23:31.013  - info: host.raspberrypi received SIGTERM
2023-04-22 18:23:31.019  - info: backitup.0 (9766) cleaned everything up...
2023-04-22 18:23:30.999  - info: trashschedule.0 (9969) cleaned everything up...
2023-04-22 18:23:31.033  - info: admin.0 (9373) terminating http server on port 8081
2023-04-22 18:23:31.034  - info: wled.0 (10341) cleaned everything up...
2023-04-22 18:23:31.025  - info: accuweather.0 (9854) cleaned everything up...
2023-04-22 18:23:31.022  - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true)
2023-04-22 18:23:31.025  - info: host.raspberrypi stopInstance system.adapter.alexa2.0 (force=false, process=true)
2023-04-22 18:23:31.028  - info: host.raspberrypi stopInstance system.adapter.ical.0 (force=false, process=false)
2023-04-22 18:23:31.030  - info: host.raspberrypi stopInstance system.adapter.tuya.0 (force=false, process=true)
2023-04-22 18:23:31.033  - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=true)
2023-04-22 18:23:31.035  - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
2023-04-22 18:23:31.037  - info: host.raspberrypi stopInstance system.adapter.accuweather.0 (force=false, process=true)
2023-04-22 18:23:31.040  - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false)
2023-04-22 18:23:31.047  - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 (force=false, process=true)
2023-04-22 18:23:31.049  - info: host.raspberrypi stopInstance system.adapter.bring.0 (force=false, process=true)
2023-04-22 18:23:31.050  - info: host.raspberrypi stopInstance system.adapter.daswetter.0 (force=false, process=false)
2023-04-22 18:23:31.053  - info: host.raspberrypi stopInstance canceled schedule system.adapter.daswetter.0
2023-04-22 18:23:31.054  - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=true)
2023-04-22 18:23:31.056  - info: host.raspberrypi stopInstance system.adapter.habpanel.0 (force=false, process=false)
2023-04-22 18:23:31.057  - info: host.raspberrypi stopInstance system.adapter.wled.0 (force=false, process=true)
2023-04-22 18:23:31.160  - info: bring.0 (10071) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.182  - info: alexa2.0 (9495) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.188  - info: admin.0 (9373) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.200  - info: backitup.0 (9766) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.202  - info: accuweather.0 (9854) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.208  - info: bring.0 (10071) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.195  - info: tuya.0 (9601) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.205  - info: trashschedule.0 (9969) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.192  - info: alexa2.0 (9495) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.230  - info: web.0 (10270) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.220  - info: wled.0 (10341) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.237  - info: admin.0 (9373) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.224  - info: discovery.0 (9680) Got terminate signal TERMINATE_YOURSELF
2023-04-22 18:23:31.244  - info: backitup.0 (9766) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.244  - info: wled.0 (10341) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.253  - info: trashschedule.0 (9969) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.276  - info: discovery.0 (9680) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.286  - info: accuweather.0 (9854) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.289  - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal
2023-04-22 18:23:31.305  - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal
2023-04-22 18:23:31.307  - info: host.raspberrypi stopInstance system.adapter.tuya.0 send kill signal
2023-04-22 18:23:31.309  - info: host.raspberrypi stopInstance system.adapter.discovery.0 send kill signal
2023-04-22 18:23:31.310  - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
2023-04-22 18:23:31.311  - info: host.raspberrypi stopInstance system.adapter.accuweather.0 send kill signal
2023-04-22 18:23:31.312  - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 send kill signal
2023-04-22 18:23:31.313  - info: host.raspberrypi stopInstance system.adapter.bring.0 send kill signal
2023-04-22 18:23:31.314  - info: host.raspberrypi stopInstance system.adapter.web.0 send kill signal
2023-04-22 18:23:31.315  - info: host.raspberrypi stopInstance system.adapter.wled.0 send kill signal
2023-04-22 18:23:31.496  - info: web.0 (10270) terminated http server on port 8082
2023-04-22 18:23:31.510  - info: web.0 (10270) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:31.808  - info: host.raspberrypi instance system.adapter.bring.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:31.917  - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.107  - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.115  - info: host.raspberrypi instance system.adapter.wled.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.227  - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.229  - info: host.raspberrypi instance system.adapter.accuweather.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.231  - info: host.raspberrypi instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.272  - info: host.raspberrypi instance system.adapter.trashschedule.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:32.349  - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:34.043  - info: tuya.0 (9601) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2023-04-22 18:23:34.663  - info: host.raspberrypi instance system.adapter.tuya.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:34.665  - info: host.raspberrypi All instances are stopped.
2023-04-22 18:23:34.804  - info: host.raspberrypi terminated
2023-04-22 18:23:34.663  - info: host.raspberrypi instance system.adapter.tuya.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2023-04-22 18:23:34.665  - info: host.raspberrypi All instances are stopped.
2023-04-22 18:23:34.804  - info: host.raspberrypi terminated
                        1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Sebi_7_6 last edited by

                          @sebi_7_6 sagte in [HowTo] ioBroker Restore unter Linux durchführen:

                          Wollte mein Backup einspiele und er sagt Wiederherstellung wird gestartet

                          Was machst du da genau?

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            Sebi_7_6 @Thomas Braun last edited by

                            @thomas-braun

                            Stelle meine Sicherung wieder her .

                            08a8eb35-61d2-4f1d-9928-2535556e2ae3-grafik.png

                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Sebi_7_6 last edited by

                              @sebi_7_6

                              Mach es mal komplett im Terminal.

                              iobroker restore <backup name or path>
                              S 1 Reply Last reply Reply Quote 0
                              • S
                                Sebi_7_6 @Thomas Braun last edited by Sebi_7_6

                                @thomas-braun

                                iobroker controller daemon is not running
host.raspberrypi OK.
The current version of js-controller differs from the version in the backup.
The js-controller version of the backup can not be restored automatically.
To restore the js-controller version of the backup, execute "npm i iobroker.js-controller@4.0.23 --production" inside your ioBroker directory
If you really want to restore the backup with the current installed js-controller, execute the restore command with the --force flag
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @Sebi_7_6 last edited by

                                  @sebi_7_6 sagte in [HowTo] ioBroker Restore unter Linux durchführen:

                                  The current version of js-controller differs from the version in the backup.

                                  Dann hast du ja den Grund.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sebi_7_6 last edited by

                                    Jaja 🙂 Warum sagt er mir das in der GUI nicht. Denke jeder hat nich immer sein Version aktuell obwohl ich es eigentlich dachte, dass sie es wäre.
                                    Und was mache ich jetzt ?

                                    Thomas Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @Sebi_7_6 last edited by

                                      @sebi_7_6

                                      Steht doch da. Die alte Version installieren.
                                      Dann passt auch das Backup da wieder rein.

                                      To restore the js-controller version of the backup, execute "npm i iobroker.js-controller@4.0.23 --production" inside your ioBroker directory

                                      Warum sagt er mir das in der GUI nicht.

                                      Weil GUIs notorisch lügen und Informationen zurückhalten.

                                      Bitte gewöhn dir an für Texte aus der Konsole die CodeTags zu verwenden.

                                      S 1 Reply Last reply Reply Quote 0
                                      • S
                                        Sebi_7_6 @Thomas Braun last edited by

                                        @thomas-braun

                                        Danke für den Hinweis.
                                        Ich danke dir aufjedenfall recht Herzlich für deine Hilfe!

                                        1 Reply Last reply Reply Quote 0
                                        • S
                                          Sebi_7_6 last edited by

                                          cefd3f98-5c90-4300-b98b-f3badd9aa46c-grafik.png

                                          Das Backup hat soweit funktioniert nur das HABPanel nicht. Hab es entfernt und die Instanz wieder neu installiert.
                                          Aber es steht immer 2x drinn. Clicke ich drauf kommt so etwas ..

                                          URIError: Failed to decode param '%web_protocol%://%web_bind%:%web_port%/habpanel/index.html'
    at decodeURIComponent (<anonymous>)
    at decode_param (/opt/iobroker/node_modules/express/lib/router/layer.js:172:12)
    at Layer.match (/opt/iobroker/node_modules/express/lib/router/layer.js:148:15)
    at matchLayer (/opt/iobroker/node_modules/express/lib/router/index.js:585:18)
    at next (/opt/iobroker/node_modules/express/lib/router/index.js:226:15)
    at compression (/opt/iobroker/node_modules/compression/index.js:220:5)
    at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
    at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)
                                          Glasfaser 1 Reply Last reply Reply Quote 0
                                          • Glasfaser
                                            Glasfaser @Sebi_7_6 last edited by

                                            @sebi_7_6 sagte in [HowTo] ioBroker Restore unter Linux durchführen:

                                            Hab es entfernt und die Instanz wieder neu installiert.

                                            Was entfernt , nur die Instanz ... oder auch den Adapter !?

                                            Zeige mal

                                            iob diag
                                            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

                                            1.0k
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            backitup how-to restore restore backup
                                            76
                                            513
                                            109257
                                            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