-
Notifications
You must be signed in to change notification settings - Fork 617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nexcloud down and daily backup stuck #4736
Comments
As @szaimen suggested, removing the file |
Thanks for the report! My idea is to add a warning to the AIO interface what to do if it should be stuck. |
My backup got stuck last night as well. First time this has happened in a few months. |
I also encountered this. New installation, first backup went without a problem, secont time it got stuck. I manually killed borg container, deleted whole borg repo and retried from the start with initial backup and after it finished successfully I tried changing 1 file in nextcloud and tried creating new backup manually and it's stuck unfortunately. Borg container:
I see that the borg is doing "something" but it's not doing much, during initial backup it was using much more IO around 60Mb read/writes. My backup is 1.2tb so with 400kb it will take approximately forever to scan it at this rate. EDIT:
Is there a way to disable backup of data directory in this case? It's extremely slow compared to ZFS snapshots. EDIT2:
Another 100mb backup took an 1h15m. Is there something wrong here? Shouldn't it be faster? The system wasnt under any significant load nor it isn't that slow:
|
I am not sure if this is a separate issue or belongs here: My backup isn't stuck, but my AIO interface shows that it's running even though it has finished. I only noticed this after a reboot when I saw that the nextcloud containers weren't running. Restarting the mastercontainer or the backup container didn't help (the backup ran through, but the containers didn't start). The AIO interface still shows the backup is running. I manually started the nextcloud containers and it's working fine apart from the AIO interface: Mastercontainer log:
I am using openmediavault 7 / Debian Bookworm. There was a Docker/containerd update yesterday. Could this be related in any way? Edit: Removing the file |
This is now released with v9.0.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel |
Hello, the backup process is stuck again.
Logs:
I still don't have the feature to manually unblock the backup from the dashboard, because it was implemented for AIO v9. Maybe it is something to investigate? New feature idea: it would be good to add a timestamp next to the log message for better troubleshooting. |
Steps to reproduce
Expected behavior
The backup should start at 4am UTC and finish after a few minutes
Actual behavior
The backup is still ongoing at 2pm UTC (~10hours later)
Host OS
Ubuntu 22.04
Nextcloud AIO version
v8.2.1
Current channel
Can't see it, there is only this message:
Other valuable info
Not sure if relevant but the AIO data dir is on an external ssd, and the backup is stored in a second external drive. I checked the drives and they are fine. I also don't see rsync running, I don't know why the dashboard says backup in progress.
Master container logs:
Watch tower logs:
The text was updated successfully, but these errors were encountered: