You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2011/03/21 11:50:05 UTC
[jira] [Created] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
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 ubuntu@10.245.106.99
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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
[jira] [Updated] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-268:
------------------------------
Attachment: WHIRR-268.patch
Trivial patch as discussed.
> 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
> Attachments: WHIRR-268.patch
>
>
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009930#comment-13009930 ]
Adrian Cole commented on WHIRR-268:
-----------------------------------
lets do this for all private ranges?
// 24-bit Block (/8 prefix, 1/A) 10.0.0.0 10.255.255.255
// 20-bit Block (/12 prefix, 16/B) 172.16.0.0 172.31.255.255
// 16-bit Block (/16 prefix, 256/C) 192.168.0.0 192.168.255.255 65536
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010954#comment-13010954 ]
Adrian Cole commented on WHIRR-268:
-----------------------------------
no problem using the previous patch. I thought that hadoop itself depends in ssh inter-connectivity inside the cloud. just ignore or remove the patch I sent.
> 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
> Attachments: WHIRR-268.patch, WHIRR-268.patch
>
>
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009881#comment-13009881 ]
Tom White commented on WHIRR-268:
---------------------------------
I've seen this occasionally and have had to edit known_hosts manually. Is there a better way to deal with this? At the very least we should put guidance in the docs.
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Resolved] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu resolved WHIRR-268.
-------------------------------
Resolution: Fixed
I've just committed the first version of the patch. Thanks guys!
> 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
> Assignee: Andrei Savu
> Fix For: 0.5.0
>
> Attachments: WHIRR-268.patch, WHIRR-268.patch
>
>
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Updated] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Savu updated WHIRR-268:
------------------------------
Fix Version/s: 0.5.0
Assignee: Andrei Savu
> 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
> Assignee: Andrei Savu
> Fix For: 0.5.0
>
> Attachments: WHIRR-268.patch, WHIRR-268.patch
>
>
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Issue Comment Edited] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Hyunsik Choi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009920#comment-13009920 ]
Hyunsik Choi edited comment on WHIRR-268 at 3/23/11 12:09 AM:
--------------------------------------------------------------
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?
was (Author: hyunsik.choi):
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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009898#comment-13009898 ]
Adrian Cole commented on WHIRR-268:
-----------------------------------
I'm guessing by the log output that this is coming from the ssh proxy, which uses commandline ssh.
we should be able to work around this by adding the following to the ssh args:
-o StrictHostKeyChecking=no
http://www.symantec.com/connect/articles/ssh-host-key-protection
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Hyunsik Choi (JIRA)" <ji...@apache.org>.
[ 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009899#comment-13009899 ]
Tom White commented on WHIRR-268:
---------------------------------
Even when StrictHostKeyChecking is set to 'no' the keys are added to known_hosts - the problem is that nothing removes them, so there is a risk of conflicts if you get the same host for another cluster.
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009903#comment-13009903 ]
Tom White commented on WHIRR-268:
---------------------------------
I think the hanging may be coincidental since jclouds doesn't use known_hosts AFAIK. But it is a problem with the Hadoop proxy, which is run from the user's laptop, or if the user tries to ssh into a machine in the cluster.
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009924#comment-13009924 ]
Tom White commented on WHIRR-268:
---------------------------------
Looks like the best solution I've seen.
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009901#comment-13009901 ]
Adrian Cole commented on WHIRR-268:
-----------------------------------
ahh.. sorry. I see what you mean. this is from within the cluster, and not the user's laptop?
maybe on configure() we can address this?
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Updated] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Adrian Cole (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Cole updated WHIRR-268:
------------------------------
Attachment: WHIRR-268.patch
patch includes prior changes and then adds the /etc/ssh/ssh_config rules.
tested on cloudservers-us
> 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
> Attachments: WHIRR-268.patch, WHIRR-268.patch
>
>
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010929#comment-13010929 ]
Andrei Savu commented on WHIRR-268:
-----------------------------------
Adrian, I don't understand why we need to update ssh_config (global ssh client settings) on the nodes. We are only seeing this problem on the client running Whirr and nodes always start with an empty known_hosts file. By doing this we make nodes vulnerable to man-in-the-middle attacks inside the cloud provider network. The first patch should be enough to solve the reported issue.
> 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
> Attachments: WHIRR-268.patch, WHIRR-268.patch
>
>
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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
[jira] [Commented] (WHIRR-268) whirr hangs when the file
'$HOME/.ssh/known_hosts' includes an obsolete identifier for a certain ip
address host.
Posted by "Hyunsik Choi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WHIRR-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010047#comment-13010047 ]
Hyunsik Choi commented on WHIRR-268:
------------------------------------
@Adrian That's good idea. Intuitively, I know how to set both A and C class private ranges. They will be as follows:
{noformat}
Host 10.*.*.*
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null
Host 192.168.*.*
StrictHostKeyChecking no
UserKnownHostsFile=/dev/null
{noformat}
However, I cannot find how to set B class private range. According to ssh_config man page, openssh seems to only support '*' and '?' for IP range patterns.
Anyone knows that?
> 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 ubuntu@10.245.106.99
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ 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