Good morning everyone,
When attempting a backup, I get the following error within AIO: database-dump is missing. Cannot perform backup!
I’ve never completed a backup before as this is a fresh installation. Does anyone happen to have any ideas as to what might be causing this error to surface?
Hi, can you look into the database container logs? Ehat is written in there?
I don’t know how much this will help, but this was the only entry within the log:
database-dump is missing. Cannot perform backup!
I left Nextcloud alone to run idly for a few hours and just attempted the backup again and it completed successfully with tons of log files with it finally ending with:
Compacting the archives...
Backup finished successfully on 25.10.2023 - 20:34:55 (00 hours 01 minutes 29 seconds).
Perhaps there was something running in the background that just hadn’t been completed yet? Either way, everything is looking good now. Thanks for the help szaimen!
Hello @Vanimox , I’m facing the same issue on a fresh instance of NC AIO, how long did you have to leave it idle? I’ve left it overnight and still getting the error 
Thank you!
In case it helps, the database log is:
Setting max connections…
chmod: /var/run/postgresql: Operation not permitted
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-10-31 08:06:40.868 CET [14] LOG: starting PostgreSQL 15.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-10-31 08:06:40.868 CET [14] LOG: listening on IPv4 address “0.0.0.0”, port 5432
2023-10-31 08:06:40.868 CET [14] LOG: listening on IPv6 address “::”, port 5432
2023-10-31 08:06:40.869 CET [14] LOG: listening on Unix socket “/var/run/postgresql/.s.PGSQL.5432”
2023-10-31 08:06:40.872 CET [24] LOG: database system was interrupted; last known up at 2023-10-31 08:00:58 CET
2023-10-31 08:06:41.068 CET [24] LOG: database system was not properly shut down; automatic recovery in progress
2023-10-31 08:06:41.070 CET [24] LOG: redo starts at 0/6DFBBC8
2023-10-31 08:06:41.071 CET [24] LOG: invalid record length at 0/6E31518: wanted 24, got 0
2023-10-31 08:06:41.071 CET [24] LOG: redo done at 0/6E314E0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2023-10-31 08:06:41.085 CET [14] LOG: database system is ready to accept connections
Hello @szaimen , I’m sorry to keep posting, but you’re my last hope 
As you can imagine, it’s kind of important to have the backups working and the annoying thing is that I’ve already created several users, uploaded files, configured things…
I’ve tried waiting for hours leaving the nextcloud idle, I’ve tried reproducing the same docker run command in a fresh installation of Ubunt 23 in a VM, and I get exactly the same issue, I’ve tried moving to the beta channel… nothing helps.
The environmental variables that I pass to the container are pretty much the same as I had in Windows using Docker desktop (with the obvious changes in the paths for the data dir). I’m at a loss here…
sudo docker run
–init
–sig-proxy=false
–name nextcloud-aio-mastercontainer
–restart always
–publish 80:80
–publish 8080:8080
–publish 8443:8443
–dns=8.8.8.8
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config
–volume /var/run/docker.sock:/var/run/docker.sock:ro
–env NEXTCLOUD_UPLOAD_LIMIT=100G
–env NEXTCLOUD_MEMORY_LIMIT=1024M
–env SKIP_DOMAIN_VALIDATION=true
–env NEXTCLOUD_DATADIR=“/home/user/ncdata”
nextcloud/all-in-one:latest
I am confused by your question. Starting the backup container should stop all running containers. Is that not what is happening? Can you maybe do a screenrecording of what happens if you click on the Create backup button?
Sorry I didn’t mean to create any confusion. I’m having exactly the same issue as the OP, except in my case it’s not getting solved on its own.
The create backup does indeed stop all containers (except master, of course); but the backup fails due to the “database-dump is missing. Cannot perform backup!” error that Vanimox originally reported. I suspect this is due to something being wrong with the database because its log always states “database system was interrupted;” and “database system was not properly shut down” (see my first post for full log) (even though the database container is stopped graciously by the backup container).
I have used the backup functionality before (in Windows with Docker Desktop) and I am familiar with how it works, (stopping the containers, creating the backup and then updating them if applicable and finally bringing them back online). I don’t think the issue is so much related with the backup container itself, as it is related to why that “database-dump is missing”.
More than happy to do the screen recording if you think it will help, but you won’t see anything out of the ordinary, other than the containers stopping, the backup container attempting to run but failing almost immediately and displaying the aforementioned message in the log that Vanimox and I have shared.
Thank you very much in advance and apologies about the lack of clarity.
Can you please share the database container logs after attempting to Create a backup from the AIO interface?
Many thanks for your lightning quick response.
Sure thing. Here it is:
Setting max connections...
chmod: /var/run/postgresql: Operation not permitted
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-11-02 14:33:37.153 CET [14] LOG: starting PostgreSQL 15.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-11-02 14:33:37.153 CET [14] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-11-02 14:33:37.153 CET [14] LOG: listening on IPv6 address "::", port 5432
2023-11-02 14:33:37.154 CET [14] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-02 14:33:37.158 CET [24] LOG: database system was interrupted; last known up at 2023-11-02 14:28:45 CET
2023-11-02 14:33:37.362 CET [24] LOG: database system was not properly shut down; automatic recovery in progress
2023-11-02 14:33:37.364 CET [24] LOG: redo starts at 0/E196430
2023-11-02 14:33:37.366 CET [24] LOG: invalid record length at 0/E1C2770: wanted 24, got 0
2023-11-02 14:33:37.366 CET [24] LOG: redo done at 0/E1C2738 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2023-11-02 14:33:37.381 CET [14] LOG: database system is ready to accept connections
I’ve done a video as well: https://streamable.com/siyjor
The log from the database container doesn’t change when the backup container stops it (i.e. it is the same as when it was last started, in this case, for the video linked above this line)
Can you please press Stop containers and after doing so before starting them again, get the database logs and post them here? I am wondering why apparently the database export fails in your case…
Of course. Unfortunately, it doesn’t change.
Video: 2023-11-02-15-04-49
Log after stopping manually the containers (and before starting them again):
Setting max connections...
chmod: /var/run/postgresql: Operation not permitted
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-11-02 15:03:45.377 CET [14] LOG: starting PostgreSQL 15.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-11-02 15:03:45.377 CET [14] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-11-02 15:03:45.377 CET [14] LOG: listening on IPv6 address "::", port 5432
2023-11-02 15:03:45.378 CET [14] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-02 15:03:45.381 CET [24] LOG: database system was interrupted; last known up at 2023-11-02 15:01:09 CET
2023-11-02 15:03:45.585 CET [24] LOG: database system was not properly shut down; automatic recovery in progress
2023-11-02 15:03:45.588 CET [24] LOG: redo starts at 0/E244DD0
2023-11-02 15:03:45.590 CET [24] LOG: invalid record length at 0/E276308: wanted 24, got 0
2023-11-02 15:03:45.590 CET [24] LOG: redo done at 0/E2762D0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2023-11-02 15:03:45.606 CET [14] LOG: database system is ready to accept connections
I assume you were expecting to see some new lines here following the shutdown instruction… 
Yes, it should trigger the shutdown and database dump automatically when you stop the containers. Not sure why it doesnt do this on your system…
No idea… It is a Ryzen 7 5800H with 32GB of RAM. The options I used for the container are:
sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8080:8080 \
--publish 8443:8443 \
--dns=8.8.8.8 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
--env NEXTCLOUD_UPLOAD_LIMIT=100G \
--env NEXTCLOUD_MEMORY_LIMIT=1024M \
--env SKIP_DOMAIN_VALIDATION=true \
--env NEXTCLOUD_DATADIR="/home/xyz/ncdata" \
nextcloud/all-in-one: latest
which are pretty much identical to what I was using in my previous Intel NUC i5 7260U with 16GB of ram running windows. I added the dns 8.8.8.8 because I saw in some logs that it was complaining about a failed dns resolution… and little else was changed. The datadir is in the home folder, but I don’t think this is a problem. I must say the nextcloud instance works perfectly, fast, responsive, zero (apparent) errors when running it.
The weird thing is, if you take a brand new Ubuntu 23 VM and apply the exact same docker run command, you will get the behaviour I’m experiencing. However, I’ve just done it on a Ubuntu 22 VM and it has worked:
2023-11-02 14:29:23.736 UTC [36] LOG: received fast shutdown request
waiting for server to shut down....2023-11-02 14:29:23.737 UTC [36] LOG: aborting any active transactions
2023-11-02 14:29:23.738 UTC [36] LOG: background worker "logical replication launcher" (PID 42) exited with exit code 1
2023-11-02 14:29:23.740 UTC [37] LOG: shutting down
2023-11-02 14:29:23.741 UTC [37] LOG: checkpoint starting: shutdown immediate
2023-11-02 14:29:23.784 UTC [37] LOG: checkpoint complete: wrote 927 buffers (5.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.039 s, sync=0.002 s, total=0.045 s; sync files=308, longest=0.001 s, average=0.001 s; distance=4227 kB, estimate=4227 kB
2023-11-02 14:29:23.790 UTC [36] LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
2023-11-02 14:29:23.858 UTC [14] LOG: starting PostgreSQL 15.4 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-11-02 14:29:23.858 UTC [14] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-11-02 14:29:23.858 UTC [14] LOG: listening on IPv6 address "::", port 5432
2023-11-02 14:29:23.859 UTC [14] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-11-02 14:29:23.863 UTC [57] LOG: database system was shut down at 2023-11-02 14:29:23 UTC
2023-11-02 14:29:23.868 UTC [14] LOG: database system is ready to accept connections
2023-11-02 14:31:44.979 UTC [104] ERROR: relation "oc_circle_circles" does not exist at character 15
2023-11-02 14:31:44.979 UTC [104] STATEMENT: SELECT * FROM "oc_circle_circles"
2023-11-02 14:33:00.036 UTC [14] LOG: received fast shutdown request
2023-11-02 14:33:00.037 UTC [14] LOG: aborting any active transactions
2023-11-02 14:33:00.037 UTC [192] FATAL: terminating connection due to administrator command
2023-11-02 14:33:00.039 UTC [14] LOG: background worker "logical replication launcher" (PID 60) exited with exit code 1
2023-11-02 14:33:00.045 UTC [55] LOG: shutting down
2023-11-02 14:33:00.047 UTC [55] LOG: checkpoint starting: shutdown immediate
2023-11-02 14:33:00.086 UTC [55] LOG: checkpoint complete: wrote 676 buffers (4.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.034 s, sync=0.005 s, total=0.042 s; sync files=730, longest=0.002 s, average=0.001 s; distance=4325 kB, estimate=4325 kB
2023-11-02 14:33:00.092 UTC [14] LOG: database system is shut down
waiting for server to shut down.... done
server stopped
Database dump successful!
Initializing repository...
using builtin fallback logging configuration
33 self tests completed in 0.24 seconds
Initializing repository at "/mnt/borgbackup/borg"
Key in "<Repository /mnt/borgbackup/borg>" created.
Keep this key safe. Your data will be inaccessible without it.
check_free_space: few segments, not requiring a full free segment
check_free_space: calculated working space for compact as 0 bytes
check_free_space: required bytes 169138, free bytes 3677462528
security: previous location file /root/.config/borg/security/1dc0d98cd06087551073d80c42d27d15f05472c4b6a21b25416972d593f9c4e4/location not found
security: manifest timestamp file /root/.config/borg/security/1dc0d98cd06087551073d80c42d27d15f05472c4b6a21b25416972d593f9c4e4/manifest-timestamp not found
security: determined newest manifest timestamp as
security: remembering previously unknown repository
security: saving state for 1dc0d98cd06087551073d80c42d27d15f05472c4b6a21b25416972d593f9c4e4 to /root/.config/borg/security/1dc0d98cd06087551073d80c42d27d15f05472c4b6a21b25416972d593f9c4e4
security: current location /mnt/borgbackup/borg
security: key type 5
security: manifest timestamp 2023-11-02T14:38:05.953870
security: repository checks ok, allowing access
Synchronizing chunks cache...
Archives: 0, w/ cached Idx: 0, w/ outdated Idx: 0, w/o cached Idx: 0.
Verified integrity of /mnt/borgbackup/borg/index.1
Done.
security: saving state for 1dc0d98cd06087551073d80c42d27d15f05472c4b6a21b25416972d593f9c4e4 to /root/.config/borg/security/1dc0d98cd06087551073d80c42d27d15f05472c4b6a21b25416972d593f9c4e4
security: current location /mnt/borgbackup/borg
security: key type 5
security: manifest timestamp 2023-11-02T14:38:05.953870
By default repositories initialized with this version will produce security
errors if written to with an older version (up to and including Borg 1.0.8).
If you want to use these older versions, you can disable the check by running:
borg upgrade --disable-tam /mnt/borgbackup/borg
See https://borgbackup.readthedocs.io/en/stable/changes.html#pre-1-0-9-manifest-spoofing-vulnerability for details about the security implications.
IMPORTANT: you will need both KEY AND PASSPHRASE to access this repo!
If you used a repokey mode, the key is stored in the repo, but you should back it up separately.
Use "borg key export" to export the key, optionally in printable format.
Write down the passphrase. Store both at safe place(s).
Repository successfully initialized.
Performing backup...
Starting the backup...
Creating archive at "/mnt/borgbackup/borg::20231102_143806-nextcloud-aio"
0 B O 0 B C 0 B D 0 N nextcloud_aio_volumes
zing cache transaction: Reading config
zing cache transaction: Reading chunks
zing cache transaction: Reading files
O 15.11 MB C 15.11 MB D 10 N nextcloud_aio_volu.../Nextcloud Manual.pdf
O 35.24 MB C 35.24 MB D 47 N nextcloud_aio_volu...s/Documents/Readme.md
O 39.16 MB C 39.16 MB D 67 N nextcloud_aio_volu...000010000000000000001
O 40.12 MB C 40.12 MB D 426 N nextcloud_aio_vol...base/base/1/13395_fsm
O 41.68 MB C 40.22 MB D 953 N nextcloud_aio_vol..._database/base/5/3085
O 43.18 MB C 41.43 MB D 1301 N nextcloud_aio_vol...base/base/16384/3576
O 43.32 MB C 41.58 MB D 1982 N nextcloud_aio_vol...ase/base/16384/17809
O 43.62 MB C 41.88 MB D 2330 N nextcloud_aio_vol...MetadataEnvelope.php
O 43.90 MB C 42.15 MB D 2729 N nextcloud_aio_vol...etworksException.php
O 44.17 MB C 42.43 MB D 2992 N nextcloud_aio_vol...11-29/api-2.json.php
B O 44.60 MB C 42.85 MB D 3184 N nextcloud_aio_vo...-rule-set-1.json.php
B O 45.26 MB C 43.52 MB D 3405 N nextcloud_aio_vo...aginators-1.json.php
B O 45.83 MB C 44.08 MB D 3612 N nextcloud_aio_vo...07-14/api-2.json.php
B O 46.61 MB C 44.86 MB D 3930 N nextcloud_aio_vo...overy-control-config
B O 47.28 MB C 45.53 MB D 4207 N nextcloud_aio_vo...h/src/BigInteger.php
B O 47.94 MB C 46.19 MB D 4669 N nextcloud_aio_vo.../PrintableString.php
B O 48.30 MB C 46.56 MB D 5089 N nextcloud_aio_vo...umberMetadata_GM.php
B O 48.59 MB C 46.85 MB D 5407 N nextcloud_aio_vo...umberMetadata_NE.php
B O 50.07 MB C 48.32 MB D 5672 N nextcloud_aio_vo...ng/data/en/86188.php
B O 51.10 MB C 49.34 MB D 5913 N nextcloud_aio_vo...ocale/data/en-fm.php
B O 51.80 MB C 49.98 MB D 6360 N nextcloud_aio_vo.../SeekableWrapper.php
B O 52.36 MB C 50.54 MB D 6760 N nextcloud_aio_vo...openstack/src/Metric
B O 53.22 MB C 51.32 MB D 7062 N nextcloud_aio_vo...a/fr/currencies.json
B O 54.14 MB C 52.24 MB D 7402 N nextcloud_aio_vo.../punic/code/Misc.php
B O 54.61 MB C 52.71 MB D 7722 N nextcloud_aio_vo...onse/MultiStatus.php
B O 55.22 MB C 53.32 MB D 8107 N nextcloud_aio_vo...op/Pop3Exception.php
B O 55.73 MB C 53.82 MB D 8523 N nextcloud_aio_vo...ny/mailer/Mailer.php
B O 56.65 MB C 54.74 MB D 8905 N nextcloud_aio_vo...rorfuncException.php
B O 58.55 MB C 56.64 MB D 9238 N nextcloud_aio_vo...s/activity-10.js.map
B O 62.14 MB C 60.22 MB D 9253 N nextcloud_aio_vo.../activity-783.js.map
B O 65.87 MB C 63.96 MB D 9274 N nextcloud_aio_vo...ivity-sidebar.js.map
B O 66.65 MB C 64.71 MB D 9661 N nextcloud_aio_vo...min_audit/l10n/sr.js
B O 67.70 MB C 65.74 MB D 9952 N nextcloud_aio_vo...cles/l10n/en_GB.json
B O 68.38 MB C 66.36 MB D 10303 N nextcloud_aio_vo...ms/CircleCreate.php
B O 69.07 MB C 66.95 MB D 10651 N nextcloud_aio_vo...r/autoload_real.php
B O 69.39 MB C 67.25 MB D 11068 N nextcloud_aio_vo...board/l10n/zh_CN.js
B O 70.17 MB C 67.97 MB D 11370 N nextcloud_aio_vo...ption/Forbidden.php
B O 70.80 MB C 68.55 MB D 11718 N nextcloud_aio_vo...cryption/l10n/sl.js
B O 71.34 MB C 69.02 MB D 12041 N nextcloud_aio_vo...deration/l10n/fi.js
B O 71.91 MB C 69.55 MB D 12298 N nextcloud_aio_vo...files/l10n/es_PR.js
B O 72.63 MB C 70.25 MB D 12561 N nextcloud_aio_vo...ind/smb/src/ACL.php
B O 73.42 MB C 70.96 MB D 12889 N nextcloud_aio_vo...nitionParameter.php
B O 76.17 MB C 73.71 MB D 12985 N nextcloud_aio_vo...e-Japan1-UCS2.bcmap
B O 77.43 MB C 74.97 MB D 13223 N nextcloud_aio_vo...a/viewer.properties
B O 79.96 MB C 77.49 MB D 13407 N nextcloud_aio_vo...htclick/css/app.css
B O 80.55 MB C 78.02 MB D 13715 N nextcloud_aio_vo...haring/l10n/gl.json
B O 81.20 MB C 78.65 MB D 13963 N nextcloud_aio_vo...shbin/l10n/es_NI.js
B O 81.60 MB C 79.02 MB D 14327 N nextcloud_aio_vo...eVersionBackend.php
B O 86.47 MB C 81.29 MB D 14571 N nextcloud_aio_vo...d/package-lock.json
B O 87.59 MB C 82.38 MB D 14820 N nextcloud_aio_vo...nector/l10n/eu.json
B O 89.92 MB C 84.69 MB D 15077 N nextcloud_aio_vo...ment_-4efa53.js.map
B O 91.21 MB C 85.94 MB D 15426 N nextcloud_aio_vo...s/oauth2/l10n/nl.js
B O 92.88 MB C 87.60 MB D 15713 N nextcloud_aio_vo...cy/lists/list-4.php
B O 96.73 MB C 91.43 MB D 15723 N nextcloud_aio_vo...olicy/composer.lock
B O 99.51 MB C 94.21 MB D 15736 N nextcloud_aio_vo.../photos-main.js.map
B O 103.41 MB C 98.11 MB D 15758 N nextcloud_aio_v...hotos-public.js.map
B O 105.05 MB C 99.74 MB D 16005 N nextcloud_aio_v...ner/TagListener.php
B O 109.33 MB C 104.00 MB D 16184 N nextcloud_aio_v...ivacy/l10n/vi.json
B O 110.88 MB C 105.52 MB D 16551 N nextcloud_aio_v...sources/l10n/is.js
B O 112.39 MB C 106.98 MB D 16971 N nextcloud_aio_v...tings/l10n/af.json
B O 114.39 MB C 108.86 MB D 17210 N nextcloud_aio_v...lopment.notice.php
B O 115.39 MB C 109.78 MB D 17662 N nextcloud_aio_v...lient/l10n/tr.json
B O 116.91 MB C 111.29 MB D 18001 N nextcloud_aio_v...p/parallel/LICENSE
B O 117.52 MB C 111.88 MB D 18487 N nextcloud_aio_v...mmittee-machine.md
B O 117.85 MB C 112.21 MB D 18776 N nextcloud_aio_v...tringConverter.php
B O 118.21 MB C 112.57 MB D 19153 N nextcloud_aio_v.../ext/kernel/file.h
B O 118.87 MB C 113.15 MB D 19557 N nextcloud_aio_v...UsedController.php
B O 121.14 MB C 115.41 MB D 19913 N nextcloud_aio_v...s/highlight/ini.js
B O 122.13 MB C 116.40 MB D 20257 N nextcloud_aio_v...ighlight/step21.js
B O 124.36 MB C 118.63 MB D 20380 N nextcloud_aio_v...s/text-text.js.map
B O 127.36 MB C 121.63 MB D 20383 N nextcloud_aio_v...text-viewer.js.map
B O 130.30 MB C 124.57 MB D 20384 N nextcloud_aio_v...text/js/vendors.js
B O 133.98 MB C 128.26 MB D 20386 N nextcloud_aio_v.../js/vendors.js.map
B O 135.90 MB C 130.14 MB D 20573 N nextcloud_aio_v.../Db/StepMapper.php
B O 148.01 MB C 142.25 MB D 20667 N nextcloud_aio_v...ritz-sea-spray.jpg
B O 155.08 MB C 149.29 MB D 20884 N nextcloud_aio_v...upcodes/l10n/cs.js
B O 156.75 MB C 150.93 MB D 21236 N nextcloud_aio_v...otp/vendor/rullzer
B O 158.14 MB C 152.13 MB D 21530 N nextcloud_aio_v...ldap/l10n/zh_CN.js
B O 160.81 MB C 154.78 MB D 21789 N nextcloud_aio_v...viewer-main.js.map
B O 161.54 MB C 155.49 MB D 22164 N nextcloud_aio_v...wengine/l10n/el.js
B O 163.96 MB C 157.88 MB D 22601 N nextcloud_aio_v...dmin/_images/8.png
B O 171.72 MB C 165.63 MB D 22827 N nextcloud_aio_v...rces/index.rst.txt
B O 176.57 MB C 170.48 MB D 23033 N nextcloud_aio_v...calendar_event.png
B O 185.44 MB C 179.35 MB D 23173 N nextcloud_aio_v...s-setup-dialog.png
B O 196.49 MB C 187.39 MB D 23291 N nextcloud_aio_v...ore/signature.json
B O 201.33 MB C 192.23 MB D 23311 N nextcloud_aio_v...toSans-Regular.ttf
B O 203.58 MB C 194.41 MB D 23625 N nextcloud_aio_v...ud/core/l10n/he.js
B O 240.04 MB C 195.60 MB D 23771 N nextcloud_aio_v...low/authpicker.php
B O 243.10 MB C 198.67 MB D 23791 N nextcloud_aio_v...core-common.js.map
B O 247.29 MB C 202.85 MB D 23791 N nextcloud_aio_v...core-common.js.map
B O 250.50 MB C 206.06 MB D 23946 N nextcloud_aio_v...status-menu.js.map
B O 252.05 MB C 207.61 MB D 24453 N nextcloud_aio_v...private/Federation
B O 253.02 MB C 208.57 MB D 24956 N nextcloud_aio_v...e/URLGenerator.php
B O 253.59 MB C 209.15 MB D 25508 N nextcloud_aio_v...tion/IRegistry.php
B O 258.83 MB C 214.25 MB D 25695 N nextcloud_aio_v...arch64/notify_push
B O 264.62 MB C 220.04 MB D 25696 N nextcloud_aio_v.../armv7/notify_push
B O 269.75 MB C 225.17 MB D 25697 N nextcloud_aio_v...x86_64/notify_push
B O 274.35 MB C 229.76 MB D 25731 N nextcloud_aio_v...asks/img/tasks.png
B O 277.56 MB C 232.96 MB D 25735 N nextcloud_aio_v...s/js/tasks-main.js
B O 282.25 MB C 237.66 MB D 25740 N nextcloud_aio_v.../tasks-talk.js.map
B O 285.61 MB C 240.98 MB D 25952 N nextcloud_aio_v...tes-commons.js.map
B O 289.32 MB C 244.68 MB D 26090 N nextcloud_aio_v...s/notes/l10n/pl.js
B O 293.50 MB C 248.86 MB D 26221 N nextcloud_aio_v...ntacts-main.js.map
B O 294.68 MB C 250.00 MB D 26739 N nextcloud_aio_v...ontacts/l10n/ko.js
B O 298.10 MB C 253.41 MB D 26969 N nextcloud_aio_v...nts-booking.js.map
B O 302.67 MB C 257.98 MB D 26988 N nextcloud_aio_v...s/calendar-main.js
B O 306.22 MB C 261.53 MB D 27157 N nextcloud_aio_v...nt_locale_gu_js.js
B O 309.17 MB C 264.47 MB D 27400 N nextcloud_aio_v...st_i-f6d773.js.map
B O 311.90 MB C 267.16 MB D 27739 N nextcloud_aio_v...collections.js.map
B O 315.73 MB C 270.99 MB D 27756 N nextcloud_aio_v.../deck-reference.js
B O 320.74 MB C 276.00 MB D 27765 N nextcloud_aio_v...s/deck-talk.js.map
B O 325.03 MB C 280.29 MB D 27781 N nextcloud_aio_v...E_common_js.js.map
B O 326.33 MB C 281.56 MB D 28200 N nextcloud_aio_v...ser/installed.json
iles cache
hunks cache
ache config
----------------------------------------------------------------------
Repository: /mnt/borgbackup/borg
Archive name: 20231102_143806-nextcloud-aio
Archive fingerprint: d6a2cc8d411a8717b9c47bc2366ba9db805283b44a676ad1a294c7daaa64b2b3
Time (start): Thu, 2023-11-02 14:38:07
Time (end): Thu, 2023-11-02 14:38:31
Duration: 23.56 seconds
Number of files: 28264
Utilization of max. archive size: 0%
------------------------------------------------------------------------------
Original size Compressed size Deduplicated size
This archive: 953.58 MB 326.40 MB 281.58 MB
All archives: 953.57 MB 326.39 MB 283.03 MB
Unique chunks Total chunks
Chunk index: 25633 28135
------------------------------------------------------------------------------
BORG_PRUNE_OPTS are --keep-within=7d --keep-weekly=4 --keep-monthly=6
Pruning the archives...
------------------------------------------------------------------------------
Original size Compressed size Deduplicated size
Deleted data: 0 B 0 B 0 B
All archives: 953.57 MB 326.39 MB 283.03 MB
Unique chunks Total chunks
Chunk index: 25633 28135
------------------------------------------------------------------------------
Compacting the archives...
Backup finished successfully on 02.11.2023 - 14:38:33 (00 hours 00 minutes 27 seconds).
I suppose I have to delete everything… move to Ubuntu 22 and try again? What would be your advice?
Yes, I would always recommend to use Ubuntu LTS for Server things. So Ubuntu 22.04 LTS is the correct choice since as you can see apparently something is not working correctly with Ubuntu 23 which is most likely caused by Ubuntu 23.
Thank you very much, Simon. I’ll do that. I’m sort of new in Linux and thought that Ubuntu 23 was perfectly fine for most home-related activities. As a predominantly Windows user, I have a feeling that I suffer from “versionitis” or the urge for being always up to date with the last version available 
Anyway, thank you ever so much for your help, I hope I didn’t waste much of your time. I truly appreciate the work you and other developers do.
Kind regards,
I am now getting this same behaviour running NC AIO 9.8.0 on an Ubuntu 24.04 LTS server.
Is there anything that can be done besides “just wait some undefined length of time” and maybe it will work?
Kind regards
Hi, please open a new thread for this and post all information about your system, e.g. the output of sudo docker info. Thanks!