Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Rotes Skript beim automatischen Backup auf usb - Fehler?

    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

    Rotes Skript beim automatischen Backup auf usb - Fehler?

    This topic has been deleted. Only users with topic management privileges can see it.
    • simatec
      simatec Developer Most Active @Mapio90 last edited by

      @Malo_60
      Das ist auch richtig so. Im Anschluss wird es auf den stick kopiert, so dass es lokal ubd auf den Stick vorhanden ist.

      M 1 Reply Last reply Reply Quote 0
      • M
        Mapio90 @simatec last edited by

        @simatec in meinem Fall aber nicht, wenn ich unter filezilla den ordner (vom usb) aktualisere taucht kein backup auf. Mache ich was falsch, eventuell eine fehlende Einstellung?

        simatec 1 Reply Last reply Reply Quote 0
        • simatec
          simatec Developer Most Active @Mapio90 last edited by

          @Malo_60

          Stelle mal backitup in den Instanzen auf debug und poste den Log vom backup

          M 1 Reply Last reply Reply Quote 0
          • M
            Mapio90 @simatec last edited by

            @simatec

            backitup.0 2019-03-24 19:07:23.979 debug system.adapter.admin.0: logging true
            backitup.0 2019-03-24 19:07:23.974 debug redis pmessage io..logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553450843971,"q":0,"from":"system.adapter.admin.0","lc":1553450843971}
            backitup.0 2019-03-24 19:07:18.067 debug [total/history] done
            backitup.0 2019-03-24 19:07:18.048 debug [total/telegram] done
            backitup.0 2019-03-24 19:07:18.046 debug [total/telegram] [total] used Telegram-Instance: telegram.0
            backitup.0 2019-03-24 19:07:17.994 debug [total] 10 00 16 /7 * *
            backitup.0 2019-03-24 19:07:17.988 info [total] backup was activated at 16:00 every 7 day(s)
            backitup.0 2019-03-24 19:07:17.987 debug [minimal] 10 15 16 /7 * *
            backitup.0 2019-03-24 19:07:17.957 info [minimal] backup was activated at 16:15 every 7 day(s)
            backitup.0 2019-03-24 19:07:17.251 debug [DEBUG] [total/start] IoBroker started ...
            backitup.0 2019-03-24 19:07:17.250 debug [DEBUG] [total/telegram] done
            backitup.0 2019-03-24 19:07:17.250 debug [DEBUG] [total/start] done
            backitup.0 2019-03-24 19:07:17.249 debug [DEBUG] [total/clean] done
            backitup.0 2019-03-24 19:07:17.248 error [ERROR] [total/clean] Backup files not deleted from /opt/iobroker/backups because some errors.
            backitup.0 2019-03-24 19:07:17.248 debug [DEBUG] [total/cifs] done
            backitup.0 2019-03-24 19:07:17.247 error [ERROR] [total/cifs] Error: EACCES: permission denied, open '/media/usbstick/total_2019_03_24-19_05_09_backupiobroker.tar.gz'
            backitup.0 2019-03-24 19:07:17.247 debug [DEBUG] [total/cifs] Copy total_2019_03_24-19_05_09_backupiobroker.tar.gz...
            backitup.0 2019-03-24 19:07:17.246 debug [DEBUG] [total/total] done
            backitup.0 2019-03-24 19:07:17.246 debug [DEBUG] [total/total] Ignore dir: /opt/iobroker/backups
            backitup.0 2019-03-24 19:07:17.245 debug [DEBUG] [total/total] TAR started...
            backitup.0 2019-03-24 19:07:17.244 debug [DEBUG] [total/mount] done
            backitup.0 2019-03-24 19:07:17.243 debug Printing logs of previous backup
            backitup.0 2019-03-24 19:07:17.234 info starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.1
            backitup.0 2019-03-24 19:07:17.034 info States connected to redis: 127.0.0.1:6379
            backitup.0 2019-03-24 19:07:17.028 debug statesDB connected
            backitup.0 2019-03-24 19:07:16.991 debug objectDB connected
            backitup.0 2019-03-24 19:05:06.638 debug system.adapter.admin.0: logging false
            backitup.0 2019-03-24 19:05:06.637 debug redis pmessage io.
            .logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1553450706636,"q":0,"from":"system.host.ioBroker-Pi","lc":1553450706421}
            backitup.0 2019-03-24 19:05:06.446 debug system.adapter.admin.0: logging false
            backitup.0 2019-03-24 19:05:06.425 debug redis pmessage io.
            .logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1553450706421,"q":0,"from":"system.adapter.admin.0","lc":1553450706421}
            backitup.0 2019-03-24 19:05:06.287 debug redis pmessage io.backitup.0.oneClick.
            io.backitup.0.oneClick.total {"val":false,"ack":true,"ts":1553450706282,"q":0,"from":"system.adapter.backitup.0","lc":1553450706282}
            backitup.0 2019-03-24 19:05:06.277 debug [total] exec: done
            backitup.0 2019-03-24 19:05:06.235 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.total {"val":true,"ack":false,"ts":1553450706234,"q":0,"from":"system.adapter.admin.0","lc":1553450706234}
            backitup.0 2019-03-24 19:05:00.911 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"538063270":"Malo"}
            backitup.0 2019-03-24 19:05:00.903 debug redis pmessage messagebox.system.adapter.backitup.0 messagebox.system.adapter.backitup.0 {"command":"getTelegramUser","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":1
            backitup.0 2019-03-24 19:04:03.222 debug system.adapter.admin.0: logging true
            backitup.0 2019-03-24 19:04:03.216 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553450643213,"q":0,"from":"system.adapter.admin.0","lc":1553450643213}
            backitup.0 2019-03-24 19:03:59.676 debug [total] 10 00 16 */7 * *
            backitup.0 2019-03-24 19:03:59.670 info [total] backup was activated at 16:00 every 7 day(s)
            backitup.0 2019-03-24 19:03:59.670 debug [minimal] 10 15 16 /7 * *
            backitup.0 2019-03-24 19:03:59.639 info [minimal] backup was activated at 16:15 every 7 day(s)
            backitup.0 2019-03-24 19:03:59.595 info starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.1
            backitup.0 2019-03-24 19:03:59.399 info States connected to redis: 127.0.0.1:6379
            backitup.0 2019-03-24 19:03:59.392 debug statesDB connected
            backitup.0 2019-03-24 19:03:59.355 debug objectDB connected
            backitup.0 2019-03-24 19:07:23.990 debug system.adapter.admin.0: logging true
            backitup.0 2019-03-24 19:07:23.987 debug redis pmessage io.
            .logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553450843971,"q":0,"from":"system.adapter.admin.0","lc":1553450843971}

            simatec 1 Reply Last reply Reply Quote 0
            • simatec
              simatec Developer Most Active @Mapio90 last edited by simatec

              @Malo_60

              Dein User iobroker hat keine Schreibrechte auf dem stick.

              sudo chmod 777 /pfad/zum/stick
              
              M 1 Reply Last reply Reply Quote 0
              • M
                Mapio90 @simatec last edited by

                @simatec said in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                sudo chmod 777 /pfad/zum/stick

                Habe ich ausgeführt sudo chmod 777 /media/usbstick
                Kommt wieder folgende Fehlermeldung:

                backitup.0 2019-03-24 19:39:38.971 debug system.adapter.admin.0: logging true
                backitup.0 2019-03-24 19:39:38.970 debug redis pmessage io..logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553452778968,"q":0,"from":"system.adapter.admin.0","lc":1553452778968}
                backitup.0 2019-03-24 19:39:32.308 debug system.adapter.admin.0: logging false
                backitup.0 2019-03-24 19:39:32.307 debug redis pmessage io.
                .logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1553452772304,"q":0,"from":"system.adapter.admin.0","lc":1553452772304}
                backitup.0 2019-03-24 19:39:32.004 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1553452772002,"q":0,"from":"system.adapter.backitup.0","lc":1553452772002}
                backitup.0 2019-03-24 19:39:32.000 debug [minimal] exec: done
                backitup.0 2019-03-24 19:39:31.993 debug [minimal/umount] done
                backitup.0 2019-03-24 19:39:31.990 debug [minimal/history] done
                backitup.0 2019-03-24 19:39:31.973 debug [minimal/telegram] done
                backitup.0 2019-03-24 19:39:31.967 debug sendTo "send" to system.adapter.telegram.0 from system.adapter.backitup.0
                backitup.0 2019-03-24 19:39:31.965 debug [minimal/telegram] [minimal] used Telegram-Instance: telegram.0
                backitup.0 2019-03-24 19:39:31.953 debug [minimal/clean] done
                backitup.0 2019-03-24 19:39:31.952 debug [minimal/clean] Backup files not deleted from /opt/iobroker/backups because some errors.
                backitup.0 2019-03-24 19:39:31.944 debug [minimal/cifs] done
                backitup.0 2019-03-24 19:39:31.943 debug [minimal/cifs] Error: EACCES: permission denied, open '/media/usbstick/minimal_2019_03_24-19_39_28_backupiobroker.tar.gz'
                backitup.0 2019-03-24 19:39:31.929 debug [minimal/cifs] Copy minimal_2019_03_24-19_39_28_backupiobroker.tar.gz...
                backitup.0 2019-03-24 19:39:31.923 debug [minimal/minimal] done
                backitup.0 2019-03-24 19:39:31.902 debug [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_03_24-19_39_28_backupiobroker.tar.gz
                backitup.0 2019-03-24 19:39:28.980 debug [minimal/mount] done
                backitup.0 2019-03-24 19:39:28.223 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":true,"ack":false,"ts":1553452768221,"q":0,"from":"system.adapter.admin.0","lc":1553452768221}
                backitup.0 2019-03-24 19:39:25.774 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"538063270":"Malo"}
                backitup.0 2019-03-24 19:39:38.975 debug system.adapter.admin.0: logging true
                backitup.0 2019-03-24 19:39:38.974 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553452778968,"q":0,"from":"system.adapter.admin.0","lc":1553452778968}

                1 Reply Last reply Reply Quote 0
                • simatec
                  simatec Developer Most Active last edited by

                  Mache mal folgendes noch ...

                  sudo chmod 777 /media/usbstick/
                  sudo chmod 777 /media/usbstick/*
                  
                  1 Reply Last reply Reply Quote 0
                  • M
                    Mapio90 last edited by

                    Es funktioniert trotz den sudo Befehlen immer noch nicht.

                    690b79a9-bd15-4b96-a199-07de4b23f938-grafik.png

                    7dee7273-084c-4788-be88-c5358e43f6c4-grafik.png

                    simatec 1 Reply Last reply Reply Quote 0
                    • simatec
                      simatec Developer Most Active @Mapio90 last edited by

                      @Malo_60

                      Ist denn der Stick richtig eingehängt?
                      Der muss vorher natürlich richtig eingehangen sein.
                      Einen Stick mountet backitup nicht.
                      Beim Copy wird wirklich nur an den angegebenen Stick kopiert.

                      1 Reply Last reply Reply Quote 0
                      • M
                        Mapio90 last edited by

                        in der vorletzten Zeile...

                        pi@ioBroker-Pi:~ $ df -h
                        Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
                        /dev/root 15G 1,9G 13G 14% /
                        devtmpfs 460M 0 460M 0% /dev
                        tmpfs 464M 0 464M 0% /dev/shm
                        tmpfs 464M 13M 452M 3% /run
                        tmpfs 5,0M 4,0K 5,0M 1% /run/lock
                        tmpfs 464M 0 464M 0% /sys/fs/cgroup
                        /dev/mmcblk0p1 44M 22M 22M 51% /boot
                        /dev/sda1 3,9G 236M 3,7G 6% /media/usbstick
                        tmpfs 93M 0 93M 0% /run/user/1000

                        simatec 1 Reply Last reply Reply Quote 0
                        • simatec
                          simatec Developer Most Active @Mapio90 last edited by

                          @Malo_60

                          Hast du mal Testweise probiert, dein backup auf einen anderen lokalen Pfad abzulegen?
                          Ich werde morgen mal probieren, das ganze nachzustellen und zutesten

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            Mapio90 @simatec last edited by

                            @simatec Nein das hab ich noch nicht versucht. Werde ich aber nachher probieren und berichten

                            1 Reply Last reply Reply Quote 0
                            • M
                              Mapio90 last edited by

                              Es funktioniert Lokal auch nicht

                              1 Reply Last reply Reply Quote 0
                              • simatec
                                simatec Developer Most Active last edited by

                                Bitte poste mal den Log.
                                Läuft dein iobroker unter User "iobroker"?
                                Wann wurde dein iobroker aufgesetzt?

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  Mapio90 @simatec last edited by

                                  @simatec said in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                                  Bitte poste mal den Log.

                                  backitup.0 2019-03-25 20:06:56.429 debug system.adapter.admin.0: logging true
                                  backitup.0 2019-03-25 20:06:56.428 debug redis pmessage io..logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553540816422,"q":0,"from":"system.adapter.admin.0","lc":1553540816422}
                                  backitup.0 2019-03-25 20:06:08.978 debug system.adapter.admin.0: logging false
                                  backitup.0 2019-03-25 20:06:08.976 debug redis pmessage io.
                                  .logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1553540768975,"q":0,"from":"system.adapter.admin.0","lc":1553540768975}
                                  backitup.0 2019-03-25 20:05:02.727 debug system.adapter.admin.0: logging true
                                  backitup.0 2019-03-25 20:05:02.726 debug redis pmessage io..logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1553540702723,"q":0,"from":"system.adapter.admin.0","lc":1553540702723}
                                  backitup.0 2019-03-25 20:04:53.597 debug redis pmessage io.backitup.0.oneClick.
                                  io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1553540693594,"q":0,"from":"system.adapter.backitup.0","lc":1553540693594}
                                  backitup.0 2019-03-25 20:04:53.592 debug [minimal] exec: done
                                  backitup.0 2019-03-25 20:04:53.586 debug [minimal/umount] done
                                  backitup.0 2019-03-25 20:04:53.583 debug [minimal/history] done
                                  backitup.0 2019-03-25 20:04:53.566 debug [minimal/telegram] done
                                  backitup.0 2019-03-25 20:04:53.563 debug [minimal/telegram] [minimal] used Telegram-Instance: telegram.0
                                  backitup.0 2019-03-25 20:04:53.555 debug [minimal/clean] done
                                  backitup.0 2019-03-25 20:04:53.549 debug [minimal/cifs] [IGNORED] Path "C:/IObroker" not found
                                  backitup.0 2019-03-25 20:04:53.543 debug [minimal/minimal] done
                                  backitup.0 2019-03-25 20:04:53.523 debug [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_03_25-20_04_50_backupiobroker.tar.gz
                                  backitup.0 2019-03-25 20:04:50.574 debug [minimal/mount] done
                                  backitup.0 2019-03-25 20:04:49.805 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":true,"ack":false,"ts":1553540689803,"q":0,"from":"system.adapter.admin.0","lc":1553540689803}
                                  backitup.0 2019-03-25 20:04:48.491 debug [total] 10 00 16 */7 * *
                                  backitup.0 2019-03-25 20:04:48.485 info [total] backup was activated at 16:00 every 7 day(s)
                                  backitup.0 2019-03-25 20:04:48.484 debug [minimal] 10 15 16 */7 * *
                                  backitup.0 2019-03-25 20:04:48.454 info [minimal] backup was activated at 16:15 every 7 day(s)
                                  backitup.0 2019-03-25 20:04:48.413 info starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.1
                                  backitup.0 2019-03-25 20:04:48.213 info States connected to redis: 127.0.0.1:6379
                                  backitup.0 2019-03-25 20:04:48.207 debug statesDB connected
                                  backitup.0 2019-03-25 20:04:48.170 debug objectDB connected
                                  backitup.0 2019-03-25 20:03:28.207 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"538063270":"Malo"}
                                  backitup.0 2019-03-25 20:03:28.201 debug redis pmessage messagebox.system.adapter.backitup.0 messagebox.system.adapter.backitup.0 {"command":"getTelegramUser","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":1
                                  backitup.0 2019-03-25 20:03:23.616 debug [total] 10 00 16 */7 * *
                                  backitup.0 2019-03-25 20:03:23.610 info [total] backup was activated at 16:00 every 7 day(s)
                                  backitup.0 2019-03-25 20:03:23.610 debug [minimal] 10 15 16 */7 * *
                                  backitup.0 2019-03-25 20:03:23.580 info [minimal] backup was activated at 16:15 every 7 day(s)
                                  backitup.0 2019-03-25 20:03:23.540 info starting. Version 1.1.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.1
                                  backitup.0 2019-03-25 20:03:23.348 info States connected to redis: 127.0.0.1:6379
                                  backitup.0 2019-03-25 20:03:23.342 debug statesDB connected
                                  backitup.0 2019-03-25 20:03:23.305 debug objectDB connected

                                  @simatec said in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                                  Läuft dein iobroker unter User "iobroker"?

                                  0d222968-46e2-4668-a424-5648c3c17513-grafik.png

                                  @simatec said in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                                  Wann wurde dein iobroker aufgesetzt?

                                  vor circa 3 Wochen. Meine SD karte ging nach einem Stromausfall kaputt. Deswegen wurde es vor ca. 3 wochen Neu aufgesetzt

                                  1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active last edited by simatec

                                    @Malo_60 sagte in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                                    IObroker

                                    C:/iobroker kann nicht gehen. Da ist doch dein Windows Rechner.
                                    Wenn dann geht der Pfad /home/iobroker zum testen.

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      Mapio90 @simatec last edited by

                                      @simatec said in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                                      C:/iobroker kann nicht gehen. Da ist doch dein Windows Rechner.
                                      Wenn dann geht der Pfad /home/iobroker zum testen

                                      Der Pfad funktioniert. Hatte mich auch noch gewundert, wie der raspi dass auf den pc bekommen soll :). Wie gesagt der Pfad /home/iobroker funktioniert das backup.

                                      1 Reply Last reply Reply Quote 0
                                      • simatec
                                        simatec Developer Most Active last edited by

                                        Dann ist es definitiv ein Rechteproblem bei deinem Stick.
                                        Der User iobroker benötigt die Schreibrechte auf dem Stick.

                                        Welches Dateisystem hat dein Stick. Eventuell solltest du ihn in ntfs formatieren.

                                        https://forum.ubuntuusers.de/post/8519583/

                                        M 1 Reply Last reply Reply Quote 0
                                        • M
                                          Mapio90 @simatec last edited by

                                          @simatec said in Rotes Skript beim automatischen Backup auf usb - Fehler?:

                                          Welches Dateisystem hat dein Stick. Eventuell solltest du ihn in ntfs formatieren.

                                          Das kann ich dir nicht sagen. Woher bekomme ich das in Erfahrung? ich hatte ihn mit dem Programm sd card formatter auf fat32 formatiert.

                                          1 Reply Last reply Reply Quote 0
                                          • simatec
                                            simatec Developer Most Active last edited by

                                            Dann ist er auch fat32.
                                            Formatiere ihn einfach unter Windows im Arbeitsplatz.

                                            M 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

                                            866
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            backup fehler usb automatisch usb stick
                                            4
                                            33
                                            1295
                                            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