duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] BackendException: ssh connection to ... failed: EOF


From: Sven
Subject: Re: [Duplicity-talk] BackendException: ssh connection to ... failed: EOF when reading a line
Date: Mon, 11 Feb 2013 13:44:29 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

edgar.soldin writes:
> did you update your duplicity lately?

Yes, and I've just reverted not just duplicity but also paramiko - and 
got one step closer to the source of the problem:

I can't easily revert back to duplicity-0.6.18 since this version has been 
pulled from Gentoo's mirrors already. However, I can revert to 
paramiko-1.7.7.1 and this problem DOES NOT exist with that version of 
paramiko.

Nevertheless, I've done the tests you've asked for:

> check if your script really is run as root and the file known_hosts is 
> there and contains your entry. maybe a weird changeroot problem.

Here's the script run as root cronjob:

#!/bin/bash
export URL='sftp://#####:address@hidden/config'
export PASSPHRASE='#####'
duplicity                                                                \
  --full-if-older-than 1W                                                \
  --encrypt-sign-key ########                                            \
  --include /etc                                                         \
  --exclude '**'                                                         \
  /                                                                      \
  ${URL}                                                                 \
  --verbosity 9

The job runs as root, here's what "ps aux" shows:

root      4664  0.0  0.0  11744  1500 ?        Ss   13:47   0:00 
  /bin/bash /opt/bin/duplicity-hetzner-config-test
root      4666  0.0  0.0 192096 15528 ?        Sl   13:47   0:00 
  /usr/bin/python2.7 /usr/bin/duplicity #####

And the output:

Using archive dir: //.cache/duplicity/#####
Using backup name: #####
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.u1backend Failed: No module named httplib2
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
The authenticity of host '#####' can't be established.
SSH-RSA key fingerprint is ##:##:##:##:##:##:##:##:##:##:##:##:##:##:##:##.
Are you sure you want to continue connecting (yes/no)? Using temporary 
  directory
  /tmp/duplicity-NIITrb-tempdir
Backend error detail: Traceback (most recent call last):
 File "/usr/bin/duplicity-2.7", line 1403, in <module>
   with_tempdir(main)
 File "/usr/bin/duplicity-2.7", line 1396, in with_tempdir
   fn()
 File "/usr/bin/duplicity-2.7", line 1247, in main
   action = commandline.ProcessCommandLine(sys.argv[1:])
 File "/usr/lib64/python2.7/site-packages/duplicity/commandline.py", 
   line 1002, in ProcessCommandLine
   backup, local_pathname = set_backend(args[0], args[1])
 File "/usr/lib64/python2.7/site-packages/duplicity/commandline.py",
   line 895, in set_backend
   globals.backend = backend.get_backend(bend)
 File "/usr/lib64/python2.7/site-packages/duplicity/backend.py",
   line 161, in get_backend
   return _backends[pu.scheme](pu)
 File "/usr/lib64/python2.7/site-packages/duplicity/backends/_ssh_paramiko
   .py", line 182, in __init__ self.config['port'],e))
BackendException: ssh connection to #####.de:22 failed: EOF when reading 
a line

BackendException: ssh connection to #####.de:22 failed: EOF when reading 
a line
Job /opt/bin/duplicity-hetzner-config-test terminated (exit status: 23) 
(mailing output)

> additionally switch back to the old ssh pexpect backend, via 
> --ssh-backend switch and see if that behaves differently.

The SFTP connection does work with pexpect backend. (However, I get an
unrelated "gpg: decryption failed: No secret key" error further down.)

Cheers, -sven





reply via email to

[Prev in Thread] Current Thread [Next in Thread]