search

simatec / ioBroker.backitup

ioBroker.backitup allows you to backup and restore your ioBroker installation and other systems, such as databases, Zigbee, scripts and many more.
MIT License
68 stars 35 forks source link

Backupfiles from Dropbox are not shown for restore #771

Closed Standarduser closed 1 year ago

Standarduser commented 1 year ago

My BackItUp adapter is configured to upload backup files into my Dropbox - this works fine. It's also configured to keep the last 5 Backups.

But if I want to select a backup for restore I can't see the latest backups, just 5 old ones. At the moment there are 9 backup files instead of 5.

iobroker_2022_09_28-02_00_13_backupiobroker.tar.gz iobroker_2022_10_01-02_00_10_backupiobroker.tar.gz iobroker_2022_10_04-02_00_10_backupiobroker.tar.gz iobroker_2022_10_07-02_00_10_backupiobroker.tar.gz iobroker_2022_10_10-02_00_10_backupiobroker.tar.gz iobroker_2022_10_13-02_00_10_backupiobroker.tar.gz iobroker_2022_10_17-18_00_12_backupiobroker.tar.gz iobroker_2022_10_19-02_00_10_backupiobroker.tar.gz iobroker_2022_10_19-07_10_45_backupiobroker.tar.gz

In debug mode there are following messages in log file:

2022-10-19 16:34:29.597 - info: backitup.0 (463496) Loglevel changed from "warn" to "debug"
2022-10-19 16:34:46.384 - debug: backitup.0 (463496) telegram-instance: telegram.0
2022-10-19 16:34:51.339 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:34:51.340 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:34:51.341 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:35:27.545 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:35:27.545 - debug: backitup.0 (463496) Backup list cannot be read ...
2022-10-19 16:35:27.546 - debug: backitup.0 (463496) Backup list cannot be read ...
simatec commented 1 year ago

I need a few more details. The error is not reproducible for me.

On my test systems, all backups can be read from Dropbox.

Standarduser commented 1 year ago

Sorry, I don't have more information due to poor debug logging of BackItUp.

But I noticed that a newer backup gets displayed when I delete an older one.

Maybe the problem gets solved if all available backups are displayed, regardless howmany the adapter is configured to keep.

simatec commented 1 year ago

What bad debug logging?

Do not understand the statement. I need more info, screenshots etc.

All my test systems show all backups from dropbox and this is the first time I've heard this message from you.

What names do your backups have and what else is in the directories?

Please more info

Standarduser commented 1 year ago

poor != bad (just to say) Sorry if this was a misunderstanding.

Okay, even if I don't really have more information I will try to explain a little bit more. I got that issue described in the first post and was able to solve this by deleting all backups and start from beginning.

But I'm able to reproduce it (it's a little bit different from above).

Now at this moment I have a Dropbox folder which contains only backups made with BackItUp adapter (22 files). This is a screenshot from Dropbox web ui:

dropbox-files

You can count 7 ioBroker backups.

Next screenshot is from BackItUp:

backitup-files

You can count 3 ioBroker backups.

This is what BackItUp writes into log:

backitup-log

What else can I provide to help?

simatec commented 1 year ago

Ich kann deinen Fehler leider nicht nachstellen.

Bildschirmfoto 2022-10-30 um 13 28 48

Prüfe mal, ob eventuell Dateien in der dropbox beschädigt sind. Was auch noch zu empfehlen ist, dass man Unterordner für die Backups anlegt. Also sprich, iobroker und Homematic trennen.

Dies kannst du in Backitup einstellen

simatec commented 1 year ago

Another option would also be to renew your token. You can do this in the Backitup menu.

mibr85 commented 1 year ago

ich hänge mich mal mit dran bei mir besteht das gleiche Problem. kann es damit zusammenhängen das ioBroker im Docker läuft? Backups erstellen und in der DB speichern funktioniertaber super. wenn ich auf Sicherungen abrufen klicke passiert gar nix image

Instanz steht auf Debug aber im log wird nach dem start nur das angezeigt: image

einstellungen im Drobox Tab: image

Token ist neu von heute

simatec commented 1 year ago

Ich kann das Problem nicht nachstellen. Habe auch auf der Testumgebung einen neuen Token geholt und ich kann im Config Menü und über den Backitup Tab die Backups holen. Was mir aufgefallen ist, bei dir stehen die Default Verzeichnisse in der Config. Eigentlich sind das Platzhalter. Stimmen die denn mit deinen Dropbox-Pfaden überein?

simatec commented 1 year ago

image

image

mibr85 commented 1 year ago

Verzeichnisse passen image Kann es denn mit der Installation in Docker zu tun haben?

simatec commented 1 year ago

Nein... Mein Testsystem ist auch auf Docker

simatec commented 1 year ago

Zeige mal im Pfad /opt/iobroker/node_modules/iobroker.backitup die Ausgabe von folgenden Befehl

npm ls

mibr85 commented 1 year ago

`root@ioBrokerTWS:/opt/iobroker# cd node_modules/iobroker.backitup root@ioBrokerTWS:/opt/iobroker/node_modules/iobroker.backitup# npm ls iobroker.backitup@2.5.7 (github:simatec/ioBroker.backitup#67543045504cee442132f7d0b7cab5c8685fd307) /opt/iobroker/node_modules/iobroker.backitup ├── UNMET DEPENDENCY @googleapis/drive@^4.0.0 ├─┬ @iobroker/adapter-core@2.6.7 │ └─┬ @types/iobroker@4.0.5 │ └── UNMET DEPENDENCY @types/node@* ├─┬ axios@1.1.3 │ ├── follow-redirects@1.15.2 │ ├─┬ form-data@4.0.0 │ │ ├── UNMET DEPENDENCY asynckit@^0.4.0 │ │ ├── UNMET DEPENDENCY combined-stream@^1.0.8 │ │ └── UNMET DEPENDENCY mime-types@^2.1.12 │ └── UNMET DEPENDENCY proxy-from-env@^1.1.0 ├── UNMET DEPENDENCY dropbox-v2-api@^2.5.6 ├─┬ express@4.18.2 │ ├─┬ accepts@1.3.8 │ │ ├─┬ mime-types@2.1.35 │ │ │ └── mime-db@1.52.0 │ │ └── negotiator@0.6.3 │ ├── UNMET DEPENDENCY array-flatten@1.1.1 │ ├─┬ body-parser@1.20.1 │ │ ├── UNMET DEPENDENCY bytes@3.1.2 │ │ ├── UNMET DEPENDENCY content-type@~1.0.4 │ │ ├── UNMET DEPENDENCY debug@2.6.9 │ │ ├── depd@2.0.0 deduped │ │ ├── UNMET DEPENDENCY destroy@1.2.0 │ │ ├── UNMET DEPENDENCY http-errors@2.0.0 │ │ ├── UNMET DEPENDENCY iconv-lite@0.4.24 │ │ ├── UNMET DEPENDENCY on-finished@2.4.1 │ │ ├── qs@6.11.0 deduped │ │ ├── UNMET DEPENDENCY raw-body@2.5.1 │ │ ├── UNMET DEPENDENCY type-is@~1.6.18 │ │ └── UNMET DEPENDENCY unpipe@1.0.0 │ ├── UNMET DEPENDENCY content-disposition@0.5.4 │ ├── UNMET DEPENDENCY content-type@~1.0.4 │ ├── cookie@0.5.0 │ ├── UNMET DEPENDENCY cookie-signature@1.0.6 │ ├── UNMET DEPENDENCY debug@2.6.9 │ ├── depd@2.0.0 │ ├── UNMET DEPENDENCY encodeurl@~1.0.2 │ ├── UNMET DEPENDENCY escape-html@~1.0.3 │ ├── UNMET DEPENDENCY etag@~1.8.1 │ ├── UNMET DEPENDENCY finalhandler@1.2.0 │ ├── UNMET DEPENDENCY fresh@0.5.2 │ ├── UNMET DEPENDENCY http-errors@2.0.0 │ ├── UNMET DEPENDENCY merge-descriptors@1.0.1 │ ├── UNMET DEPENDENCY methods@~1.1.2 │ ├── UNMET DEPENDENCY on-finished@2.4.1 │ ├── UNMET DEPENDENCY parseurl@~1.3.3 │ ├── UNMET DEPENDENCY path-to-regexp@0.1.7 │ ├── UNMET DEPENDENCY proxy-addr@~2.0.7 │ ├─┬ qs@6.11.0 │ │ └── UNMET DEPENDENCY side-channel@^1.0.4 │ ├── UNMET DEPENDENCY range-parser@~1.2.1 │ ├── safe-buffer@5.2.1 │ ├── UNMET DEPENDENCY send@0.18.0 │ ├── UNMET DEPENDENCY serve-static@1.15.0 │ ├── UNMET DEPENDENCY setprototypeof@1.2.0 │ ├── UNMET DEPENDENCY statuses@2.0.1 │ ├── UNMET DEPENDENCY type-is@~1.6.18 │ ├── UNMET DEPENDENCY utils-merge@1.0.1 │ └── UNMET DEPENDENCY vary@~1.1.2 ├─┬ fs-extra@10.1.0 │ ├── UNMET DEPENDENCY graceful-fs@^4.2.0 │ ├── UNMET DEPENDENCY jsonfile@^6.0.1 │ └── UNMET DEPENDENCY universalify@^2.0.0 ├── UNMET DEPENDENCY ftp@^0.3.10 ├── UNMET DEPENDENCY google-auth-library@^8.6.0 ├── UNMET DEPENDENCY node-schedule@^2.1.0 ├── UNMET DEPENDENCY node-wol@^0.1.1 ├── UNMET DEPENDENCY request@^2.88.2 ├── UNMET DEPENDENCY tar-fs@^2.1.1 └── UNMET DEPENDENCY webdav@^4.11.0

npm ERR! missing: @googleapis/drive@^4.0.0, required by iobroker.backitup@2.5.7 npm ERR! missing: dropbox-v2-api@^2.5.6, required by iobroker.backitup@2.5.7 npm ERR! missing: ftp@^0.3.10, required by iobroker.backitup@2.5.7 npm ERR! missing: google-auth-library@^8.6.0, required by iobroker.backitup@2.5.7 npm ERR! missing: node-schedule@^2.1.0, required by iobroker.backitup@2.5.7 npm ERR! missing: node-wol@^0.1.1, required by iobroker.backitup@2.5.7 npm ERR! missing: request@^2.88.2, required by iobroker.backitup@2.5.7 npm ERR! missing: tar-fs@^2.1.1, required by iobroker.backitup@2.5.7 npm ERR! missing: webdav@^4.11.0, required by iobroker.backitup@2.5.7 npm ERR! missing: @types/node@*, required by @types/iobroker@4.0.5 npm ERR! missing: proxy-from-env@^1.1.0, required by axios@1.1.3 npm ERR! missing: asynckit@^0.4.0, required by form-data@4.0.0 npm ERR! missing: combined-stream@^1.0.8, required by form-data@4.0.0 npm ERR! missing: mime-types@^2.1.12, required by form-data@4.0.0 npm ERR! missing: array-flatten@1.1.1, required by express@4.18.2 npm ERR! missing: content-disposition@0.5.4, required by express@4.18.2 npm ERR! missing: content-type@~1.0.4, required by express@4.18.2 npm ERR! missing: cookie-signature@1.0.6, required by express@4.18.2 npm ERR! missing: debug@2.6.9, required by express@4.18.2 npm ERR! missing: encodeurl@~1.0.2, required by express@4.18.2 npm ERR! missing: escape-html@~1.0.3, required by express@4.18.2 npm ERR! missing: etag@~1.8.1, required by express@4.18.2 npm ERR! missing: finalhandler@1.2.0, required by express@4.18.2 npm ERR! missing: fresh@0.5.2, required by express@4.18.2 npm ERR! missing: http-errors@2.0.0, required by express@4.18.2 npm ERR! missing: merge-descriptors@1.0.1, required by express@4.18.2 npm ERR! missing: methods@~1.1.2, required by express@4.18.2 npm ERR! missing: on-finished@2.4.1, required by express@4.18.2 npm ERR! missing: parseurl@~1.3.3, required by express@4.18.2 npm ERR! missing: path-to-regexp@0.1.7, required by express@4.18.2 npm ERR! missing: proxy-addr@~2.0.7, required by express@4.18.2 npm ERR! missing: range-parser@~1.2.1, required by express@4.18.2 npm ERR! missing: send@0.18.0, required by express@4.18.2 npm ERR! missing: serve-static@1.15.0, required by express@4.18.2 npm ERR! missing: setprototypeof@1.2.0, required by express@4.18.2 npm ERR! missing: statuses@2.0.1, required by express@4.18.2 npm ERR! missing: type-is@~1.6.18, required by express@4.18.2 npm ERR! missing: utils-merge@1.0.1, required by express@4.18.2 npm ERR! missing: vary@~1.1.2, required by express@4.18.2 npm ERR! missing: bytes@3.1.2, required by body-parser@1.20.1 npm ERR! missing: content-type@~1.0.4, required by body-parser@1.20.1 npm ERR! missing: debug@2.6.9, required by body-parser@1.20.1 npm ERR! missing: destroy@1.2.0, required by body-parser@1.20.1 npm ERR! missing: http-errors@2.0.0, required by body-parser@1.20.1 npm ERR! missing: iconv-lite@0.4.24, required by body-parser@1.20.1 npm ERR! missing: on-finished@2.4.1, required by body-parser@1.20.1 npm ERR! missing: raw-body@2.5.1, required by body-parser@1.20.1 npm ERR! missing: type-is@~1.6.18, required by body-parser@1.20.1 npm ERR! missing: unpipe@1.0.0, required by body-parser@1.20.1 npm ERR! missing: side-channel@^1.0.4, required by qs@6.11.0 npm ERR! missing: graceful-fs@^4.2.0, required by fs-extra@10.1.0 npm ERR! missing: jsonfile@^6.0.1, required by fs-extra@10.1.0 npm ERR! missing: universalify@^2.0.0, required by fs-extra@10.1.0 root@ioBrokerTWS:/opt/iobroker/node_modules/iobroker.backitup# ^C`

