Everything posted by KluthR
-
[Plugin] CA Appdata Backup / Restore v2.5
Cant tell. the next version has debug infos for more diagnosis. are you able to start the container manually? do you have enabled Auto Update?
-
[Plugin] CA Appdata Backup / Restore v2.5
Of course, because it IS an issue. But you are able to ignore it by setting.
-
[Plugin] CA Appdata Backup / Restore v2.5
Do you see „DEBUG: dockerInfo written to /tmp/“ in the logs?
-
[Plugin] CA Appdata Backup / Restore v2.5
Thats coming with the next big update. For now, just extract it yourself and pick up what you need.
-
[Plugin] CA Appdata Backup / Restore v2.5
Could you do this here as well and give the output back?
-
[Plugin] CA Appdata Backup / Restore v2.5
I dont think so. You can see that this rsync always deletes the backup set. So you only have one working backup. Now it should grow to the „keep x backups“ setting. is it always this calendar app thats failing? Could you look into it whats inside? since your nextcloud container is stopped, there is nothing accessing it. Weird. some posts ago I asked an user to add some diag code, could you do the same? Dont have the post link, Iam at my mobile phone.
-
[Plugin] CA Appdata Backup / Restore v2.5
I found one issue, but I dont know if thats your issue: Your usbBackup Destination is set to /mnt/user/Backups/. Thats the same dir for the destination. Since the USB Backup makes an 1:1 copy of it, it also deletes EVERY other data (including your backups). So your backups are currently broken. Please create a dir names "USBBackup" or similar INSIDE /mnt/user/Backups/ and let the USB backup path point to it. Then try again, please. You can safely clear /mnt/user/Backups/ before - its broken anyway. That is one thing, which will be fixed in the new version. Got less time this week, but I try to finish it asap.
-
[Plugin] CA Appdata Backup / Restore v2.5
Could you share this file as attachment? /boot/config/plugins/ca.backup2/BackupOptions.json
-
[Plugin] CA Appdata Backup / Restore v2.5
Hmm. Whats happening, when you run a manual backup? Does it raise the same error?
-
[Plugin] CA Appdata Backup / Restore v2.5
Please post the full backup log as code or as attachmemt, thanks.
-
[Plugin] CA Appdata Backup / Restore v2.5
Okay, thanks for that info, I will focus my tests on that.
-
[Plugin] CA Appdata Backup / Restore v2.5
Thats already possible? I would bet, if you declare something like /mnt/cache/appdata/myfolder/*.ext that would ignore all .ext files. We will see if there are some additions needed after next release.
-
[Plugin] CA Appdata Backup / Restore v2.5
Idk what happened at your end tonight, but this debug thing is working on my side: I dont event know what caused a removal of that folder, sorry. This is being logged everytime a error is detected + overhead of this debug adaption.
-
[Plugin] CA Appdata Backup / Restore v2.5
The socket error could be fixed by putting it to the exclusion list. The main issue is the file ./radarr/MediaCover/129/fanart-360.jpg: which seems to be changed during backup. I dont know why, because all dockers seem to be stopped. Yet another user with this issue. I dont get whats causing it. Could you do me a favor? Please open /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php, go to line 317. 317 should be: backupLog("tar verify failed!"); DIRECTLY AFTER that line, paste: $debug = "/tmp/ca.backup.debug.".uniqid(); file_put_contents($debug, json_encode($dockerClient->getDockerContainers(), JSON_PRETTY_PRINT)); $output = $outval = null; exec("docker ps -a", $output, $outval); file_put_contents($debug, json_encode($output, JSON_PRETTY_PRINT), FILE_APPEND); backupLog("DEBUG: dockerInfo written to /tmp/"); Save and let the baclup run again (or do it manually). The log should post the DEBUB: line. If so, please attach (or send via PM) all /tmp/ca.backup-debug* files. Maybe I see, if some docker things are going on.
-
[Plugin] CA Appdata Backup / Restore v2.5
The log is telling you whats wrong. Please attach the full log 1:1 for more analysis.
-
[Plugin] CA Appdata Backup / Restore v2.5
But in most cases they found the reason. you could do an „lsof path-to-the-changed-file“ just now. Maybe there is something
-
[Plugin] CA Appdata Backup / Restore v2.5
Something is still running and/or accessing these files during backup. Doesnt need to be these dockers, could be anything. Maybe I have to add some kind of helper which tries to find the root cause. Like lsof which can tell infos about open files.
-
[Plugin] CA Appdata Backup / Restore v2.5
No, it just open fine and is zoomable 🤔 If not: first beta will give you detailed view
-
[Plugin] CA Appdata Backup / Restore v2.5
Hmm 🤔. Well see 😂. Dont even know it yet
-
[Plugin] CA Appdata Backup / Restore v2.5
Okay, then I include the option as well. Maybe not that bad. But the vdisks are missing then.
-
[Plugin] CA Appdata Backup / Restore v2.5
Interesting. Because the image will always be backed up while vms are running. Thats not consistent at all 🤔
-
[Plugin] CA Appdata Backup / Restore v2.5
Finally, I "finished" the final new UI for the settings part. I oriented myself on how Unraid does it. (DEV-Sidenote: Wow, these many code documentation of the webgui-code is gorgeous... NOT! Maybe I start to add some to important things...) However, the current design looks like this: I expanded the important help blocks for this screenshot. Can we work with this?
-
[Plugin] CA Appdata Backup / Restore v2.5
-
[Plugin] CA Appdata Backup / Restore v2.5
Is already on my ToDo Iam doing an overhaul currently, so theres no update yet.
-
[Plugin] CA Appdata Backup / Restore v2.5
Depends, if containers depends on each other. The new update allows some control of it