Unable to backup

Bug #388034 reported by Alex Parkins
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
High
Unassigned
Déjà Dup
Invalid
High
Unassigned

Bug Description

Using Deja Dup version 10.1 and Duplicity version 0.6.00 I get the following error when I try to make a backup:

Failed with an unknown error:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1002, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 995, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 974, in main
    full_backup(col_stats)
  File "/usr/bin/duplicity", line 415, in full_backup
    sig_outfp.to_remote()
  File "/usr/lib/python2.6/dist-packages/duplicity/dup_temp.py", line 179, in to_remote
    size = sys.maxint / 2)
  File "/usr/lib/python2.6/dist-packages/duplicity/gpg.py", line 313, in GzipWriteFile
    new_block = block_iter.next(bytes_to_go)
  File "/usr/lib/python2.6/dist-packages/duplicity/dup_temp.py", line 244, in next
    (src.name, sys.exc_info()),
NameError: global name 'src' is not defined

Tags: backup
Revision history for this message
Michael Terry (mterry) wrote :

Ken, this looks like a duplicity bug.

tags: added: backup
Changed in deja-dup:
importance: Undecided → High
Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

Actually, this is probably a 2-part problem. One is that src.name should be src_name, and the other is probably the read block size issue that Peter Schuller and I have been chasing.

Changed in duplicity:
assignee: nobody → Kenneth Loafman (kenneth-loafman)
importance: Undecided → High
Revision history for this message
Peter Schuller (scode) wrote :

At the very least running with the src name fix will show the first error (the strack trace above happens when another error happens, because the error handling code itself has the bug, thus hiding the original problem).

Revision history for this message
Simon Lukell (slukell) wrote :

I believe it should be self.src.name instead of src.name

Revision history for this message
Alex Parkins (alexparkins) wrote :

Well if I rename src.name to self.src.name on line 244 of dup_temp.py then I get the error:

Failed to read /home/aparkins/.cache/deja-dup/duplicity-full-signatures.20090620T075222Z.sigtar.part: (<type 'exceptions.MemoryError'>, MemoryError(), <traceback object at 0xa2dc57c>)

Revision history for this message
Peter Schuller (scode) wrote : Re: [Bug 388034] Re: Unable to backup

> Well if I rename src.name to self.src.name on line 244 of dup_temp.py
> then I get the error:
>
> Failed to read /home/aparkins/.cache/deja-dup/duplicity-full-
> signatures.20090620T075222Z.sigtar.part: (<type
> 'exceptions.MemoryError'>, MemoryError(), <traceback object at
> 0xa2dc57c>)

Yes, this is the real error. The src.name thing was an error in the
error handling path. Fixes to both issues are in the branch:

   https://code.launchpad.net/~scode/duplicity/reasonable-io-blocksize

And is pending approval/merge.

--
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <email address hidden>'
Key retrieval: Send an E-Mail to <email address hidden>
E-Mail: <email address hidden> Web: http://www.scode.org

Changed in duplicity:
assignee: Kenneth Loafman (kenneth-loafman) → nobody
status: New → Fix Committed
Michael Terry (mterry)
Changed in deja-dup:
status: New → Invalid
Changed in duplicity:
milestone: none → 0.6.1
Changed in duplicity:
status: Fix Committed → Fix Released
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.