A few months ago I changed the location of Duplicity backups to my local NAS ( smb://wdmycloud/xxxxx/ ) and it’s been working fine until last week. But now I get - BackUp failed “No such file or directory”.
As far as I’m aware nothing has changed.
I can see the BackUp location, ( DuplictyBackUps ), in Files, where it shows 1.7TB free, and navigate within it, but backups now fail.
I created a new backup folder in the same location but that didn’t work either.
Any suggestions as to what to look at and what to look for to resolve this?
Yikes - thanks for the report! It is odd that it would suddenly stop working!
One way to grab logs is to go into the About menu and there’s debugging / system info in there, which should include logs from the last run. Can you post that here? Maybe that would have useful info.
I dont see anything suspicious there… sometimes filesystem error messages like that are really about the SOURCE system (like, a problem running out of temporary space on the source, rather than running out of space on the target system).
Does your own machine have plenty of disk space?
Actually… I really don’t see anything suspicious in that log… did you grab that debugging info after a failed backup? If so, that tells me that Deja Dup itself (rather than the underlying duplicity tool…) hmmm not sure where we would be generating that message though.
The source laptop running Ubuntu 22.04.3 LTS has plenty of spare memory capacity. Very little is stored on the machine most is in the cloud.
As far as I’m aware there have been no significant changes since the last successful back up a couple of weeks ago.
I tried to do another backup manually just before posting this and spotted a few differences, which don’t mean a great deal to me, in the debug info, which I’ve posted below - hopefully the differences mean something to you.
System Details:
OS=Ubuntu 22.04.3 LTS
Desktop=ubuntu
Locale=en_GB.UTF-8
Home=/home/bnagq
Version=42.9
Tool Name=Duplicity
Tool Version=0.8.21
GSettings:
[org.gnome.DejaDup]
exclude-list=['$TRASH', '$DOWNLOAD', '/home/bnagq/cvdjotn', '/home/bnagq/.ayalvbt', '/home/bnagq/.qpcnscv-uirv']
prompt-check='2020-06-06T05:04:23+00'
include-list=['$HOME']
periodic=false
delete-after=90
nag-check='2023-08-07T04:27:10.853738Z'
last-backup='2023-09-07T04:17:15.051265Z'
last-run='2023-09-20T04:33:38.299928Z'
backend='remote'
[org.gnome.DejaDup.Local]
folder='obqdk-cpkcfe'
[org.gnome.DejaDup.Google]
folder='obqdk-cpkcfe'
[org.gnome.DejaDup.Remote]
folder='fsweevxowyhgaju'
uri='smb://nkvwavqtk/bnagq/'
Latest Duplicity Log:
INFO 1
. Found 12 volumes in manifest
DEBUG 1
. Registering (mktemp) temporary file /tmp/duplicity-iy2263n9-tempdir/apyeei-ot_qoytv-ag
INFO 1
. Processing local manifest b /home/bnagq/.cache/deja-dup/msycsjdfadsgykpupewxmwlvafdjveye/duplicity-inc.20230831T044127Z.to.20230907T041529Z.manifest (998744)
DEBUG 1
. Found manifest volume 1
DEBUG 1
. Found manifest volume 2
DEBUG 1
. Found manifest volume 3
DEBUG 1
. Found manifest volume 4
DEBUG 1
. Found manifest volume 5
DEBUG 1
. Found manifest volume 6
DEBUG 1
. Found manifest volume 7
DEBUG 1
. Found manifest volume 8
DEBUG 1
. Found manifest volume 9
DEBUG 1
. Found manifest volume 10
DEBUG 1
. Found manifest volume 11
INFO 1
. Found 11 volumes in manifest
DEBUG 1
. Registering (mktemp) temporary file /tmp/duplicity-iy2263n9-tempdir/iybclx-_s_fjdrx-ab
INFO 1
. Making directory /home/bnagq/.cache/deja-dup/metadata
INFO 7 README reg
. Writing README of type reg
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/eycjwn-aij_vktq-j
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/eycjwn-aij_vktq-j
INFO 2 1 123
. Processed volume 1 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/oxlxty-fcdqgody-j
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/oxlxty-fcdqgody-j
INFO 2 2 123
. Processed volume 2 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/xvccwu-dibfq_nd-x
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/xvccwu-dibfq_nd-x
INFO 2 3 123
. Processed volume 3 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/mkjmum-ekpbwmk_-y
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/mkjmum-ekpbwmk_-y
INFO 2 4 123
. Processed volume 4 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/mjifoy-ggivvhfb-m
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/mjifoy-ggivvhfb-m
INFO 2 5 123
. Processed volume 5 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/twjlil-_vvgxwtg-t
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/twjlil-_vvgxwtg-t
INFO 2 6 123
. Processed volume 6 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/aofdmm-majuntry-a
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/aofdmm-majuntry-a
INFO 2 7 123
. Processed volume 7 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/esqexw-_cocrfsi-d
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/esqexw-_cocrfsi-d
INFO 2 8 123
. Processed volume 8 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/apyeei-ot_qoytv-ag
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/apyeei-ot_qoytv-ag
INFO 2 9 123
. Processed volume 9 of 123
INFO 1
. Deleting /tmp/duplicity-iy2263n9-tempdir/iybclx-_s_fjdrx-ab
DEBUG 1
. Forgetting temporary file /tmp/duplicity-iy2263n9-tempdir/iybclx-_s_fjdrx-ab
INFO 2 10 123
. Processed volume 10 of 123
DEBUG 1
. Releasing lockfile b /home/bnagq/.cache/deja-dup/msycsjdfadsgykpupewxmwlvafdjveye/lockfile
DEBUG 1
. Removing still remembered temporary file /tmp/duplicity-iy2263n9-tempdir/ofavljb-qkpib_cd-w
OK that log isn’t any more enlightening. Two thoughts. One is: I wonder if there’s extra debug information printed to the console. Try running Deja Dup like so: DEJA_DUP_DEBUG=1 G_MESSAGES_DEBUG=all deja-dup and start a backup from that new window. You may see more warnings.
The other thought is harder to debug. I’m worried that this is something Deja Dup is doing internally and doesn’t have good messaging for (like, ideally the error you end up seeing would say “Could not make cache directory: No such file or directory” or something. Something to indicate where in the code we hit this issue. But the message you are seeing is annoyingly vague. IF the above debug run shows a warning message in the console for “No such file or directory” – then we could trick Deja Dup into crashing when it shows this error and get some stack trace info. But if it doesn’t print a message for the issue… Oh boy I dunno.
Was prompted to install some updates, which I did.
Was then prompted to restart which I did.
Ran DEJA_DUP_DEBUG=1 G_MESSAGES_DEBUG=all deja-dup in terminal, then BackUp Now and away it went.
It tells me it’s backed up and I have new files in my backup folder.
I’m worried that this is something Deja Dup is doing internally and doesn’t have good messaging for (like, ideally the error you end up seeing would say “Could not make cache directory: No such file or directory” or something. Something to indicate where in the code we hit this issue. But the message you are seeing is annoyingly vague. IF the above debug run shows a warning message in the console for “No such file or directory” – then we could trick Deja Dup into crashing when it shows this error and get some stack trace info. But if it doesn’t print a message for the issue… Oh boy I dunno.
Because I was still not seeing anything actionable in those logs…
I will say that SMB backups do seem the most error prone. The gvfs layer for samba feels flaky, in a way I’m not sure how to help with.