[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Backup to pool with different hostkeys
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Backup to pool with different hostkeys |
Date: |
Sat, 06 Apr 2013 17:26:27 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 |
On 06.04.2013 14:22, Roman wrote:
> Hi everyone,
>
> i was just revisiting duplicity for my server-backups.
>
> I am running a cluster of backup-servers under the same dns "fs.hasnoname.de"
> with different IPs/Hostnames and Hostkeys.
>
> Via ssh/scp on the console this is not a problem with the following
> ~/.ssh/config:
>
> Host fs.hasnoname.de
> user xyz
> CheckHostIP no
>
> But running duplicity as the same user:
>
> ~> duplicity /etc scp://fs.hasnoname.de:22/backup
>
>
> Produces this error about the different Hostkey. Shouldn't duplicity take the
> settings from ~/.ssh/config? Or where else can i change this behaviour of
> duplicity?
>
> Benutze temporäres Verzeichnis /tmp/duplicity-Gd8Pr_-tempdir
> Backend Fehler Detail: Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1411, in <module>
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1404, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1255, in main
> action = commandline.ProcessCommandLine(sys.argv[1:])
> File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line
> 1007, in ProcessCommandLine
> backup, local_pathname = set_backend(args[0], args[1])
> File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 900,
> in set_backend
> globals.backend = backend.get_backend(bend)
> File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 158, in
> get_backend
> return _backends[pu.scheme](pu)
> File "/usr/lib/python2.7/dist-packages/duplicity/backends/sshbackend.py",
> line 115, in __init__
> raise BackendException("ssh connection to %s:%d failed: %s" %
> (parsed_url.hostname,portnumber,e))
> BackendException: ssh connection to fs.hasnoname.de:22 failed: Host key for
> server fs.hasnoname.de does not match!
>
> BackendException: ssh connection to fs.hasnoname:22 failed: Host key for
> server fs.domain.de does not match!
>
>
probably paramiko ssh backend does not support this option. switching back to
--ssh-backend pexpect should solve that for you.
..ede/duply.net