Return-Path: X-Original-To: apmail-whirr-dev-archive@www.apache.org Delivered-To: apmail-whirr-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E3EF9D30 for ; Fri, 23 Sep 2011 03:50:13 +0000 (UTC) Received: (qmail 40944 invoked by uid 500); 23 Sep 2011 03:50:12 -0000 Delivered-To: apmail-whirr-dev-archive@whirr.apache.org Received: (qmail 40032 invoked by uid 500); 23 Sep 2011 03:49:56 -0000 Mailing-List: contact dev-help@whirr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@whirr.apache.org Delivered-To: mailing list dev@whirr.apache.org Received: (qmail 39532 invoked by uid 99); 23 Sep 2011 03:49:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 03:49:47 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 03:49:46 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 20F26AA742 for ; Fri, 23 Sep 2011 03:49:26 +0000 (UTC) Date: Fri, 23 Sep 2011 03:49:26 +0000 (UTC) From: "Adrian Cole (JIRA)" To: dev@whirr.apache.org Message-ID: <772045840.4934.1316749766131.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <416716495.8004.1314719377890.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (WHIRR-378) Auth fail when creating a cluster from an EC2 instance MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/WHIRR-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113142#comment-13113142 ] Adrian Cole commented on WHIRR-378: ----------------------------------- OK I think this testing is done. We need more info before taking any more action, as this config is pretty expensive to test! My guess based on the error, is that there is an issue in ~/.ssh/id_rsa or ~/.ssh/id_rsa.pub, something we can possibly validate prior to use. My suggestion is that the user generate new keys and try having whirr use them, especially as this problem is noted in both ec2 and rackspace. > 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] > <> woke to: net.schmizz.sshj.userauth.UserAuthException: publickey auth failed > <> 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