Borg backup fail #5701

WouterYVZ · 2024-12-04T10:23:38Z

WouterYVZ
Dec 4, 2024

Hey, I have automatic borg backups enabled in my Nextcloud AIO instance. But it stopped working random out of nowhere.

The logs in the master container tell me this:

2024-12-03T03:04:48.185882311Z Connection to nextcloud-aio-nextcloud (172.22.0.8) 9000 port [tcp/] succeeded!
2024-12-03T03:04:48.185970930Z Sending backup notification...
2024-12-03T03:05:07.976502991Z Daily backup script has finished
2024-12-03T03:05:08.052328886Z Total reclaimed space: 0B
2024-12-03T03:06:08.084216917Z ++ head -1 /mnt/docker-aio-config/data/daily_backup_time
2024-12-03T03:06:08.085322676Z + BACKUP_TIME=03:00
2024-12-03T03:06:08.085368661Z + export BACKUP_TIME
2024-12-03T03:06:08.085381023Z + export DAILY_BACKUP=1
2024-12-03T03:06:08.085390062Z + DAILY_BACKUP=1
2024-12-03T03:06:08.086229220Z ++ sed -n 2p /mnt/docker-aio-config/data/daily_backup_time
2024-12-03T03:06:08.087371165Z + '[' automaticUpdatesAreNotEnabled '!=' automaticUpdatesAreNotEnabled ']'
2024-12-03T03:06:08.087422506Z + export AUTOMATIC_UPDATES=0
2024-12-03T03:06:08.087435312Z + AUTOMATIC_UPDATES=0
2024-12-03T03:06:08.087444438Z + export START_CONTAINERS=1
2024-12-03T03:06:08.087452477Z + START_CONTAINERS=1
2024-12-03T03:06:08.088196277Z ++ sed -n 3p /mnt/docker-aio-config/data/daily_backup_time
2024-12-03T03:06:08.089395712Z + '[' '' '!=' successNotificationsAreNotEnabled ']'
2024-12-03T03:06:08.089439874Z + export SEND_SUCCESS_NOTIFICATIONS=1
2024-12-03T03:06:08.089452947Z + SEND_SUCCESS_NOTIFICATIONS=1
2024-12-03T03:06:08.089461464Z + set +x
2024-12-04T03:00:17.590522653Z Daily backup script has started
2024-12-04T03:00:17.611385543Z Connection to nextcloud-aio-apache (172.22.0.10) 11000 port [tcp/] succeeded!
2024-12-04T03:00:17.630769290Z Creating daily backup...
2024-12-04T03:00:39.072437955Z
2024-12-04T03:00:39.072460498Z Fatal error: Uncaught Exception: Could not create container nextcloud-aio-borgbackup: Client error: POST http://127.0.0.1/v1.41/containers/create?name=nextcloud-aio-borgbackup resulted in a 400 Bad Request response:
2024-12-04T03:00:39.072465683Z {"message":"invalid mount config for type "bind": bind source path does not exist: /mnt/backup/cloud"}
2024-12-04T03:00:39.072469723Z
2024-12-04T03:00:39.072472460Z in /var/www/docker-aio/php/src/Docker/DockerActionManager.php:598
2024-12-04T03:00:39.072475583Z Stack trace:
2024-12-04T03:00:39.072478593Z #0 /var/www/docker-aio/php/src/Controller/DockerController.php(65): AIO\Docker\DockerActionManager->CreateContainer(Object(AIO\Container\Container))
2024-12-04T03:00:39.072482700Z #1 /var/www/docker-aio/php/src/Controller/DockerController.php(102): AIO\Controller\DockerController->PerformRecursiveContainerStart('nextcloud-aio-b...')
2024-12-04T03:00:39.072494158Z #2 /var/www/docker-aio/php/src/Cron/CreateBackup.php(17): AIO\Controller\DockerController->startBackup()
2024-12-04T03:00:39.072497614Z #3 {main}
2024-12-04T03:00:39.072500364Z thrown in /var/www/docker-aio/php/src/Docker/DockerActionManager.php on line 598
2024-12-04T03:00:39.093739577Z Something seems to be wrong: the borg container should be started at this step.
2024-12-04T03:00:39.110260688Z Starting containers without updating them...
2024-12-04T03:00:41.431340668Z Waiting for the Nextcloud container to start
2024-12-04T03:01:11.460116372Z Connection to nextcloud-aio-nextcloud (172.22.0.8) 9000 port [tcp/*] succeeded!
2024-12-04T03:01:11.460172139Z Sending backup notification...
2024-12-04T03:01:11.483544816Z Daily backup script has finished
2024-12-04T03:01:11.573314709Z Total reclaimed space: 0B
2024-12-04T03:02:11.615838088Z ++ head -1 /mnt/docker-aio-config/data/daily_backup_time
2024-12-04T03:02:11.616692321Z + BACKUP_TIME=03:00
2024-12-04T03:02:11.616729105Z + export BACKUP_TIME
2024-12-04T03:02:11.616918779Z + export DAILY_BACKUP=1
2024-12-04T03:02:11.616952747Z + DAILY_BACKUP=1
2024-12-04T03:02:11.617829662Z ++ sed -n 2p /mnt/docker-aio-config/data/daily_backup_time
2024-12-04T03:02:11.618946147Z + '[' automaticUpdatesAreNotEnabled '!=' automaticUpdatesAreNotEnabled ']'
2024-12-04T03:02:11.618981384Z + export AUTOMATIC_UPDATES=0
2024-12-04T03:02:11.618990583Z + AUTOMATIC_UPDATES=0
2024-12-04T03:02:11.618996763Z + export START_CONTAINERS=1
2024-12-04T03:02:11.619003267Z + START_CONTAINERS=1
2024-12-04T03:02:11.619728849Z ++ sed -n 3p /mnt/docker-aio-config/data/daily_backup_time
2024-12-04T03:02:11.620786217Z + '[' '' '!=' successNotificationsAreNotEnabled ']'
2024-12-04T03:02:11.620823252Z + export SEND_SUCCESS_NOTIFICATIONS=1
2024-12-04T03:02:11.620831728Z + SEND_SUCCESS_NOTIFICATIONS=1
2024-12-04T03:02:11.620838364Z + set +x
2024-12-04T10:14:27.970849874Z Deleting duplicate sessions

I hope someone could help me with this matter.

Answered by szaimen

Dec 5, 2024

Can you re-try after removing /mnt/backup/cloud from the list?

View full answer

WouterYVZ · 2024-12-04T10:33:39Z

WouterYVZ
Dec 4, 2024
Author

Also, the 2024-12-04T03:00:39.072465683Z {"message":"invalid mount config for type "bind": bind source path does not exist: /mnt/backup/cloud"} is something else that did not cause this. This is an extra mount, but this problem existed before I even put that extra mount there.

1 reply

szaimen Dec 5, 2024
Maintainer

Can you re-try after removing /mnt/backup/cloud from the list?

Answer selected by WouterYVZ

WouterYVZ · 2024-12-04T21:57:43Z

WouterYVZ
Dec 4, 2024
Author

These are the logs from the backup container:
2024-12-04T21:52:51.429736405Z Creating archive at "/mnt/borgbackup/borg::20241204_215251-nextcloud-aio" 2024-12-04T21:56:23.639937522Z /backupscript.sh: line 309: 37 Segmentation fault borg create "${BORG_OPTS[@]}" "${BORG_EXCLUDE[@]}" "::$CURRENT_DATE-nextcloud-aio" "/nextcloud_aio_volumes/" --exclude-from /borg_excludes 2024-12-04T21:56:23.639962402Z Deleting the failed backup archive... 2024-12-04T21:56:23.946686008Z Killed stale lock nextcloud-aio-borgbackup.37-0. 2024-12-04T21:56:24.047686531Z Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0. 2024-12-04T21:56:24.047753827Z Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0. 2024-12-04T21:56:24.126966226Z Killed stale lock nextcloud-aio-borgbackup.37-0. 2024-12-04T21:56:24.227961740Z Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0. 2024-12-04T21:56:24.228044089Z Removed stale exclusive roster lock for host nextcloud-aio-borgbackup pid 37 thread 0. 2024-12-04T21:56:24.300682472Z Archive 20241204_215251-nextcloud-aio not found (1/1).

1 reply

szaimen Dec 5, 2024
Maintainer

This looks like a general borg problem. Can you open an issue here?
https://github.com/borgbackup/borg/issues

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Borg backup fail #5701

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 2 replies

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Borg backup fail #5701

WouterYVZ Dec 4, 2024

Replies: 2 comments · 2 replies

WouterYVZ Dec 4, 2024 Author

szaimen Dec 5, 2024 Maintainer

WouterYVZ Dec 4, 2024 Author

szaimen Dec 5, 2024 Maintainer

WouterYVZ
Dec 4, 2024

Replies: 2 comments 2 replies

WouterYVZ
Dec 4, 2024
Author

szaimen Dec 5, 2024
Maintainer

WouterYVZ
Dec 4, 2024
Author

szaimen Dec 5, 2024
Maintainer