Bug 1753742 - Duplicity fails with "OverflowError: size does not fit in an int"
Summary: Duplicity fails with "OverflowError: size does not fit in an int"
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: duplicity
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-19 17:32 UTC by Robert Scheck
Modified: 2019-11-14 14:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2019-09-19 17:32:42 UTC
Description of problem:
Running "duplicity --full-if-older-than 32D --encrypt-key <key> /backup/ sftp://backup.net//backup-offsite/ --use-agent" ends up with this failure which feels like a bug:

--- snipp ---
Local and Remote metadata are synchronized, no sync needed.
Last inc backup left a partial set, restarting.
Last full backup date: Mon Aug 19 01:00:02 2019
RESTART: Volumes 68 to 68 failed to upload before termination.
         Restarting backup at volume 68.
Restarting after volume 67, file server/gitlab/gitlab-Incremental-0251, block 8176
/usr/lib64/python2.7/site-packages/duplicity/util.py:79: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  m = e.message
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1581, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1567, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1419, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1549, in do_backup
    incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 673, in incremental_backup
    globals.backend)
  File "/usr/bin/duplicity", line 435, in write_multivol
    globals.volsize)
  File "/usr/lib64/python2.7/site-packages/duplicity/gpg.py", line 386, in GPGWriteFile
    data = block_iter.next().data
  File "/usr/lib64/python2.7/site-packages/duplicity/diffdir.py", line 523, in next
    result = self.process(self.input_iter.next())
  File "/usr/lib64/python2.7/site-packages/duplicity/diffdir.py", line 218, in get_delta_iter
    (new_path, sig_path, sigTarFile))
  File "/usr/lib64/python2.7/site-packages/duplicity/robust.py", line 38, in check_common_error
    return function(*args)
  File "/usr/lib64/python2.7/site-packages/duplicity/diffdir.py", line 139, in get_delta_path
    delta_path.setfileobj(librsync.DeltaFile(old_sigfp, newfp))
  File "/usr/lib64/python2.7/site-packages/duplicity/librsync.py", line 159, in __init__
    self.maker = _librsync.new_deltamaker(sig_string)
 OverflowError: size does not fit in an int
--- snapp ---

Version-Release number of selected component (if applicable):
duplicity-0.7.19-1.el7.x86_64

How reproducible:
Currently all the time, but not sure how it is triggered.

Actual results:
Duplicity fails with "OverflowError: size does not fit in an int"

Expected results:
No Python traceback failure. If at all, a properly catched failure, which is user/admin friendly.

Comment 1 Gwyn Ciesla 2019-09-19 19:49:43 UTC
Does this occur if you backup to another remote location, or back up another folder to that location?

Comment 2 Robert Scheck 2019-11-14 10:04:36 UTC
The issue happens independent of the location, even when wiping the remote location and restarting from an empty remote location.

Comment 3 Gwyn Ciesla 2019-11-14 14:47:29 UTC
Out of curiosity, what changes if you omit --use-agent?


Note You need to log in before you can comment on or make changes to this bug.