You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@provisionr.apache.org by Tudor Rogoz <ro...@adobe.com> on 2013/05/24 12:19:24 UTC
cannot connect to ec2 instances
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 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]
Re: cannot connect to ec2 instances
Posted by Tudor Rogoz <ro...@adobe.com>.
Hi
Thanks a lot, I changed the image and it works.
Tudor
On 05/24/2013 02:13 PM, Andrei Savu wrote:
>
> On Fri, May 24, 2013 at 2:01 PM, Tudor Rogoz <rogoz@adobe.com
> <ma...@adobe.com>> wrote:
>
> Yes is the same situation, and is happening every time.
>
>
> You should be using an Ubuntu OS - the Puppet user admin scripts
> assume Ubuntu. I haven't tested with Amazon Linux.
>
> Try selecting an AMI from here:
> http://cloud-images.ubuntu.com/locator/ec2/
>
> 12.04 LTS should be good enough.
>
> -- Andrei Savu
Re: cannot connect to ec2 instances
Posted by Andrei Savu <sa...@gmail.com>.
On Fri, May 24, 2013 at 2:01 PM, Tudor Rogoz <ro...@adobe.com> wrote:
> Yes is the same situation, and is happening every time.
You should be using an Ubuntu OS - the Puppet user admin scripts assume
Ubuntu. I haven't tested with Amazon Linux.
Try selecting an AMI from here:
http://cloud-images.ubuntu.com/locator/ec2/
12.04 LTS should be good enough.
-- Andrei Savu
Re: cannot connect to ec2 instances
Posted by Tudor Rogoz <ro...@adobe.com>.
Hi Andrei,
Yes is the same situation, and is happening every time.
Tudor
On 05/24/2013 01:36 PM, Andrei Savu wrote:
> 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 <ro...@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]
>>
>>
Re: cannot connect to ec2 instances
Posted by Andrei Savu <sa...@gmail.com>.
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 <ro...@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]
>
>