I think I resolved it.
The issue was related to NOT USING relative paths.
address@hidden:~/test$ duplicity list-current-files sftp://vps9.example.net:2999/Backup/Documents/abdoks
-------- Original Message --------
Subject: [Duplicity-tracker] duplicity list-current-files failing with "CollectionsError: No signature chains found"
Local Time: December 20, 2017 3:59 PM
UTC Time: December 20, 2017 8:59 PM
From: address@hidden
To: address@hidden <address@hidden>
Hello all -
A new duplicity user here.
I am testing a simple backup, list files and restore.
While running duplicity list-current-files, I got the following error:
address@hidden:~/test$ duplicity list-current-files sftp://vps9.example.net:2999/home/vin/Backup/Documents/abdoks
/usr/lib/python2.7/dist-packages/Crypto/Cipher/blockalgo.py:141: FutureWarning: CTR mode needs counter parameter, not IV
self._cipher = factory.new(key, *args, **kwargs)
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1394, in main
do_backup(action)
File "/usr/bin/duplicity", line 1477, in do_backup
list_current(col_stats)
File "/usr/bin/duplicity", line 703, in list_current
sig_chain = col_stats.get_signature_chain_at_time(time)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 1008, in get_signature_chain_at_time
raise CollectionsError("No signature chains found")
CollectionsError: No signature chains found
However, when I copy the remote directory to a local directory and run the list-current-files it works:
address@hidden:~/test/abdoks$ cd ..
address@hidden:~/test$ rmdir abdoks/
address@hidden:~/test$ scp -r -P 2999
address@hidden:/home/vin/Backup/abdoks .Warning: Permanently added '[vps9.example.net]:2999,[967.488.998.337]:2999' (ECDSA) to the list of known hosts.
duplicity-full.20171215T031851Z.vol2.difftar.gpg 100% 200MB 20.0MB/s 00:10
duplicity-full.20171215T031851Z.vol1.difftar.gpg 100% 200MB 16.7MB/s 00:12
duplicity-full.20171215T031851Z.manifest.gpg 100% 139KB 139.1KB/s 00:00
duplicity-full.20171215T031851Z.vol4.difftar.gpg 100% 170MB 18.9MB/s 00:09
duplicity-full-signatures.20171215T031851Z.sigtar.gpg 100% 17MB 17.3MB/s 00:01
duplicity-full.20171215T031851Z.vol3.difftar.gpg 100% 200MB 22.2MB/s 00:09
duplicity list-current-files --encrypt-key=D7XXXXXX --sign-key=D7XXXXXX file:///home/vin/test/abdoks | tee log.txt
<<Removed gnupg pp request and response>>
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Thu Dec 14 22:18:51 2017
Sat Apr 5 11:40:32 2014 .
Sat Apr 5 11:38:28 2014 _PROJECTS
...
....
....
List of backup contents follows.
....
address@hidden:~/test$ uname -a
Linux i7 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
address@hidden:~/test$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
address@hidden:~/test$ duplicity --version
duplicity 0.7.15
address@hidden:~/test$ date
Wed Dec 20 15:57:39 EST 2017
address@hidden:~/test$
Any hints on how to resolve this?
For obvious reasons, names and ips randomized.
Thank you. Apologize if this was already addressed in any previous threads - I searched, couldn't find it.