← Back to team overview

duplicity-team team mailing list archive

[Question #145784]: duplicity keeps crashing with 'ValueError: need more than 0 values to unpack'

 

New question #145784 on Duplicity:
https://answers.launchpad.net/duplicity/+question/145784

I'm using duplicity 0.6.11 and I have yet to successfully backup a folder with it after trying multiple ways, such as local, remote, with/without encryption, different directories. For example, trying to backup to the extracted duplicity source files to the local filesystem I get the following error:

[root@30AK10 duplicity-0.6.11]# duplicity full -v9 --archive-dir /tmp/archive  /tmp/duplicity-0.6.11 file:///tmp/backup
Using archive dir: /tmp/archive/ba8d32ccb88d13597b4784252744fc75
Using backup name: ba8d32ccb88d13597b4784252744fc75
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.giobackend Failed: No module named gio
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Main action: full
PASSPHRASE variable not set, asking user.
GnuPG passphrase:
================================================================================
duplicity 0.6.11 (November 20, 2010)
Args: /usr/bin/duplicity full -v9 --archive-dir /tmp/archive /tmp/duplicity-0.6.11 file:///tmp/backup
/usr/bin/python 2.4.3 (#1, Nov 11 2010, 13:30:19)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-48)]
================================================================================
Using temporary directory /tmp/duplicity--uD9Qb-tempdir
Registering (mkstemp) temporary file /tmp/duplicity--uD9Qb-tempdir/mkstemp-sWTswu-1
Temp has 426427809792 available, backup will use approx 34078720.
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: LocalBackend
Archive dir: /tmp/archive/ba8d32ccb88d13597b4784252744fc75

Found 0 secondary backup chains.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
PASSPHRASE variable not set, asking user.

<snip>

Generating delta - new file: src/util.py
Selecting /tmp/duplicity-0.6.11/tarfile-LICENSE
Comparing ('tarfile-LICENSE',) and None
Getting delta of (('tarfile-LICENSE',) /tmp/duplicity-0.6.11/tarfile-LICENSE reg) and None
Generating delta - new file: tarfile-LICENSE
Removing still remembered temporary file /tmp/duplicity-MtTlAs-tempdir/mkstemp-WngM6S-1
Removing still remembered temporary file /tmp/duplicity-MtTlAs-tempdir/mktemp-rnSJTU-2
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1245, in ?
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1238, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1211, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 417, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 302, in write_multivol
    vi.set_info(vol_num, *get_indicies(tarblock_iter))
  File "/usr/bin/duplicity", line 226, in get_indicies
    start_index, start_block = tarblock_iter.recall_index()
ValueError: need more than 0 values to unpack

Removing still remembered temporary file /tmp/archive/ba8d32ccb88d13597b4784252744fc75/duplicity-Tp8h4h-tempdir/mktemp-vWXtH2-1
Removing still remembered temporary file /tmp/archive/ba8d32ccb88d13597b4784252744fc75/duplicity-Te6JI7-tempdir/mktemp-gn0VqS-1

It looks like it is working at first but then it blows up after processing random files.  Maybe this has something to do with how I installed duplicity. At first I did 'yum install duplicity', then I downloaded the tar from the website and did 'python setup.py install'.  So maybe it could be using some old version of files somewhere.

Thanks for any help.


-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.