Mailing-List: contact dev-help@provisionr.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@provisionr.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of savu.andrei@gmail.com
 designates 209.85.212.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <519F3EAC.20301@adobe.com>
References: <519F3EAC.20301@adobe.com>
From: Andrei Savu <savu.andrei@gmail.com>
Date: Fri, 24 May 2013 13:36:09 +0300
Message-ID: 
 <CAHZL8y84OcEZP-Dzq0p0tkwj49f4uqh8CUWV0K+tUysX5+8uOA@mail.gmail.com>
Subject: Re: cannot connect to ec2 instances
To: dev <dev@provisionr.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a11c385be270cda04dd745f39

--001a11c385be270cda04dd745f39
Content-Type: text/plain; charset=ISO-8859-1

Hi Tudor -

Do you get the same failure even if you don't specify the --public-key-path
 and --private-key-path? Is this happening every time?

Provisionr should use  the same keys by default.

-- Andrei Savu

On Fri, May 24, 2013 at 1:19 PM, Tudor Rogoz <rogoz@adobe.com> wrote:

> Hi,
>
> I'm trying to create a pool of instances using the following command.
>
> provisionr:create --id amazon --key r3 --size 2 --volume /dev/sda1:8
> --volume /dev/sda2:8 --hardware-type m1.medium --public-key-path
> /home/tudor/.ssh/id_rsa.pub --private-key-path /home/tudor/.ssh/id_rsa
> --template mongos --image-id ami-3ac64a0a --timeout 1200
>
> The ec2 instances are created, each of them with the attached volumes, but
> it seems that the ssh connection fails during initialization.I tried also
> without the keys parameters and it's the same behavior.
> I took a fragment from the log [0], do you know which may be the problem?
>
> Thanks,
> Tudor
>
> [0]
> 2013-05-24 12:39:49,703 | INFO  | reader           | Ssh
>            | 97 - org.apache.provisionr.core - 0.4.0.incubating-SNAPSHOT |
> Automatically accepting host key for ec2-54-244-156-198.us-west-2.**
> compute.amazonaws.com:22<http://ec2-54-244-156-198.us-west-2.compute.amazonaws.com:22>with fingerprint dc:a8:3a:af:1d:2a:0a:ab:9a:77:
> **de:e9:d0:07:da:53
> 2013-05-24 12:39:50,466 | ERROR | ool-10-thread-17 | Promise
>            | 93 - net.schmizz.sshj - 0.8.1 | <<authenticated>> woke to:
> net.schmizz.sshj.userauth.**UserAuthException: publickey auth failed
> 2013-05-24 12:39:50,468 | ERROR | ool-10-thread-17 | CommandContext
>             | 88 - org.activiti.engine - 5.10.0 | Error while closing
> command context
> org.activiti.engine.impl.pvm.**PvmException: couldn't execute activity
> <serviceTask id="setupAdminAccess" ...>: Exhausted available authentication
> methods
>     at org.activiti.engine.impl.pvm.**runtime.**
> AtomicOperationActivityExecute**.execute(**AtomicOperationActivityExecute*
> *.java:48)[88:org.activiti.**engine:5.10.0]
>     at org.activiti.engine.impl.**interceptor.CommandContext.**
> performOperation(**CommandContext.java:80)[88:**
> org.activiti.engine:5.10.0]
>
>

--001a11c385be270cda04dd745f39--