Your message dated Mon, 09 Jul 2012 16:17:26 +0000
with message-id <e1sogem-0004jl...@franck.debian.org>
and subject line Bug#659007: fixed in paramiko 1.7.7.1-3
has caused the Debian Bug report #659007,
regarding Transfers fail after 1GB; rekeying window too small
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
659007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659007
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.17-3
Severity: important
I have had a very simple backup script using duplicity runnig for a long time.
Recently (I have noticed it since mid-January, perhaps related to the
introduction of python-paramiko) it frequently (not always) fails with (using
switches "--asynchronous-upload -v5"):
"""
AsyncScheduler: task execution done (success: False)
....[some files aded to next volume]...
AsyncScheduler: scheduling task for asynchronous execution
AsyncScheduler: a previously scheduled task has failed; propagating the result
immediately
Backend error detail: Traceback (most recent call last):
File "/usr/bin/duplicity", line 1388, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1381, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1351, in main
full_backup(col_stats)
File "/usr/bin/duplicity", line 500, in full_backup
globals.backend)
File "/usr/bin/duplicity", line 399, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
151, in schedule_task
return self.__run_asynchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
215, in __run_asynchronously
with_lock(self.__cv, wait_for_and_register_launch)
File "/usr/lib/python2.7/dist-packages/duplicity/dup_threading.py", line 100,
in with_lock
return fn()
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
196, in wait_for_and_register_launch
check_pending_failure() # raise on fail
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
191, in check_pending_failure
self.__failed_waiter()
File "/usr/lib/python2.7/dist-packages/duplicity/dup_threading.py", line 201,
in caller
value = fn()
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
183, in <lambda>
(waiter, caller) = async_split(lambda: fn(*params))
File "/usr/bin/duplicity", line 398, in <lambda>
async_waiters.append(io_scheduler.schedule_task(lambda tdp, dest_filename,
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 296, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/sshbackend.py",
line 189, in put
raise BackendException("sftp put of %s (as %s) failed: %s" %
(source_path.name,remote_filename,e))
BackendException: sftp put of /media/5-2000/tmp/duplicity-tmp/duplicity-CyAVNR-
tempdir/mktemp-d28oCp-409 (as duplicity-
full.20120207T111003Z.vol408.difftar.gpg) failed: Server connection dropped:
"""
and to STDERR it is written
"""
No handlers could be found for logger "paramiko.transport"
BackendException: sftp put of /media/5-2000/tmp/duplicity-tmp/duplicity-CyAVNR-
tempdir/mktemp-d28oCp-409 (as duplicity-
full.20120207T111003Z.vol408.difftar.gpg) failed: Server connection dropped:
"""
It sounds like a local connection error, but it has never happened before and
the error mentions paramiko explicitly. I have recently started using
"--asynchronous-upload", but I believe it happened before that as well (it is
hard to track down since it seems to happen randomly).
It happens more often during full backups, when 20GB+ is transferred (default
volume size 25MB), than during incremental backups when only a few volumes
typically is transferred.
Perhaps it is a local connection error that always have existed, but the
previous SFTP backend retried as default action instead of failing.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii libc6 2.13-26
ii librsync1 0.9.7-8
ii python 2.7.2-10
ii python-gnupginterface 0.3.2-9.1
ii python2.7 2.7.2-13
Versions of packages duplicity recommends:
ii python-paramiko 1.7.7.1-2
ii rsync 3.0.9-1
Versions of packages duplicity suggests:
pn lftp 4.3.4-1
pn ncftp 2:3.2.5-1
pn python-boto <none>
pn python-cloudfiles <none>
pn python-gdata <none>
pn python-pexpect 2.3-1
pn tahoe-lafs <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: paramiko
Source-Version: 1.7.7.1-3
We believe that the bug you reported is fixed in the latest version of
paramiko, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 659...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jeremy T. Bouse <jbo...@debian.org> (supplier of updated paramiko package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 09 Jul 2012 11:02:38 -0400
Source: paramiko
Binary: python-paramiko
Architecture: source all
Version: 1.7.7.1-3
Distribution: unstable
Urgency: low
Maintainer: Jeremy T. Bouse <jbo...@debian.org>
Changed-By: Jeremy T. Bouse <jbo...@debian.org>
Description:
python-paramiko - Make ssh v2 connections with Python
Closes: 659007 668239
Changes:
paramiko (1.7.7.1-3) unstable; urgency=low
.
* Accept NMU uploads (Closes: #659007, #668239)
* Update package to clean up lintian findings
* debian/source/local-options: set unapply-patches option
* debian/watch: Don't need to use uupdate with gbp
* debian/control: Upgrade Debian Standard (no changes needed)
Checksums-Sha1:
74419a44318df83a1ea80f2181db1f0073aaf939 1345 paramiko_1.7.7.1-3.dsc
c2872d231ed52d1bb48dc7351d8099376143b020 5357 paramiko_1.7.7.1-3.debian.tar.gz
3ef20f1e8c453c26e6dc33c310d720d57d92d60c 806772
python-paramiko_1.7.7.1-3_all.deb
Checksums-Sha256:
8bf5b2dc47f8069a75cf64f741c99576378d6a538376c82de2142769c6fd0db3 1345
paramiko_1.7.7.1-3.dsc
b0b3d8d8c933a235597fb0a4a43f30e36ba468d590d098a5a5632014f60ae457 5357
paramiko_1.7.7.1-3.debian.tar.gz
749a3e3db2aacb9ebbb44fde63327eeeae6da0cfc83930f090c5ddd05beb5f35 806772
python-paramiko_1.7.7.1-3_all.deb
Files:
3dae5b390b64b5e1ce5f071092359fb2 1345 python optional paramiko_1.7.7.1-3.dsc
94c9e27d03bc91502202cd7ee9596162 5357 python optional
paramiko_1.7.7.1-3.debian.tar.gz
b10eae4c9cccc0267541bdb24250aa9f 806772 python optional
python-paramiko_1.7.7.1-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iF4EAREIAAYFAk/7AUgACgkQ8C9U2GaKntdj/gD6A2LkQbDmuewcq8bBpsIbQsOw
gP+FPJWkoRt0zMmvgiQA/0uR7Rqcus16HFy5Aj7h/KwOFlrlR9oSKRoHR/5MRUbZ
=X20d
-----END PGP SIGNATURE-----
--- End Message ---
