You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Joris Poort (Commented) (JIRA)" <ji...@apache.org> on 2012/03/02 08:03:00 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=13220740#comment-13220740 ] 

Joris Poort commented on WHIRR-378:
-----------------------------------

Having some issues with this again - not sure if its from 0.7.1 but we just transitioned to this latest version.

2012-03-01 22:54:24,843 ERROR [net.schmizz.sshj.transport.TransportImpl] (reader) Dying because - java.net.SocketTimeoutException: Read timed out
2012-03-01 22:54:30,986 ERROR [net.schmizz.sshj.transport.TransportImpl] (reader) Dying because - java.net.SocketTimeoutException: Read timed out

I started with a working configuration (standard Ubuntu 10.04) then created a custom AMI (without changing anything) and tried to boot the cluster.

I'm using:
whirr.bootstrap-user=ubuntu
whirr.cluster-user=whirr
jclouds.ec2.ami-query=owner-id=[ID]

Any ideas on what I can try out?

Thanks in advance!

                
> 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