You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Michael David (Commented) (JIRA)" <ji...@apache.org> on 2012/01/03 22:30:40 UTC
[jira] [Commented] (WHIRR-378) Auth fail when creating a cluster
from an EC2 instance
[ https://issues.apache.org/jira/browse/WHIRR-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179032#comment-13179032 ]
Michael David commented on WHIRR-378:
-------------------------------------
I am seeing the same SSH issue, and I am not running as root. I am running as the default user ec2-user.
It seems as if whirr is creating a new keypair despite the fact that I already have set one in my properties.
I've tried a number of AMIs from various tutorials, and can't seem to get it to ssh in.
whirr version: Whirr 0.5.0-cdh3u2
hadoop version: Hadoop 0.20.2-cdh3u2
I've spent hours trying to get to the bottom of this with no luck so far.
Thanks for any help!
Properties FILE:
--------------------
whirr.cluster-name=myhadoopcluster
whirr.instance-templates=1 hadoop-jobtracker+hadoop-namenode,1 hadoop-datanode+hadoop-tasktracker
whirr.provider=aws-ec2
whirr.identity=<my actual key>
whirr.credential=<my secret key>
whirr.login-user=ec2-user
whirr.hardware-id=m1.small
whirr.image-id=us-east-1/ami-6936fb00
whirr.private-key-file=/home/ec2-user/.ssh/id_rsa
whirr.public-key-file=/home/ec2-user/.ssh/id_rsa.pub
whirr.hadoop-install-function=install_cdh_hadoop
whirr.hadoop-configure-function=configure_cdh_hadoop
LOGS:
--------------
[org.apache.whirr.actions.NodeStarter] (pool-5-thread-5) Starting 1 node(s) with roles [hadoop-datanode, hadoop-tasktracker]
2012-01-03 21:01:08,903 DEBUG [jclouds.compute] (pool-5-thread-5) >> running 1 node group(myhadoopcluster) location(us-east-1) image(us-east-1/ami-6936fb00) hardwareProfile(m1.small) options([groupIds=[], keyPair=null, noKeyPair=false, monitoringEnabled=false, placementGroup=null, noPlacementGroup=false, subnetId=null, userData=null, blockDeviceMappings=[]])
2012-01-03 21:01:08,904 DEBUG [jclouds.compute] (pool-5-thread-5) >> creating keyPair region(us-east-1) tag(myhadoopcluster)
2012-01-03 21:01:09,245 DEBUG [jclouds.compute] (pool-5-thread-5) << created keyPair(jclouds#myhadoopcluster#us-east-1#70)
2012-01-03 21:01:09,246 DEBUG [jclouds.compute] (pool-5-thread-5) >> running 1 instance region(us-east-1) zone(null) ami(ami-6936fb00) params({InstanceType=[m1.small], SecurityGroup.1=[jclouds#myhadoopcluster#us-east-1], KeyName=[jclouds#myhadoopcluster#us-east-1#70]})
2012-01-03 21:01:09,542 DEBUG [jclouds.compute] (pool-5-thread-5) << started instances(i-xxx)
2012-01-03 21:01:09,610 DEBUG [jclouds.compute] (pool-5-thread-5) << present instances(i-xxx8)
2012-01-03 21:01:24,697 DEBUG [jclouds.compute] (user thread 6) >> blocking on socket [address=02.xx.xx.xx, port=22] for 600000 seconds
2012-01-03 21:01:25,777 DEBUG [jclouds.compute] (user thread 6) << socket [address=01.xx.xx.xx, port=22] opened
2012-01-03 21:01:48,490 DEBUG [jclouds.compute] (user thread 6) >> blocking on socket [address=02.xx.xx.xx, port=22] for 600000 seconds
2012-01-03 21:01:48,493 DEBUG [jclouds.compute] (user thread 6) << socket [address=01.xx.xx.xx, port=22] opened
2012-01-03 21:01:54,292 ERROR [jclouds.compute] (user thread 6) << problem applying options to node(us-east-1/i-901170f2):
org.jclouds.ssh.SshException: ec2-user@xx.xx.xx.xx: Error connecting to session.
at org.jclouds.ssh.jsch.JschSshClient.propagate(JschSshClient.java:251)
at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:205)
at org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:89)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:139)
at org.jclouds.compute.strategy.CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(CustomizeNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:55)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: com.jcraft.jsch.JSchException: Auth fail
at com.jcraft.jsch.Session.connect(Session.java:461)
at com.jcraft.jsch.Session.connect(Session.java:154)
at org.jclouds.ssh.jsch.JschSshClient.newSession(JschSshClient.java:246)
at org.jclouds.ssh.jsch.JschSshClient.connect(JschSshClient.java:185)
> 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
> Priority: Critical
> Fix For: 0.8.0
>
> Attachments: run-test.sh, setup-whirr.sh
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira