duplicity backup fails with obscure error message Ubuntu 22.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
duplicity (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
I try to do a backup onto a network location (ssh://192.168.1.61 - I can successfully connect to this location via ssh). The backup completes the scan phase, then dies with error messages like this:
Failed to read /tmp/duplicity-
While the backup is running, we can see a duplicity* directory under /tmp:
$ ll /tmp/duplicity-
total 16
drwx------ 2 scohen scohen 4096 Apr 24 12:52 ./
drwxrwxrwt 26 root root 12288 Apr 24 12:52 ../
-rw------- 1 scohen scohen 0 Apr 24 12:52 mkstemp-cx21bs8l-1
However, note that this is not the directory mentioned in the failure message.
A scan of the directory after the failure reveals no files like /tmp/dupl*
Why is it trying to read files that do not exist?
$ lsb_release -rd
Description: Ubuntu 22.04 LTS
Release: 22.04
$ apt-cache policy duplicity
duplicity:
Installed: 0.8.21-1build1
Candidate: 0.8.21-1build1
Version table:
*** 0.8.21-1build1 500
500 http://
100 /var/lib/
description: | updated |
Changed in duplicity (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Invalid |
Changed in duplicity: | |
milestone: | none → 0.8.24 |
Changed in duplicity: | |
milestone: | 0.8.24 → 0.8.23 |
Changed in duplicity: | |
status: | Confirmed → Fix Committed |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
I think that /tmp filename is a file that duplicity proceeds to throw away. It copies files there, tries to unpack them, then cleans up after itself (regardless of success). So that error message would be a lot more useful if it indicated what the actual source file it had copied from the storage location was named (like duplicity-vol1.gz or whatever).
The error message makes it sound like the file it is trying to unpack is corrupted. It's possible that a backup file got interrupted/cutoff during writing/transfer?