So before I burn another $ for nothing....should I try a) ssh-i ~/.ssh/id_rsa ec2-50-17-89-76.compute-1.amazonaws.com or did you mean
b) define whirr.cluster-user = myName and after cluster launch connect with: ssh-i ~/.ssh/id_rsa [email protected] ? ________________________________ Von: Andrei Savu <[email protected]> An: [email protected]; Christian Schäfer <[email protected]> Gesendet: 10:23 Montag, 31.Oktober 2011 Betreff: Re: hbase cluster setup works - ssh to machine doesnt It is just discard ubuntu@host. whirr.cluster-user = your local user -- Andrei Savu On Mon, Oct 31, 2011 at 11:19 AM, Christian Schäfer <[email protected]> wrote: As written in my inital mail I exactly do installl and login as in the whirr faq/tutorial > >e.g. > >hbase-ec2.properties > >>whirr.private-key-file=${sys:user.home}/.ssh/id_rsa >>whirr.public-key-file=${sys:user.home}/.ssh/id_rsa.pub > > >>ssh -i ~/.ssh/id_rsa [email protected] > >the jira is maybe helpful...but when I configure whirr with freshly generated >rsa key pair it should after install be possible to login with the same >keys...but isnt :( > > >________________________________ >Von: Andrei Savu <[email protected]> >An: [email protected]; Christian Schäfer <[email protected]> >Gesendet: 8:49 Montag, 31.Oktober 2011 >Betreff: Re: hbase cluster setup works - ssh to machine doesnt > > > >From the FAQ: http://whirr.apache.org/faq.html >How do I log in to a node in the cluster? >On EC2, if you know the node's address you can do: >ssh -i ~/.ssh/id_rsa <whirr.cluster-user>@host >This assumes that you use the default private key; if this is not the case >then specify the one you used at cluster launch. >whirr.cluster-user defaults to the name of the local user running Whirr. >I have also created this new JIRA issue so that we can actually display the >SSH command in the console: >https://issues.apache.org/jira/browse/WHIRR-419 >Cheers, >-- Andrei Savu / andreisavu.ro > > > >On Mon, Oct 31, 2011 at 1:22 AM, Christian Schäfer <[email protected]> >wrote: > > >> >>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 [email protected] >> >>...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 >> >> >> >> >> >> > > >
