Package: duplicity
Version: 0.7.10-1~bpo8+1
Severity: important

Dear Maintainer,

   * What led up to the situation?
Using duplicity with a S3 remote for a while, until multiple backup chains 
exist.

   * What exactly did you do (or not do) that was effective (or ineffective)?
/usr/bin/duplicity full --s3-use-ia --asynchronous-upload --encrypt-key <KEYID> 
--encrypt-key <KEYID2> --include-filelist /etc/backup-targets / <AWSBUCKET>

(same effect when substituting full for incremental or collection-status)

   * What was the outcome of this action?
Sudden spikes in CPU and memory consumption resulting in a machine that does 
not react to console or ssh logins until reboot. Screen displays kernel 
warnings for hung tasks / timeouts (unfortunately not recoverable from logging).

   * What outcome did you expect instead?
Normal completion of full and incremental backups

when run using a soft ulimit on memory use, I get the following error trace:

---->8 snip >8----
Reading globbing filelist /etc/backup-targets
Local and Remote metadata are synchronized, no sync needed.


Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1553, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1547, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1398, in main
    do_backup(action)
  File "/usr/bin/duplicity", line 1423, in do_backup
    globals.archive_dir).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
    self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
    add_to_sets(f)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 830, 
in add_to_sets
    if new_set.add_filename(filename):
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
    self.set_manifest(filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
    self.set_files_changed()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
    mf = self.get_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
    return self.get_local_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
    return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
    vi = VolumeInfo().from_string(match.group(1))
MemoryError
---->8 snip >8----

-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages duplicity depends on:
ii  libc6            2.19-18+deb8u7
ii  librsync1        0.9.7-10
ii  python           2.7.9-1
ii  python-lockfile  1:0.8-2

Versions of packages duplicity recommends:
ii  python-oauthlib  0.6.3-1
ii  python-paramiko  1.15.1-1
ii  python-urllib3   1.9.1-3
ii  rsync            3.1.1-3

Versions of packages duplicity suggests:
pn  lftp                <none>
pn  ncftp               <none>
ii  python-boto         2.34.0-2
pn  python-cloudfiles   <none>
pn  python-gdata        <none>
pn  python-swiftclient  <none>
ii  tahoe-lafs          1.10.0-2

-- no debconf information

Reply via email to