duplicity fails due to lockfile issues next time if aborted

Bug #1777728 reported by hon on 2018-06-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
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-device-files --exclude-other-filesystems --no-encryption --no-compression --progress --volsize 1024 --archive-dir=/data/duplicity-cache --tempdir=/data/duplicity-tmpdir /data/stor-work file:///data/stor-duplicity/

2. Kill it:
killall duplicity

3. Try to run it again (the same command). It fails:
Using archive dir: /data/duplicity-cache/6c76e9524c6b39490e59c73ca80b1161
Using backup name: 6c76e9524c6b39490e59c73ca80b1161
Import of duplicity.backends.acdclibackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.copycombackend Succeeded
Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
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/duplicity-cache/6c76e9524c6b39490e59c73ca80b1161/lockfile.lock
Using temporary directory /data/duplicity-tmpdir/duplicity-QNiYIY-tempdir
Releasing lockfile /data/duplicity-cache/6c76e9524c6b39490e59c73ca80b1161/lockfile.lock

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.

Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.7.18
status: New → In Progress
hon (hon2048) wrote :

I had duplicity 0.7.11 from Debian repos. I uninstalled it and installed 0.7.17 from Launchpad. It works fine. Should I report Debian maintainers to upgrade the version in their repo?

It would not hurt. They do have their own processes, so it could take a bit.

Changed in duplicity:
importance: Medium → Undecided
milestone: 0.7.18 → none
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers