Crash while doing full backup

Bug #910186 reported by Milan Bouchet-Valat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

I just got this crash while doing a full backup. Happened about 30 minutes after I started it...

This looks very similar to bug 229457, but it was fixed years ago.

I'm using duplicity 0.6.14 on Fedora 15.

$ duplicity full /home/milan file:///media/VERBATIM/Sauvegardes/milan.new
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
GnuPG passphrase:
Retype passphrase to confirm:
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1311, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1304, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1274, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 447, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 325, in write_multivol
    globals.gpg_profile, globals.volsize)
  File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 307, in GPGWriteFile
    top_off(target_size - cursize, file)
  File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 280, in top_off
    assert misc.copyfileobj(incompressible_fp, file.gpg_input, bytes) == bytes
  File "/usr/lib64/python2.7/site-packages/duplicity/misc.py", line 180, in copyfileobj
    outfp.write(buf)
IOError: [Errno 32] Broken pipe

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Oh, maybe I have the explanation now: no free space on /tmp. I tried running the same command again with -v9, and I got this:
Using temporary directory /tmp/duplicity-_USM1S-tempdir
Registering (mkstemp) temporary file /tmp/duplicity-_USM1S-tempdir/mkstemp-QdJYxb-1
Temp space has 25976832 available, backup needs approx 34078720.
Removing still remembered temporary file /tmp/duplicity-_USM1S-tempdir/mkstemp-QdJYxb-1

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Sadly, free space isn't the explanation: I retries after freeing 300MB, and I still get a very similar crash. Here's the end of the output, with -v9:

[Same thing for thousands of lines.]
Selecting /<email address hidden>/folders/INBOX/cur/29/40560
Comparing ('evolution.sav', 'mail', 'imapx', '<email address hidden>', 'folders', 'INBOX', 'cur', '29', '40560') and None
Getting delta of (('evolution.sav', 'mail', 'imapx', '<email address hidden>', 'folders', 'INBOX', 'cur', '29', '40560') /<email address hidden>/folders/INBOX/cur/29/40560 reg) and None
A <email address hidden>/folders/INBOX/cur/29/40560
Removing still remembered temporary file /tmp/duplicity-qiicD3-tempdir/mkstemp-Iov4We-1
Removing still remembered temporary file /tmp/duplicity-qiicD3-tempdir/mktemp-_xPGIA-673
GPG error detail: Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1311, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1304, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1274, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 447, in full_backup
    globals.backend)
  File "/usr/bin/duplicity", line 325, in write_multivol
    globals.gpg_profile, globals.volsize)
  File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 300, in GPGWriteFile
    file.write(data)
  File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 170, in write
    self.gpg_failed()
  File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 182, in gpg_failed
    raise GPGError, msg
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
===== End GnuPG log =====

GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
===== End GnuPG log =====

Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Running a full backup with --no-encrypt succeeded, so that's really a problem with using gpg.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.