0.6.18 was a buggy release.  It is possible that it produced a backup that
was incomplete.  This looks like the case in your report above.  I don't
have it in front of me, but there is a method to manually restore files as
long as the difftar files are complete.  Look for answers by edso (Edgar
Soldin) in the duplicity-talk archives.

On Fri, May 27, 2016 at 12:02 AM, Holm <email address hidden> wrote:

> FreeBSD 10.3
>
> root@rose:/usr/ports/net/syncthing # duplicity --version
> duplicity 0.7.06
>
> root@rose:/usr/ports/net/syncthing # python2 --version
> Python 2.7.11
>
> "duplicity collection-status --no-encryption
> file:///mnt/darkstar/backups/rose" - works but list0current-files not.
>
> root@rose:/usr/ports/net/syncthing # duplicity list-current-files
> --no-encryption file:////mnt/darkstar/backups/rose
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: none
> Traceback (most recent call last):
>   File "/usr/local/bin/duplicity", line 1532, in <module>
>     with_tempdir(main)
>   File "/usr/local/bin/duplicity", line 1526, in with_tempdir
>     fn()
>   File "/usr/local/bin/duplicity", line 1380, in main
>     do_backup(action)
>   File "/usr/local/bin/duplicity", line 1461, in do_backup
>     list_current(col_stats)
>   File "/usr/local/bin/duplicity", line 696, in list_current
>     sig_chain = col_stats.get_signature_chain_at_time(time)
>   File "/usr/local/lib/python2.7/site-packages/duplicity/collections.py",
> line 994, in get_signature_chain_at_time
>     raise CollectionsError("No signature chains found")
> CollectionsError: No signature chains found
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1086374
>
> Title:
>   Backup cannot be restored (no signature chains found)
>
> Status in Duplicity:
>   New
> Status in duplicity package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I get:
>
>   [root@ ]# duplicity list-current-files scp://
> 192.168.11.2/backup/caw-server1
>   Local and Remote metadata are synchronized, no sync needed.
>   Last full backup date: none
>   Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 1391, in <module>
>   with_tempdir(main)
>   File "/usr/bin/duplicity", line 1384, in with_tempdir
>   fn()
>   File "/usr/bin/duplicity", line 1322, in main
>   list_current(col_stats)
>   File "/usr/bin/duplicity", line 598, in list_current
>   sig_chain = col_stats.get_signature_chain_at_time(time)
>   File "/usr/lib64/python2.6/site-packages/duplicity/collections.py", line
> 977, in get_signature_chain_at_time
>   raise CollectionsError("No signature chains found")
>   CollectionsError: No signature chains found
>
>   when trying to list files from my backup.  But the files seem ok outside
> of duplicity,
>   This affects multiple servers backing up to different locations.
>
>   OS is CentOS 6.2 x86
>   Duplicity 0.6.18 from the repos
>
>   ---
>   Using archive dir:
> /root/.cache/duplicity/1dc0bb65e1eb97582ca301487786e1b1
>   Using backup name: 1dc0bb65e1eb97582ca301487786e1b1
>   Import of duplicity.backends.ftpsbackend Succeeded
>   Import of duplicity.backends.u1backend Succeeded
>   Import of duplicity.backends.ftpbackend Succeeded
>   Import of duplicity.backends.webdavbackend Succeeded
>   Import of duplicity.backends.hsibackend Succeeded
>   Import of duplicity.backends.imapbackend Succeeded
>   Import of duplicity.backends.botobackend Succeeded
>   Import of duplicity.backends.cloudfilesbackend Succeeded
>   Import of duplicity.backends.rsyncbackend Succeeded
>   Import of duplicity.backends.sshbackend Succeeded
>   Import of duplicity.backends.tahoebackend Succeeded
>   Import of duplicity.backends.localbackend Succeeded
>   Import of duplicity.backends.giobackend Succeeded
>   Import of duplicity.backends.gdocsbackend Succeeded
>   Main action: list-current
>
> ================================================================================
>   duplicity 0.6.18 (February 29, 2012)
>   Args: /usr/bin/duplicity -v9 list-current-files --no-encryption scp://
> 192.168.11.1/backup/caw-server2
>   Linux caw-server2.cawdekempen.be 2.6.32-220.23.1.el6.x86_64 #1 SMP Mon
> Jun 18 18:58:52 BST 2012 x86_64 x86_64
>   /usr/bin/python 2.6.6 (r266:84292, Jun 18 2012, 14:18:47)
>   [GCC 4.4.6 20110731 (Red Hat 4.4.6-3)]
>
> ================================================================================
>   Local and Remote metadata are synchronized, no sync needed.
>   0 files exist on backend
>   0 files exist in cache
>   Extracting backup chains from list of files: []
>   Last full backup date: none
>   Collection Status
>   -----------------
>   Connecting with backend: SftpBackend
>   Archive dir: /root/.cache/duplicity/1dc0bb65e1eb97582ca301487786e1b1
>
>   Found 0 secondary backup chains.
>   No backup chains with active signatures found
>   No orphaned or incomplete backup sets found.
>   Using temporary directory /tmp/duplicity-ckTuyx-tempdir
>   Traceback (most recent call last):
>     File "/usr/bin/duplicity", line 1391, in <module>
>       with_tempdir(main)
>     File "/usr/bin/duplicity", line 1384, in with_tempdir
>       fn()
>     File "/usr/bin/duplicity", line 1322, in main
>       list_current(col_stats)
>     File "/usr/bin/duplicity", line 598, in list_current
>       sig_chain = col_stats.get_signature_chain_at_time(time)
>     File "/usr/lib64/python2.6/site-packages/duplicity/collections.py",
> line 977, in get_signature_chain_at_time
>       raise CollectionsError("No signature chains found")
>   CollectionsError: No signature chains found
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1086374/+subscriptions
>