Permanent "Another duplicity instance is already running"

[Eoghan Murray]

For many weeks now my duplicity instance (started via deja-dup) has been failing with
"Another duplicity instance is already running with this archive directory"

My storage location is on a network which is automatically mounted

I checked the folder for the presence of a lockfile (after reading the code) and there was none there.

It was only after adding extra info as follows:

` log.FatalError(
            "Another duplicity instance is already running with this archive directory: %s \n" % (globals.lockpath),
`

That I discovered that globals.lockpath is set to `~/.cache/deja-dup/3ac8a04e2f4c8feb215d2e9f8eb12645/`

Should there be something in duplicity to test the age of the lockpath, or actually test it for an actively running process, e.g. store the PID and check (using ps) whether that process is running?

Apologies if this is a concern of deja-dup.

[Kenneth Loafman (kenneth-loafman)]

Which versions? OS? Duplicity?

[bananenkasper (bananenkasper)]

ubuntu 20.04.

[Kenneth Loafman (kenneth-loafman)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

 status new
 importance undecided
 done
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEExwf+p6/3mDvUSsaGH1G0ZBEHM/EFAmBl5TEACgkQH1G0ZBEH
M/H8LQgAq8GUahEM68BdGxCtjc6dDM9s8N948Vr7VuZtLteIIn2Xx1O2yrmVzP50
ReVk6MTjLFjrM9HcJdelaE+uBnOZB+ms0jUoGQzMyCoMAS+nWLfT8I6wDk9NqSuS
VZLUfEhuzBe2xSYmx7WBCvRKtDv7SXp6l+V5R3OFA9f03OAFF4HzyLGBDvCoxGX4
/NZciOgaZUg1uLE1Qq1F1lNquXD0TE9BN3LK6foBJZMCrev1tJCQ11am+j154C3+
y1Hbngo/pVS9KrC6Sg4/5nwiIThRl6r4SMUiibVFSiUDyfQLQQaXjtqCAKth7R7o
nYmOAIL4gltw2Mw45QDlkeYvvIoiCA==
=2z9n
-----END PGP SIGNATURE-----