whirr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schäfer <syrious3...@yahoo.de>
Subject hbase cluster setup works - ssh to machine doesnt
Date Sun, 30 Oct 2011 23:22:12 GMT


Hi there,


just trying to get my first hbase test cluster of 6 machines working using whirr-0.6.0-incubating...



before cluster launch  I generated public/private key 

>ssh-keygen -t rsa -P '' -f ~/.ssh/id_rsa

..and set  key files in hbase-ec2.properties as follows

>whirr.private-key-file=${sys:user.home}/.ssh/id_rsa
>whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub


After:
>/whirr-0.6.0-incubating$ bin/whirr launch-cluster --config hbase-ec2.properties (prop.
copied from recipes to parent dir)

..cluster setup finished without a problem..


But when I try (<user>@<machine> is copied from the aws console after choosing
"connect" on an  actually running machine ):
>ssh -i ~/.ssh/id_rsa ubuntu@ec2-204-236-242-13.compute-1.amazonaws.com

...I get permission denied:

>The authenticity of host 'ec2-204-236-242-13.compute-1.amazonaws.com (204.236.242.13)'
can't be established.
>RSA key fingerprint is **********************
>Are you sure you want to continue connecting (yes/no)? yes
>Warning: Permanently added 'ec2-204-236-242-13.compute-1.amazonaws.com,204.236.242.13'
(RSA) to the list of known hosts.
>Permission denied (publickey).


Has anybody a clue why that
 happens?

Another thing I dont understand is that whirr is creating a security group (jcloud...) and
when I choose "connect" in the aws console it proposes a jclouds...pem file  that I dont
own and dont know where to get it from



regards
Chris
Mime
View raw message