Crash with stacktrace, error code 30 in validate_encryption_settings

Bug #1245805 reported by Damien Cassou on 2013-10-29
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
Undecided
Unassigned
duplicity (Ubuntu)
Undecided
Unassigned

Bug Description

While running duplicity through duply, I get:

[...]
Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Fri Oct 25 17:41:51 2013
Chain end time: Fri Oct 25 17:41:51 2013
Number of contained backup sets: 1
Total number of contained volumes: 13
 Type of backup set: Time: Num volumes:
                Full Fri Oct 25 17:41:51 2013 13
-------------------------
No orphaned or incomplete backup sets found.
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
RESTART: Volumes 13 to 473 failed to upload before termination.
         Restarting backup at volume 13.
Removing still remembered temporary file /tmp/duplicity-H1PRj7-tempdir/mkstemp-Bvibdh-1
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1374, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 509, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 346, in write_multivol
    validate_encryption_settings(globals.restart.last_backup, mf)
  File "/usr/bin/duplicity", line 325, in validate_encryption_settings
    if vol1_filename != backup_set.volume_name_dict[1]:
KeyError: 1

09:03:40.631 Task 'BKP' failed with exit code '30'.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: duplicity 0.6.21-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Tue Oct 29 09:04:56 2013
InstallationDate: Installed on 2013-10-21 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

Damien Cassou (cassou) wrote :
edso (ed.so) wrote :

enforce a full backup. see man page of duply/duplicity on how to do so...

after that worked fine you should verify, just to be sure.

after that.. run 'duply cleanup' to remove the incomplete backup resulting the error above..

..ede/duply.net

On Wed, Oct 30, 2013 at 11:31 AM, edso <email address hidden> wrote:
> enforce a full backup. see man page of duply/duplicity on how to do
> so...

Does not work:

$ duply backup_fat full
[...]
--- Start running command FULL at 11:51:12.652 ---
Reading globbing filelist /home/XXX/.duply/backup_fat/include_exclude.txt
Reading globbing filelist /home/XXX/.duply/backup_fat/exclude
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Fri Oct 25 17:41:51 2013
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
RESTART: Volumes 13 to 473 failed to upload before termination.
         Restarting backup at volume 13.
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1374, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 509, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 346, in write_multivol
    validate_encryption_settings(globals.restart.last_backup, mf)
  File "/usr/bin/duplicity", line 325, in validate_encryption_settings
    if vol1_filename != backup_set.volume_name_dict[1]:
KeyError: 1

11:51:16.168 Task 'FULL' failed with exit code '30'.
--- Finished state FAILED 'code 30' at 11:51:16.168 - Runtime 00:00:03.516 ---
$

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Success is the ability to go from one failure to another without
losing enthusiasm."
Winston Churchill

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in duplicity (Ubuntu):
status: New → Confirmed
macho (macho) wrote :

I'm still getting this crash on Ubuntu 15.10 with duplicity 0.7.02.

My initial full backup seemed to be stalled (destination stopped growing), so I did ^C and restarted:

# duplicity --full-if-older-than 2W --no-encryption --exclude-other-filesystems $home_source $home_target
Local and Remote metadata are synchronized, no sync needed.
Last full backup left a partial set, restarting.
Last full backup date: Sat Jan 2 02:14:14 2016
RESTART: Volumes 82 to 525 failed to upload before termination.
         Restarting backup at volume 82.
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1519, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1513, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1370, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1483, in do_backup
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 560, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 375, in write_multivol
    validate_encryption_settings(globals.restart.last_backup, mf)
  File "/usr/bin/duplicity", line 354, in validate_encryption_settings
    if vol1_filename != backup_set.volume_name_dict[1]:
KeyError: 1

I'll try a fresh full backup, but I fear it will stall and/or crash again.

Download full text (4.0 KiB)

This error is due to missing volumes. Try doing a 'duplicity cleanup
--force <target>', then run the backup again.

On Sun, Jan 3, 2016 at 3:06 AM, macho <email address hidden> wrote:

> I'm still getting this crash on Ubuntu 15.10 with duplicity 0.7.02.
>
> My initial full backup seemed to be stalled (destination stopped
> growing), so I did ^C and restarted:
>
> # duplicity --full-if-older-than 2W --no-encryption
> --exclude-other-filesystems $home_source $home_target
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup left a partial set, restarting.
> Last full backup date: Sat Jan 2 02:14:14 2016
> RESTART: Volumes 82 to 525 failed to upload before termination.
> Restarting backup at volume 82.
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1519, in <module>
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1513, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1370, in main
> do_backup(action)
> File "/usr/bin/duplicity", line 1483, in do_backup
> full_backup(col_stats)
> File "/usr/bin/duplicity", line 560, in full_backup
> globals.backend)
> File "/usr/bin/duplicity", line 375, in write_multivol
> validate_encryption_settings(globals.restart.last_backup, mf)
> File "/usr/bin/duplicity", line 354, in validate_encryption_settings
> if vol1_filename != backup_set.volume_name_dict[1]:
> KeyError: 1
>
> I'll try a fresh full backup, but I fear it will stall and/or crash
> again.
>
> --
> You received this bug notification because you are subscribed to
> duplicity in Ubuntu.
> https://bugs.launchpad.net/bugs/1245805
>
> Title:
> Crash with stacktrace, error code 30 in validate_encryption_settings
>
> Status in Duplicity:
> New
> Status in duplicity package in Ubuntu:
> Confirmed
>
> Bug description:
> While running duplicity through duply, I get:
>
> [...]
> Found primary backup chain with matching signature chain:
> -------------------------
> Chain start time: Fri Oct 25 17:41:51 2013
> Chain end time: Fri Oct 25 17:41:51 2013
> Number of contained backup sets: 1
> Total number of contained volumes: 13
> Type of backup set: Time: Num volumes:
> Full Fri Oct 25 17:41:51 2013 13
> -------------------------
> No orphaned or incomplete backup sets found.
> Reuse configured PASSPHRASE as SIGN_PASSPHRASE
> RESTART: Volumes 13 to 473 failed to upload before termination.
> Restarting backup at volume 13.
> Removing still remembered temporary file
> /tmp/duplicity-H1PRj7-tempdir/mkstemp-Bvibdh-1
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1411, in <module>
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1404, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1374, in main
> full_backup(col_stats)
> File "/usr/bin/duplicity", line 509, in full_backup
> globals.backend)
> File "/usr/bin/duplicity", line 346, in write_multivol
> validate_encryption_settings(globals.restart.last_backup, mf)
> File "/usr/bin/duplicity...

Read more...

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

Other bug subscribers