Misleading error message: "Invalid SSH password"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
duplicity wrongly states "Invalid SSH password" when trying to write the backup via scp/sftp to a directory that doesn't exist and cannot be created. My example:
# duplicity --include-
Reading globbing filelist /etc/duplicity/
Invalid SSH password
Running 'sftp -oServerAliveIn
It works as soon as /backup exists (and is writeable).
While not a serious bug per se it cost me half a day to find the error source since I first guessed something with my ssh authorized keys was wrong...
This bug occurs with duplicity 0.5.17 and 0.5.18, interpreted by python-2.6 on (mostly stable) gentoo linux (amd64). The target is a stable debian 5.0.2.
Verbose output:
uplicity -v9 --include-
Reading globbing filelist /etc/duplicity/
Main action: inc
Args: /usr/bin/duplicity -v9 --include-
/usr/bin/python 2.6.2 (r262:71600, Jul 31 2009, 19:25:10)
[GCC 4.3.2]
duplicity 0.5.18 (May 20, 2009)
Linux whatnow 2.6.30-gentoo-r4 #1 SMP Sat Aug 8 02:14:31 CEST 2009 x86_64 AMD Athlon(tm) X2 Dual Core Processor BE-2300
Using temporary directory /tmp/duplicity-
Registering (mkstemp) temporary file /tmp/duplicity-
Temp has 10012819456 available, backup will use approx 34078720.
Running 'sftp -oServerAliveIn
State = sftp, Before = 'Connecting to someserver...'
sftp command: 'mkdir /backup1'
State = sftp, Before = 'mkdir /backup1
Couldn't create directory:'
Invalid SSH password
Running 'sftp -oServerAliveIn
^CRemoving still remembered temporary file /tmp/duplicity-
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
globals.
File "/usr/lib64/
backend_
File "/usr/lib64/
l = self.run_
File "/usr/lib64/
time.sleep(30)
KeyboardInterrupt
Related branches
Changed in duplicity: | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in duplicity: | |
assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
milestone: | none → 0.6.06 |
Changed in duplicity: | |
milestone: | 0.6.06 → none |
Changed in duplicity: | |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
status: | In Progress → Confirmed |
Changed in duplicity: | |
milestone: | none → 0.6.17 |
status: | Confirmed → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Same error, except I'm getting a "Couldn't get handle:" error too. Folders on both computers exist, I can sftp to the remote computer ok normally. I can back up to local folders with duplicity.
v0.6.08b
State = sftp, Before = 'Connecting to hs...' -GFzKA8- tempdir/ mktemp- 4j1Ojn- 2" "i5linux/ duplicity- full.20100704T1 10914Z. vol1.difftar. gpg"' -GFzKA8- tempdir/ mktemp- 4j1Ojn- 2" "i5linux/ duplicity- full.20100704T1 10914Z. vol1.difftar. gpg" GFzKA8- tempdir/ mktemp- 4j1Ojn- 2 to /home/hankin/ i5linux/ duplicity- full.20100704T1 10914Z. vol1.difftar. gpg terval= 15 -oServerAliveCo untMax= 1 hankin@hs' failed (attempt #1) GFzKA8- tempdir/ mktemp- 4j1Ojn- 2
sftp command: 'put "/tmp/duplicity
State = sftp, Before = 'put "/tmp/duplicity
Uploading /tmp/duplicity-
Couldn't get handle:'
Invalid SSH password
Running 'sftp -oIdentityFile=xxx -oServerAliveIn
^CRemoving still remembered temporary file /tmp/duplicity-