[
https://issues.apache.org/jira/browse/WHIRR-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113110#comment-13113110
]
Adrian Cole edited comment on WHIRR-378 at 9/23/11 2:20 AM:
------------------------------------------------------------
I just ran this on 0.7.0, and received a different error ( a transient one
related to ec2 ssh keys [1] ).
However, things operated did come up without the ssh error you mentioned. How
are your ssh keys setup? Do you have a ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub file
in correct form? Are you destroying your cluster through whirr or elsewhere?
I'll also try with 0.6.0 now
-- snip --
Running configuration script on nodes: [us-east-1/i-5032a530,
us-east-1/i-5232a532, us-east-1/i-5432a534]
Configuration script run completed
Running configuration script on nodes: [us-east-1/i-4c32a52c]
Configuration script run completed
Completed configuration of hadoop
Namenode web UI available at
http://ec2-184-72-85-39.compute-1.amazonaws.com:50070
Jobtracker web UI available at
http://ec2-184-72-85-39.compute-1.amazonaws.com:50030
Wrote Hadoop site file /Users/adriancole/.whirr/hadoop/hadoop-site.xml
Wrote Hadoop proxy script /Users/adriancole/.whirr/hadoop/hadoop-proxy.sh
Wrote instances file /Users/adriancole/.whirr/hadoop/instances
Started cluster of 4 instances
--snip --
[1] http://code.google.com/p/jclouds/issues/detail?id=696
was (Author: [email protected]):
I just ran this on 0.7.0, and received a different error ( a transient one
related to ec2 ssh keys [1], which ended up having us create a 4th node ).
However, things operated did come up without the ssh error you mentioned. How
are your ssh keys setup? Do you have a ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub file
in correct form? Are you destroying your cluster through whirr or elsewhere?
I'll also try with 0.6.0 now
-- snip --
Running configuration script on nodes: [us-east-1/i-5032a530,
us-east-1/i-5232a532, us-east-1/i-5432a534]
Configuration script run completed
Running configuration script on nodes: [us-east-1/i-4c32a52c]
Configuration script run completed
Completed configuration of hadoop
Namenode web UI available at
http://ec2-184-72-85-39.compute-1.amazonaws.com:50070
Jobtracker web UI available at
http://ec2-184-72-85-39.compute-1.amazonaws.com:50030
Wrote Hadoop site file /Users/adriancole/.whirr/hadoop/hadoop-site.xml
Wrote Hadoop proxy script /Users/adriancole/.whirr/hadoop/hadoop-proxy.sh
Wrote instances file /Users/adriancole/.whirr/hadoop/instances
Started cluster of 4 instances
--snip --
[1] http://code.google.com/p/jclouds/issues/detail?id=696
> Auth fail when creating a cluster from an EC2 instance
> ------------------------------------------------------
>
> Key: WHIRR-378
> URL: https://issues.apache.org/jira/browse/WHIRR-378
> Project: Whirr
> Issue Type: Bug
> Components: service/hadoop
> Affects Versions: 0.6.0
> Reporter: Marc de Palol
> Assignee: Adrian Cole
>
> There is a ssh auth problem when creating a hadoop cluster from an EC2 ubuntu
> instance.
> I've been using the same configuration file from an EC2 computer an a
> physical one, everything works fine in the physical one, but I keep getting
> this error in EC2:
> Running configuration script on nodes: [us-east-1/i-c7fde5a6,
> us-east-1/i-c9fde5a8, us-east-1/i-cbfde5aa]
> <<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
> publickey auth failed
> <<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
> publickey auth failed
> The user in the virtual machine is new and with valid .ssh keys.
> The hadoop config file is (omitting commented lines):
> whirr.cluster-name=hadoop
> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker,3
> hadoop-datanode+hadoop-tasktracker
> whirr.provider=aws-ec2
> whirr.identity=****
> whirr.credential=****
> whirr.hardware-id=c1.xlarge
> whirr.image-id=us-east-1/ami-da0cf8b3
> whirr.location-id=us-east-1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
