BackendException: sftp put of [] failed: [Errno 2]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned |
Bug Description
Hello, I have a strange bug with v0.6.18
I get the following error:
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted session
Last full backup left a partial set, restarting.
Last full backup date: Tue Mar 6 11:42:05 2012
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
RESTART: The first volume failed to upload before termination.
Restart is impossible.
Reading filelist /root/bin/
Sorting filelist /root/bin/
Local and Remote metadata are synchronized, no sync needed.
Warning, found incomplete backup sets, probably left from aborted session
Last full backup date: none
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
No signatures found, switching to full backup.
BackendException: sftp put of /var/tmp/
yes indeed the file it is trying to access does not exist,
it doesn't appear to affect all my systems i've tested duplicity 0.6.18 on, however the systems are lucid with the latest updates installed.
* lots of comparing files *
Comparing () and None
Getting delta of (() /opt/zimbra/
A file.abc
Removing still remembered temporary file /root/.
Cleanup of temporary file /root/.
Removing still remembered temporary file /root/.
Cleanup of temporary file /root/.
AsyncScheduler: running task synchronously (asynchronicity disabled)
Removing still remembered temporary file /tmp/duplicity-
Removing still remembered temporary file /tmp/duplicity-
Backend error detail: Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
full_
File "/usr/bin/
globals.
File "/usr/bin/
(tdp, dest_filename, vol_num)))
File "/usr/lib/
return self.__
File "/usr/lib/
ret = fn(*params)
File "/usr/bin/
async_
File "/usr/bin/
backend.
File "/usr/lib/
raise BackendExceptio
BackendException: sftp put of /tmp/duplicity-
BackendException: sftp put of /tmp/duplicity-
yes i agree you are going to have an error there because that file/dir doesn't exist
the first few lines are:
Using archive dir: /root/.
Using backup name: 763e12cfbcae8ce
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Reading filelist /root/bin/
Sorting filelist /root/bin/
Main action: inc
=======
duplicity 0.6.18 ($reldate)
Args: /usr/bin/duplicity -v 9 --encrypt-key A1C86AEB --sign-key A1C86AEB --exclude-filelist /root/bin/
Linux zimbra 2.6.32-37-server #81-Ubuntu SMP Fri Dec 2 20:49:12 UTC 2011 x86_64
/usr/bin/python2.6 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3]
=======
=======
Using temporary directory /tmp/duplicity-
Registering (mkstemp) temporary file /tmp/duplicity-
Temp has 84592353280 available, backup will use approx 34078720.
Local and Remote metadata are synchronized, no sync needed.
0 files exist on backend
0 files exist in cache
Extracting backup chains from list of files: []
Last full backup date: none
Collection Status
-----------------
Connecting with backend: SftpBackend
Archive dir: /root/.
Found 0 secondary backup chains.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
Reuse configured PASSPHRASE as SIGN_PASSPHRASE
No signatures found, switching to full backup.
Using temporary directory /root/.
Registering (mktemp) temporary file /root/.
Using temporary directory /root/.
Registering (mktemp) temporary file /root/.
AsyncScheduler: instantiating at concurrency 0
Registering (mktemp) temporary file /tmp/duplicity-
Selecting /
Comparing () and None
Getting delta of (() / dir) and None
A .
Selecting /cdrom
Comparing ('cdrom',) and None
Getting delta of (('cdrom',) /cdrom dir) and None
A cdrom
Selecting /etc
Comparing ('etc',) and None
....
I get this error too. It looks to me as a bug in paramiko. Apparently it does successfully 'put' the file to the server but thinks that the operation fails.
Francis, can you check which versions of python-paramiko are installed on your hosts that work and that fail with this error?