duplicity fails due to lockfile issues next time if aborted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Invalid
|
Undecided
|
Unassigned |
Bug Description
duplicity 0.7.11
Python 2.7.13
Debian 9.4
How to reproduce:
1. Run a backup:
duplicity -v9 --exclude-
2. Kill it:
killall duplicity
3. Try to run it again (the same command). It fails:
Using archive dir: /data/duplicity
Using backup name: 6c76e9524c6b394
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Main action: inc
Another instance is already running with this archive directory
If you are sure that this is the only instance running you may delete
the following lockfile and run the command again :
/data/
Using temporary directory /data/duplicity
Releasing lockfile /data/duplicity
Line "Releasing lockfile" is misleading, because when I run third time it shows the same messages. The only way to fix the problem is to remove lockfile.lock.
Expected behaviour:
duplicity cleans up and makes a backup on the second run.
It looks like you may have an old version of duplicity first in your PATH. This happens when you have the repo version installed and then install the tarball version (different repos use different install paths). Please uninstall and reinstall using the current version, 0.7.17. This should fix your problem since we replaced module lockfile with fasteners in 0.7.13.