[
https://issues.apache.org/jira/browse/WHIRR-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165316#comment-13165316
]
Carlos González-Cadenas commented on WHIRR-378:
-----------------------------------------------
Hello,
I'm running your setup and run scripts attached but I cannot successfully
launch a cluster on EC2.
First I launch in US-EAST-1 a Natty image (ami-fd589594). Then I run the setup
script and then the run-test script.
After creating the instances, whirr starts giving errors and retrying with no
success (see below). Can you help us with this?
Thanks
Carlos
Running configuration script on nodes: [us-east-1/i-c70415a4,
us-east-1/i-c50415a6, us-east-1/i-cb0415a8]
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
Dying because - java.net.SocketTimeoutException: Read timed out
Dying because - java.net.SocketTimeoutException: Read timed out
<<authenticated>> woke to: net.schmizz.sshj.userauth.UserAuthException:
publickey auth failed
<< ([email protected]:22) error acquiring SSHClient([email protected]:22):
Exhausted available authentication methods
net.schmizz.sshj.userauth.UserAuthException: Exhausted available authentication
methods
at
net.schmizz.sshj.userauth.UserAuthImpl.authenticate(UserAuthImpl.java:114)
at net.schmizz.sshj.SSHClient.auth(SSHClient.java:204)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:304)
at net.schmizz.sshj.SSHClient.authPublickey(SSHClient.java:323)
at org.jclouds.sshj.SshjSshClient$1.create(SshjSshClient.java:183)
at org.jclouds.sshj.SshjSshClient$1.create(SshjSshClient.java:155)
at org.jclouds.sshj.SshjSshClient.acquire(SshjSshClient.java:204)
at org.jclouds.sshj.SshjSshClient.connect(SshjSshClient.java:229)
at
org.jclouds.compute.callables.RunScriptOnNodeAsInitScriptUsingSsh.call(RunScriptOnNodeAsInitScriptUsingSsh.java:107)
at
org.jclouds.compute.strategy.RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.call(RunScriptOnNodeAndAddToGoodMapOrPutExceptionIntoBadMap.java:69)
> 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
> 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
