-
Notifications
You must be signed in to change notification settings - Fork 600
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Daily borg backup locked at creating archive #4994
Comments
Have the same issue.
At this point master container continues to wait indefinitely. Backup container logs are as follows:
Backup location is on a local hard drive, always mounted. |
Hm... I fear I still cannot reproduce this on my test server. Can you maybe post the output of |
Here you are, with password masked: |
Thanks! Can you run |
Also, it looks like you are running docker as snap installation. Doing this is disrecommended by the docker maintainers afaik and might result in weird behaviours like this. I would really recommend the "normal", native install of docker. See https://docs.docker.com/engine/install/#supported-platforms or use the convenience script: |
Mounts are as follows:
So the Re-installing docker would wreak havoc, I'm afraid. I have quite a lot of containers running. |
So In any case I'll move this back to discussions since I cannot reproduce it. I'll be happy to help further if there is some proof that this is actually caused by AIO and not by the storage or docker configuration. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Discussed in #4895
Originally posted by Jycreyn June 26, 2024
Steps to reproduce
Expected behavior
Should backup, but after 10 hours, we have to kill it manually because we need to work ....
Actual behavior
It get stuck at "creating archive "
Host OS
debian 12
Nextcloud AIO version
Nextcloud AIO v9.0.1
Current channel
latest
Other valuable info
borg logs : Performing backup...
Starting the backup...
Killed stale lock nextcloud-aio-borgbackup.37-0.
Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0.
Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0.
Killed stale lock nextcloud-aio-borgbackup.37-0.
Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0.
Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0.
Creating archive at "/mnt/borgbackup/borg::20240625_220112-nextcloud-aio"
Note
This issue is already affecting multiple users with different setups, and thus cannot be considered just a question.
The proposed answer that the backup location is unavailable does not hold true in several cases.
Something is not right with automatic daily backups.
See the discussion thread attached at the top for details.
The text was updated successfully, but these errors were encountered: