[
https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009920#comment-13009920
]
Hyunsik Choi commented on WHIRR-268:
------------------------------------
I found an ad-hoc solution. The solution is to add the ssh option '-o
UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no'. Another way is to
modify the global ssh configuration file (/etc/ssh/ssh_config) or user-specific
configuration file (${HOME}/.ssh/config') with the following lines:
Host 10.*.*.*
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null
How about this way?
> whirr hangs when the file '$HOME/.ssh/known_hosts' includes an obsolete
> identifier for a certain ip address host.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WHIRR-268
> URL: https://issues.apache.org/jira/browse/WHIRR-268
> Project: Whirr
> Issue Type: Bug
> Components: core
> Affects Versions: 0.3.0
> Reporter: Hyunsik Choi
>
> my properties file is ...
> {noformat}
> $ cat cluster.properties
> whirr.cluster-name=mycluster
> whirr.instance-templates=1 jt+nn,10 dn+tt
> whirr.provider=ec2
> whirr.identity=XXXXXXXXXXXXXXXXXXXX
> whirr.credential=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> whirr.private-key-file=${sys:user.home}/.ssh/id_rsa
> whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub
> whirr.location-id=us-east-1d
> #whirr.hardware-id=m1.small
> whirr.hardware-id=c1.medium
> whirr.service-name=hadoop
> # for m1.small
> #whirr.image-id=us-east-1/ami-2caa5845
> whirr.image-id=us-east-1/ami-7000f019
> {noformat}
> {noformat}
> $ whirr/bin/whirr launch-cluster --config cluster.properties
> Bootstrapping cluster
> Configuring template
> Starting 10 node(s) with roles [tt, dn]
> Configuring template
> Starting 1 node(s) with roles [jt, nn]
> Nodes started: [[id=us-east-1/i-ba63a7d5, providerId=i-ba63a7d5,
> tag=mycluster, name=null,
> location=[id=us-east-1a, scope=ZONE, description=us-east-1a,
> parent=us-east-1], uri=null,
> imageId=us-east-1/ami-7000f019, os=[name=null, family=ubuntu, version=10.04,
> arch=paravirtual,
> is64Bit=false, description=ubuntu-images-us/ubuntu-lucid-10.04-i386-server-
> 20110201.1.manifest.xml], userMetadata={}, state=RUNNING,
> privateAddresses=[10.245.106.99],
> publicAddresses=[184.72.166.132], hardware=[id=c1.medium,
> providerId=c1.medium, name=c1.medium,
> processors=[[cores=2.0, speed=2.5]], ram=1740, volumes=[[id=null, type=LOCAL,
> size=10.0,
> device=/dev/sda1, durable=false, isBootDevice=true], [id=null, type=LOCAL,
> size=340.0,
> device=/dev/sda2, durable=false, isBootDevice=false]],
> supportsImage=Not(is64Bit())]]]
> {noformat}
> As you can see the above message, whirr is trying to startup a host whose ip
> address is '10.245.106.99'. But, whirr hangs and doesn't startup the hadoop
> service. So, I tried to login to the host '10.245.106.99' via ssh.
> {noformat}
> hadoop@domU-12-31-39-00-A5-21:~$ ssh [email protected]
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> Someone could be eavesdropping on you right now (man-in-the-middle attack)!
> It is also possible that the RSA host key has just been changed.
> The fingerprint for the RSA key sent by the remote host is
> b1:62:ad:fd:3f:a7:29:df:7f:0c:91:ca:ed:66:8e:3a.
> Please contact your system administrator.
> Add correct host key in /home/hadoop/.ssh/known_hosts to get rid of this
> message.
> Offending key in /home/hadoop/.ssh/known_hosts:8
> RSA host key for 10.245.106.99 has changed and you have requested strict
> checking.
> Host key verification failed.
> {noformat}
> I expected that whirr hangs when the file '$HOME/.ssh/known_hosts' includes
> the obsolete entry. Although such case may occur rarely, someone who employs
> many instances in EC2 would meet such case. whirr needs to prevent hanging
> caused by obsolete identifiers of ssh.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
