Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Zwei Bugs mit backitup 2.1.0 und 2.0.5

    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

    Zwei Bugs mit backitup 2.1.0 und 2.0.5

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

      @metaxa SQL hat keinen Unterordner ...
      Welche Version von Backitup nutzt du denn?

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

        @simatec Sorry, für die späte Rückmeldung. Ich versuchte den Fehler einzugrenzen.

        BackitUp: 2.1.0 (heute morgen upgedated) 1x Host, 1x Slave
        Node JS: 12.19.0
        NPM: 6.14.8
        JS-Controller: 3.2.16

        Es läuft jetzt alles!
        Was mußte ich machen. Nach jeder Änderung in der Adapteroberfläche ging danach nichts mehr, endete immer in dieser Art Fehlermeldungen:

        BackItUp:
Your backup was not completely created. Please check the errors!!

mount: Error: Command failed: sudo mount -t cifs -o username=Andreas,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.98/backups/io_096_vm /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

        Nach einem Neustart der vollständigen VM ging es dann immer auf Anhieb. Ich habe das Gefühl, dass der Unmountbefehl immer wieder hängen blieb.
        NFS habe ich wieder rausgenommen, auch die Freigabe auf dem NAS (Screen weiter oben) und bin wieder retour auf CIFS. Paar Steps mit Zwischenkontrollen und Neustarts brachten das Ergebnis. Scheinbar ist das ändern der Cronjobs nund speichern der Config kein Problem.

        Für Zigbee, SQL, usw. werden keine Unterverzeichnisse angeboten, auch keine eigenen Cronjobs. Die werden offensichtlich mit dem ioBroker Backup paralell angestossen.
        Gibt es dafür einen bestimmten Grund?

        Danke jedenfalls für den tollen Adapter und deine Muße mir heute unter "Bugs" dennoch zuhelfen.
        LG, mxa

        simatec M 2 Replies Last reply Reply Quote 0
        • simatec
          simatec Developer Most Active @metaxa last edited by

          @metaxa Gerne ... kein Problem

          1 Reply Last reply Reply Quote 1
          • M
            michael_4358 @metaxa last edited by

            @metaxa

            habe auf meinem pi das gleiche problem...
            kann aber deine fehler behebung nicht ganz nach vollziehen

            hast du einfach die alten backups gelöscht und alles neugestartet??

            metaxa 1 Reply Last reply Reply Quote 0
            • metaxa
              metaxa @michael_4358 last edited by

              @michael_4358 was willst du alles backupen, welche adapter?

              M 1 Reply Last reply Reply Quote 0
              • M
                michael_4358 @metaxa last edited by

                @metaxa ioBroker;zigbee;jarvis

                und wenn ich die history mit einbinde stürtzt das adapter ab

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

                  @michael_4358
                  Ohne Debug Log wird es schwierig dir zu helfen

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

                    @simatec
                    64300e34-a12e-4e8e-92d2-4e7508f389f9-grafik.png

                    wendy2702 simatec 2 Replies Last reply Reply Quote 0
                    • wendy2702
                      wendy2702 @michael_4358 last edited by

                      @michael_4358 kannst du das logfile bitte als Text in Code Tags </> posten!

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

                        @michael_4358
                        Bitte die Instanz auf debug stellen, damit man hier einfach mehr sieht

                        1 Reply Last reply Reply Quote 0
                        • M
                          michael_4358 @wendy2702 last edited by

                          @wendy2702 wo kann ich den adapter umschalten?

                          metaxa 1 Reply Last reply Reply Quote 0
                          • metaxa
                            metaxa @michael_4358 last edited by

                            @michael_4358 650ed685-d997-4f0a-97b4-462da8672d40-grafik.png

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              michael_4358 @metaxa last edited by michael_4358

                              @metaxa ```

                              2021-04-19 11:34:32.024 - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-04-19 11:34:34.446 - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 4271
2021-04-19 11:34:37.605 - debug: backitup.0 (4271) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-04-19 11:34:37.668 - debug: backitup.0 (4271) Objects client ready ... initialize now
2021-04-19 11:34:37.670 - debug: backitup.0 (4271) Objects create System PubSub Client
2021-04-19 11:34:37.672 - debug: backitup.0 (4271) Objects create User PubSub Client
2021-04-19 11:34:37.673 - debug: backitup.0 (4271) Objects client initialize lua scripts
2021-04-19 11:34:37.688 - debug: backitup.0 (4271) Objects connected to redis: 127.0.0.1:9001
2021-04-19 11:34:37.698 - debug: backitup.0 (4271) objectDB connected
2021-04-19 11:34:37.700 - debug: backitup.0 (4271) Redis States: Use Redis connection: 127.0.0.1:9000
2021-04-19 11:34:37.724 - debug: backitup.0 (4271) States create System PubSub Client
2021-04-19 11:34:37.726 - debug: backitup.0 (4271) States create User PubSub Client
2021-04-19 11:34:37.736 - debug: backitup.0 (4271) States connected to redis: 127.0.0.1:9000
2021-04-19 11:34:37.737 - debug: backitup.0 (4271) statesDB connected
2021-04-19 11:34:38.148 - debug: backitup.0 (4271) Plugin sentry Initialize Plugin (enabled=true)
2021-04-19 11:34:38.378 - info: backitup.0 (4271) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.21.0, js-controller: 3.2.16
2021-04-19 11:34:38.468 - info: backitup.0 (4271) [iobroker] backup was activated at 12:00 every 5 day(s)
2021-04-19 11:34:38.504 - debug: backitup.0 (4271) [iobroker] 10 00 12 */5 * *
2021-04-19 11:34:38.653 - debug: backitup.0 (4271) first mount attempt with smb option failed. try next mount attempt without smb option ...
2021-04-19 11:34:38.803 - debug: backitup.0 (4271) mount successfully completed
2021-04-19 11:34:40.869 - debug: backitup.0 (4271) detect backup file 1 from cifs: iobroker_2021_04_14-21_47_13_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:34:40.869 - debug: backitup.0 (4271) detect backup file 2 from cifs: iobroker_2021_04_14-21_48_53_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:34:40.870 - debug: backitup.0 (4271) detect backup file 3 from cifs: iobroker_2021_04_16-12_00_36_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:34:40.870 - debug: backitup.0 (4271) detect backup file 4 from cifs: iobroker_2021_04_17-14_10_04_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:34:40.871 - debug: backitup.0 (4271) detect backup file 5 from cifs: iobroker_2021_04_17-14_12_03_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:34:40.872 - debug: backitup.0 (4271) detect last backup file: iobroker_2021_04_17-14_12_03_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:34:48.477 - debug: backitup.0 (4271) mount activ... umount in 2 Seconds!!
2021-04-19 11:34:50.549 - debug: backitup.0 (4271) umount successfully completed
2021-04-19 11:34:51.476 - debug: backitup.0 (4271) telegram-instance: telegram.0
2021-04-19 11:34:51.479 - debug: backitup.0 (4271) sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"1440354501":{"firstName":"Anja"},"1455495559":{"firstName":"Michael","userName":"michael4358"}}
2021-04-19 11:34:54.699 - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true)
2021-04-19 11:34:54.716 - info: backitup.0 (4271) Got terminate signal TERMINATE_YOURSELF
2021-04-19 11:34:54.717 - info: backitup.0 (4271) cleaned everything up...
2021-04-19 11:34:54.718 - info: backitup.0 (4271) terminating
2021-04-19 11:34:54.720 - debug: backitup.0 (4271) Plugin sentry destroyed
2021-04-19 11:34:54.721 - info: backitup.0 (4271) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2021-04-19 11:34:54.717 - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal
2021-04-19 11:34:55.382 - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2021-04-19 11:34:57.759 - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 4543
2021-04-19 11:35:00.906 - debug: backitup.0 (4543) Redis Objects: Use Redis connection: 127.0.0.1:9001
2021-04-19 11:35:00.944 - debug: backitup.0 (4543) Objects client ready ... initialize now
2021-04-19 11:35:00.967 - debug: backitup.0 (4543) Objects create System PubSub Client
2021-04-19 11:35:00.968 - debug: backitup.0 (4543) Objects create User PubSub Client
2021-04-19 11:35:00.969 - debug: backitup.0 (4543) Objects client initialize lua scripts
2021-04-19 11:35:00.984 - debug: backitup.0 (4543) Objects connected to redis: 127.0.0.1:9001
2021-04-19 11:35:00.994 - debug: backitup.0 (4543) objectDB connected
2021-04-19 11:35:00.996 - debug: backitup.0 (4543) Redis States: Use Redis connection: 127.0.0.1:9000
2021-04-19 11:35:01.005 - debug: backitup.0 (4543) States create System PubSub Client
2021-04-19 11:35:01.006 - debug: backitup.0 (4543) States create User PubSub Client
2021-04-19 11:35:01.015 - debug: backitup.0 (4543) States connected to redis: 127.0.0.1:9000
2021-04-19 11:35:01.016 - debug: backitup.0 (4543) statesDB connected
2021-04-19 11:35:01.412 - debug: backitup.0 (4543) Plugin sentry Initialize Plugin (enabled=true)
2021-04-19 11:35:01.645 - info: backitup.0 (4543) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.21.0, js-controller: 3.2.16
2021-04-19 11:35:01.738 - info: backitup.0 (4543) [iobroker] backup was activated at 12:00 every 5 day(s)
2021-04-19 11:35:01.768 - debug: backitup.0 (4543) [iobroker] 10 00 12 */5 * *
2021-04-19 11:35:01.891 - debug: backitup.0 (4543) first mount attempt with smb option failed. try next mount attempt without smb option ...
2021-04-19 11:35:02.043 - debug: backitup.0 (4543) mount successfully completed
2021-04-19 11:35:02.619 - error: backitup.0 (4543) [iobroker] Backup folder not created: Error: EPERM: operation not permitted, chmod '/opt/iobroker/backups'Please reinstall backitup and run "iobroker fix"!!
2021-04-19 11:35:02.640 - debug: backitup.0 (4543) Backup has started ...
2021-04-19 11:35:02.655 - debug: backitup.0 (4543) [iobroker/mount] mount activ... umount is started before mount!!
2021-04-19 11:35:02.716 - debug: backitup.0 (4543) [iobroker/mount] umount successfully completed
2021-04-19 11:35:04.110 - debug: backitup.0 (4543) detect backup file 1 from cifs: iobroker_2021_04_14-21_47_13_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:04.110 - debug: backitup.0 (4543) detect backup file 2 from cifs: iobroker_2021_04_14-21_48_53_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:04.111 - debug: backitup.0 (4543) detect backup file 3 from cifs: iobroker_2021_04_16-12_00_36_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:04.111 - debug: backitup.0 (4543) detect backup file 4 from cifs: iobroker_2021_04_17-14_10_04_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:04.112 - debug: backitup.0 (4543) detect backup file 5 from cifs: iobroker_2021_04_17-14_12_03_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:04.113 - debug: backitup.0 (4543) detect last backup file: iobroker_2021_04_17-14_12_03_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:12.710 - debug: backitup.0 (4543) [iobroker/mount] first mount attempt with smb option failed. try next mount attempt without smb option ...
2021-04-19 11:35:12.873 - debug: backitup.0 (4543) [iobroker/mount] mount successfully completed
2021-04-19 11:35:12.874 - debug: backitup.0 (4543) [iobroker/mount] done
2021-04-19 11:35:16.110 - debug: backitup.0 (4543) [iobroker/iobroker] host.raspberrypi 3777 states saved
2021-04-19 11:35:16.202 - debug: backitup.0 (4543) [iobroker/iobroker] host.raspberrypi 6872 objects saved
2021-04-19 11:35:19.933 - debug: backitup.0 (4543) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2021_04_19-11_35_13_Pi4-1_backupiobroker.tar.gz
2021-04-19 11:35:20.984 - debug: backitup.0 (4543) [iobroker/iobroker] done
2021-04-19 11:35:21.739 - debug: backitup.0 (4543) [iobroker/historyDB] compress from historyDB started ...
2021-04-19 11:35:21.740 - debug: backitup.0 (4543) [iobroker/historyDB] [IGNORED] Backitup cannot found source "undefined" for compress!
2021-04-19 11:35:21.892 - debug: backitup.0 (4543) [iobroker/zigbee] found zigbee database: zigbee.0,zigbee.1
2021-04-19 11:35:21.893 - debug: backitup.0 (4543) [iobroker/zigbee] done
2021-04-19 11:35:22.197 - debug: backitup.0 (4543) [iobroker/jarvis] Jarvis Backup cannot created. Please install a Jarvis version >= 2.2.0
2021-04-19 11:35:22.200 - debug: backitup.0 (4543) [iobroker/jarvis] done
2021-04-19 11:35:22.802 - debug: backitup.0 (4543) [iobroker/cifs] done
2021-04-19 11:35:23.405 - debug: backitup.0 (4543) [iobroker/clean] Backup files not deleted from /opt/iobroker/backups because some errors.
2021-04-19 11:35:23.406 - debug: backitup.0 (4543) [iobroker/clean] done
2021-04-19 11:35:23.864 - debug: backitup.0 (4543) [iobroker/telegram] [iobroker] used Telegram-Instance: telegram.0
2021-04-19 11:35:23.872 - debug: backitup.0 (4543) sendTo "send" to system.adapter.telegram.0 from system.adapter.backitup.0
2021-04-19 11:35:23.873 - debug: backitup.0 (4543) [iobroker/telegram] done
2021-04-19 11:35:24.178 - debug: backitup.0 (4543) [iobroker/historyHTML] new history html values created
2021-04-19 11:35:24.179 - debug: backitup.0 (4543) [iobroker/historyHTML] done
2021-04-19 11:35:24.369 - debug: backitup.0 (4543) [iobroker/historyJSON] new history json values created
2021-04-19 11:35:24.371 - debug: backitup.0 (4543) [iobroker/historyJSON] done
2021-04-19 11:35:24.581 - debug: backitup.0 (4543) [iobroker/umount] mount activ, umount is started ...
2021-04-19 11:35:29.652 - debug: backitup.0 (4543) [iobroker/umount] umount successfully completed
2021-04-19 11:35:29.654 - debug: backitup.0 (4543) [iobroker/umount] done
2021-04-19 11:35:29.805 - debug: backitup.0 (4543) [iobroker] exec: done
```
                              simatec 1 Reply Last reply Reply Quote 0
                              • simatec
                                simatec Developer Most Active @michael_4358 last edited by

                                @michael_4358 Dein History Pfad ist nicht eingetragen. Nutzt du den history-Adapter?

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

                                  Ja nutze ich...

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

                                    @michael_4358
                                    Zeige mal bitte, was du dort konfiguriert hast

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

                                      @simatec
                                      ob was drin steht oder nicht es kommt immer der gleiche fehler...

                                      27f3d394-b97a-42b1-9631-004c30163e3e-grafik.png

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

                                        @michael_4358 Trage mal bitte in dem History Adapter und in Backitup folgenden Pfad ein

                                        /opt/iobroker/iobroker-data/history
                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          michael_4358 last edited by

                                          Scheint zu funktionieren!

                                          Danke dir

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

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          923
                                          Online

                                          31.9k
                                          Users

                                          80.1k
                                          Topics

                                          1.3m
                                          Posts

                                          6
                                          38
                                          2625
                                          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