simatec commented 1 year ago

Sieht gut aus... Ich würde einfach mal den Container durchstarten

mibr85 commented 1 year ago

leider keine änderung :-(

simatec commented 1 year ago

Kannst du die Backups Lokal abrufen? Prüfe dort mal bitte die rechte der Backups, die unter /opt/iobroker/backups liegen

ls -lah /opt/iobroker/backups

mibr85 commented 1 year ago

image

simatec commented 1 year ago

Lass mal den iob fix laufen und beobachte dann mal die nächsten Backups. Werden denn in Backitup die lokalen Backups gelistet?

mibr85 commented 1 year ago

wenn ich auf Sicherungen Abrufen clicke image

kommt das fenster und es passsiert nix auch nach 30min nicht image

bei lokal das selbe spiel image

simatec commented 1 year ago

Ich gehe davon aus, dass deine Rechte nicht korrekt sind. Was hast du denn für eine Container Version laufen? Da schonmal ein Update des Containers gemacht?

simatec commented 1 year ago

Wie ist hier der Stand beim testen?

mibr85 commented 1 year ago

Sorry hatte bis jetzt keine Zeit zum nachschauen: grafik Update vom Container hab ich noch nicht gemacht.

mibr85 commented 1 year ago

ich sollte mal updaten: grafik

mibr85 commented 1 year ago

Container Update durchgeführt. grafik

Problem weiterhin vorhanden: grafik

simatec commented 1 year ago

Hast du den iobroker fix laufen lassen? Passen deine Pfade alle?

prüfe die nochmal und speichere die Settings von Backitup.

Unbedingt den Fixer laufen lassen. Update von Backitup durchführen.

Alle Settings nochmal prüfen.

Wenn alles nicht hilft, sichere die Settings von Backitup, entferne ihn in den Instanzen und im Tab Adapter.

Installiere ihn nach einem Neustart des Containers neu und spiele die Settings zurück.