ORBIT-USER: Re: Orbit handler unable to connect via ssh.

[Mesut Ali Ergin]

I usually get around with it via an expect script, called by a bash 
script (yes, I was too lazy to find out how to loop in expect :) for the 
set of nodes you want to process. Such as

EXPECT SCRIPT
===================
#!/usr/bin/expect -f

spawn /usr/bin/ssh root@[lindex $argv 0] touch /tmp/1
expect "(yes/no)?"
send -- "yes\r"
expect "yes"


BASH SCRIPT
===================
#!/bin/bash

for node in `cat /path/to/nodelistfile`
do
   ./above_expect_script $node
done


You can also download public keys from each node and put them into your 
.ssh/known_hosts file.

Good luck,

-- 
Mesut Ali Ergin
ergin at winlab.rutgers.edu

Rutgers University, WINLAB,
Technology Center of New Jersey,
671 Rt. 1 South, North Brunswick,
New Jersey, 08902-3390, USA

Phone: 862-368-6620
Fax:   732-932-6882


Andrea G Forte wrote:
> I think I have figured out the previous problem with the ssh connection. 
> However, now I have another one where it asks me per each node to accept 
> the signature and I get:
> RSA key fingerprint is aa:be:32:7f:8f:03:c7:70:91:6d:d8:5c:69:57:4b:6c.
> Are you sure you want to continue connecting (yes/no)? The authenticity 
> of host 'node8-2 (10.10.8.2)' can't be established.
> 
> What can I do to override this?
> 
> -Andrea
>