[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] BackendException: ssh connection to ... failed: EOF
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] BackendException: ssh connection to ... failed: EOF when reading a line |
Date: |
Mon, 11 Feb 2013 13:18:21 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 |
On 11.02.2013 11:25, Sven wrote:
> Debug verbosity shows the following if and only if the script is run by fcron:
>
>> The authenticity of host 'u37398.your-backup.de' can't be established.
>> SSH-RSA key fingerprint is ###.
>> Are you sure you want to continue connecting (yes/no)?
>
> The host is in root's .ssh/known_hosts and I can connect with sftp.
>
> It appears Paramiko doesn't read root's .ssh/known_hosts, yet why? The only
> difference I see in the environments are that as a cronjob, no terminal is
> attached - no surprise.
>
> The versions are duplicity-0.6.20 and paramiko-1.9.0.
>
> I'm not sure what to try next. Thanks for hints!
>
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.
additionally switch back to the old ssh pexpect backend, via --ssh-backend
switch and see if that behaves differently.
ssh paramiko backend known_hosts file support was added a while ago in 0.6.19,
see
http://bazaar.launchpad.net/~duplicity-team/duplicity/0.6-series/view/head:/duplicity/backends/_ssh_paramiko.py#L109
so it should work.
did you update your duplicity lately?
please send the output of a run with max verbosity next '-v9' (obfuscate
private strings in it), so we can see your full command line and more detailed
what is going on.
.ede/duply.net