Another duplicity instance is already running with this archive directory

Bug #1859147 reported by Marcel Molendijk on 2020-01-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Undecided
Unassigned

Bug Description

Suddenly this behaviour occurs. Tried removing the lockfile in .cache/deja-dup but this only removes the password. Tried uninstall re-install but did not change. After removing lockfile I once get a dialoque to input the password and directly after that get the ¨Another duplicity instance is already running with this archive directory" message again...

Debian GNU/Linux 10 (buster)
deja-dup 38.3-1
duplicity 0.7.18.2-1

content deja-dup.gsettings;

org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'remote'
org.gnome.DejaDup last-run '2020-01-06T18:45:37.610602Z'
org.gnome.DejaDup nag-check '2020-01-06T18:45:37.628836Z'
org.gnome.DejaDup prompt-check '2020-01-04T10:09:08.790830Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['/home/marcel/.local/share/Trash', '/home/marcel/Downloads', '/home/marcel/programdata/spotify', "/home/marcel/Video's"]
org.gnome.DejaDup last-backup '2020-01-06T18:45:37.610602Z'
org.gnome.DejaDup allow-metered false
org.gnome.DejaDup delete-after 0
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container 'infestation'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'infestation'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container 'infestation'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'infestation'
org.gnome.DejaDup.Local folder 'infestation'
org.gnome.DejaDup.Remote uri 'sftp://<email address hidden>/data/backup/infestation/'
org.gnome.DejaDup.Remote folder 'deja-dup'
org.gnome.DejaDup.Drive uuid ''
org.gnome.DejaDup.Drive icon ''
org.gnome.DejaDup.Drive folder 'infestation'
org.gnome.DejaDup.Drive name ''
org.gnome.DejaDup.GOA id ''
org.gnome.DejaDup.GOA folder 'infestation'
org.gnome.DejaDup.GOA type 'google'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File migrated true
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File path ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []

content deja-dup.log;

DUPLICITY: INFO 1
DUPLICITY: . Using archive dir: /home/marcel/.cache/deja-dup/778dbc8b87ce3820d6ba1aae5a20c8e1

DUPLICITY: INFO 1
DUPLICITY: . Using backup name: 778dbc8b87ce3820d6ba1aae5a20c8e1

DUPLICITY: DEBUG 1
DUPLICITY: . GPG binary is gpg, version 2.2.12

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.acdclibackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.azurebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.b2backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.botobackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.cfbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.dpbxbackend Failed: No module named dropbox

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.gdocsbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.giobackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.hsibackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.hubicbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.imapbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.lftpbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.localbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.mediafirebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.megabackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.multibackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.ncftpbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.onedrivebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.par2backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.pydrivebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.rsyncbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.ssh_paramiko_backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.ssh_pexpect_backend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.swiftbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.sxbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.tahoebackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Import of duplicity.backends.webdavbackend Succeeded

DUPLICITY: INFO 1
DUPLICITY: . Main action: collection-status

DUPLICITY: DEBUG 1
DUPLICITY: . Acquiring lockfile /home/marcel/.cache/deja-dup/778dbc8b87ce3820d6ba1aae5a20c8e1/lockfile

DUPLICITY: ERROR 23
DUPLICITY: . Another duplicity instance is already running with this archive directory
DUPLICITY: .

DUPLICITY: INFO 1
DUPLICITY: . Using temporary directory /var/tmp/duplicity-HdHTSU-tempdir

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile /home/marcel/.cache/deja-dup/778dbc8b87ce3820d6ba1aae5a20c8e1/lockfile

DUPLICITY: DEBUG 1
DUPLICITY: . Releasing lockfile /home/marcel/.cache/deja-dup/778dbc8b87ce3820d6ba1aae5a20c8e1/lockfile

Marcel Molendijk (mmolendijk) wrote :
Marcel Molendijk (mmolendijk) wrote :

sorry, forgot to mention I also tried this: purge deja-dup and removed the deja-dup folder on the server. after re-installing deja-dup tried again to make a backup but same error. the operation did re-create the deja-dup folder on the server and there are files in this folder, too.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers