[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 15:51:38 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 |
On 11.02.2013 15:04, address@hidden wrote:
> On 11.02.2013 14:44, Sven wrote:
>> 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
>
> check http://duply.net/?title=Duply-documentation under TIP on how to install
> several duplicity versions in parallel
>
>> paramiko-1.7.7.1 and this problem DOES NOT exist with that version of
>> paramiko.
>
> hmmm.. maybe a paramiko API change. i'll check.
>
ok .. i verified duplicity 0.6.21 against paramiko 1.8 and 1.9 and found no
problem. i ran it as user and as root.
if the host entry is not in ~/.ssh/known_hosts you get the prompt. if it is
everything runs as expected.
please verify that the entry is indeed in your known host and the key is still
identical. when in doubt but the server is trusted acknowledge the "new" key
and it will be added to the known hosts file. is it generally possible that
your sftp space provider simply changed the key?
..ede/duply.net