Errors during testing in 1.1 release

[Venkata Pingali]

Hi,

I was trying to get a simple poolparty test setup running but
ran into a bunch of problems. I have fixes for some but not
for some. I am in the middle of debugging another problem.

Errors and notes here:
http://gist.github.com/94109

-Venkata

[fairchild]

Hello,
Looks like some of the wiki needs to be updated.
We switched to jewler for the gem building tasks, so the command you
want is
rake install, not rake local_deploy anymore.
I just now updated the wiki page, http://wiki.github.com/auser/poolparty/installing

Also, it looks like the released gemspec needs to be updated again.
For now, try this:
rake clean_pkg && rake gemspec && rake install.
This should generate a new gem that does not require bind.rb

Also, IF you have trouble with libtar (required by suitcase), you can
pull my fork, which will work without libtar.
git submodule init
git submodule update
cd vendor/gems/suitcase/
git co master
git checkout --track -b master fairchild/master
git pull fairchild master


also, I pushed some changes to my fork of poolparty. mainly, adding
an each method to key, and adding auser-parenting to the list of
bootstraped gems.
You might want to try pulling in those changes.
http://github.com/fairchild/poolparty/commit/33b787dd9eca22b4cd2e08e572555fceede32b4c#L2R52
I just went to a computer that didn't have recent poolparty stuff on
it, and was able to cloud-start after making the above changes.
Hope it works for you,
~Michael

p.s. if you can fork the repo, and push your changes thats a much
easier way to see the impact of you patches, and easier to merge from.

[Mike Wadhera]

I spent some time updating the Install page: http://wiki.github.com/auser/poolparty/installing

I've included some missing gem dependencies, a note about net/ssh and
I cleaned up the test example section. Goal was to make this page more
friendly for new users (like me) who are installing from edge.

Though it took me several cycles to get this installed and my cloud up
& running, i'm looking forward to using poolparty in our EC2
production environment. Kudos to the team, this looks like a really
slick piece of software.

On Apr 12, 3:53 pm, fairchild <fairchild.mich...@gmail.com> wrote:
> Hello,
>   Looks like some of the wiki needs to be updated.
> We switched to jewler for the gem building tasks, so the command you
> want is
> rake install, not rake local_deploy anymore.

> I just now updated the wiki page,http://wiki.github.com/auser/poolparty/installing

>
> Also, it looks like the released gemspec needs to be updated again.
> For now, try this:
> rake clean_pkg && rake gemspec && rake install.
> This should generate a new gem that does not require bind.rb
>
> Also, IF you have trouble with libtar (required by suitcase), you can
> pull my fork, which will work without libtar.
> git submodule init
> git submodule update
> cd vendor/gems/suitcase/
> git co master
> git checkout --track -b master fairchild/master
> git pull fairchild master
>
> also, I pushed some changes to my fork of poolparty.  mainly, adding
> an each method to key, and adding auser-parenting to the list of
> bootstraped gems.

> You might want to try pulling in those changes.http://github.com/fairchild/poolparty/commit/33b787dd9eca22b4cd2e08e5...

[fairchild]

Hi Mike,
Thanks for taking the time to update the wiki page.
~Michael Fairchild

[Emil Tin]

thanks for updating the wiki install page. i tried to follow the
instructions but ran into the following problems. i'm on mac os x 10.5
intel, ruby 1.8.6.


1. installing the chef gem failed.
it required the extlib gem to be installed first.

2. rake build failed
but as suggested, running rake clean_pkg && rake gemspec first solved
it. however i still got this warning during 'rake build':
WARNING: no rubyforge_project specified

3. warnings during gem install
the following error was output four times during 'sudo gem install pkg/
poolparty-1.1.0.gem':
Could not find main page README

4. failed running ./bin/cloud-start -s clouds.rb
-bash: ./bin/cloud-start: No such file or directory
the cloud commands were not installed in ./bin/, so the suggested
command failed. simply running 'cloud-start -s clouds.rb' works for me.

5. starting the cloud failed because i had no key-pair.
> cloud-start -s clouds.rb
*** Starting cloud hello_world
0 running instances (1 - 1)
/Library/Ruby/Gems/1.8/gems/grempe-amazon-ec2-0.3.7/lib/EC2.rb:261:in
`ec2_error?': The key pair 'id_rsa' does not exist
(EC2::InvalidKeyPairNotFound)

6. adding keypair failed:
> cloud add-keypair
/Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing': stack level too
deep (SystemStackError)
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
... 4769 levels...
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/cloud-add-keypair:11

'cloud-add-keypair' produces the same error


7. trying to get help on specific cloud commands fails:
> cloud help add-keypair
/Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:42:in `method_missing': stack level too
deep (SystemStackError)
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
... 4795 levels...
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `send'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/../lib/poolparty/monitors/../../../vendor/gems/
dslify/lib/dslify/dslify.rb:52:in `method_missing'
from /Library/Ruby/Gems/1.8/gems/poolparty-1.1.0/bin/../lib/poolparty/
helpers/../../../bin/cloud-add-keypair:11

this seems to be the same error as when trying to add a keypair.



at this point i'm stuck.... any idea?

thanks for all the great work! looking forward to getting up running.


emil tin

[Emil Tin]

i see that i can in fact run cloud commands as ./bin/<command>, when
i'm inside the poolparty dir. however, the same errors result.

emil

[Mike Wadhera]

Hi Emil,

Re: #6 & 7, it looks like there is a bug in the bin/add-keypair script
that is sending the command into a stack overflow.

See the patch for this in Venkata's original gist.

I ended up using the ec2 java tools for generating my keypair instead
of patching -- specifically ec2-create-keypair, to create my keypair
(see the comment above the keypair directive in the clouds.rb for an
example)

--
Best,

Mike Wadhera
http://twitter.com/mikewadhera

[Venkata Pingali]

Thanks for the update. Will give it a try again.

Will use a fork to make it easier for you to pull in the changes.

On Apr 12, 3:53 pm, fairchild <fairchild.mich...@gmail.com> wrote:

> Hello,
>   Looks like some of the wiki needs to be updated.
> We switched to jewler for the gem building tasks, so the command you
> want is
> rake install, not rake local_deploy anymore.

> I just now updated the wiki page,http://wiki.github.com/auser/poolparty/installing

>
> Also, it looks like the released gemspec needs to be updated again.
> For now, try this:
> rake clean_pkg && rake gemspec && rake install.
> This should generate a new gem that does not require bind.rb
>
> Also, IF you have trouble with libtar (required by suitcase), you can
> pull my fork, which will work without libtar.
> git submodule init
> git submodule update
> cd vendor/gems/suitcase/
> git co master
> git checkout --track -b master fairchild/master
> git pull fairchild master
>
> also, I pushed some changes to my fork of poolparty.  mainly, adding
> an each method to key, and adding auser-parenting to the list of
> bootstraped gems.

> You might want to try pulling in those changes.http://github.com/fairchild/poolparty/commit/33b787dd9eca22b4cd2e08e5...

[Venkata Pingali]

This was a good work around. I wonder if my previous test
setup worked because of the explicit reference to keypair
in the clouds.rb.

On Apr 13, 2:27 am, Mike Wadhera <mikewadh...@gmail.com> wrote:
> Hi Emil,
>
> Re: #6 & 7, it looks like there is a bug in the bin/add-keypair script
> that is sending the command into a stack overflow.
>
> See the patch for this in Venkata's original gist.
>
> I ended up using the ec2 java tools for generating my keypair instead
> of patching -- specifically ec2-create-keypair, to create my keypair
> (see the comment above the keypair directive in the clouds.rb for an
> example)
>

> ...
>
> read more »

[Mike Wadhera]

So i've updated the page with information about which environment vars
PoolParty looks for & how to create a new keypair. This should make
the testing part a little smoother:

http://wiki.github.com/auser/poolparty/installing

If you have tried installing/testing before & run into problems,
please give it another shot & post any feedback you have.

[Emil Tin]

Hi,

Thanks for updating the wiki. I gave it another try. Here's what
happened.

I created the ec2 keypair manually using the ec2-add-keypair, and
updated clouds.rb to point to the new keypair file.

When starting the cloud I now got a bit further, but got this error:

~/poolparty$ ./bin/cloud-start -s clouds.rb

*** Starting cloud hello_world
0 running instances (1 - 1)

./bin/../lib/../vendor/gems/suitcase/lib/suitcase/zipper.rb:41:in
`add': undefined method `each' for #<PoolParty::Key:0x1a2a480>
(NoMethodError)
from ./bin/../lib/poolparty/poolparty/../provision/boot_strapper.rb:
68:in `pack_the_dependencies'
from ./bin/../lib/poolparty/poolparty/../provision/boot_strapper.rb:
97:in `default_commands'
from ./bin/../lib/poolparty/poolparty/../provision/boot_strapper.rb:
55:in `initialize'
from ./bin/cloud-start:15:in `new'
from ./bin/cloud-start:15
from ./bin/../lib/poolparty/net/remoter/cloud_control.rb:18:in `call'
from ./bin/../lib/poolparty/net/remoter/cloud_control.rb:18:in
`launch_instance!'
from ./bin/../lib/poolparty/net/remoter/cloud_control.rb:30:in `call'
from ./bin/../lib/poolparty/net/remoter/cloud_control.rb:30:in
`when_instance_is_responding'
from ./bin/../lib/poolparty/net/remoter/cloud_control.rb:17:in
`launch_instance!'
from ./bin/cloud-start:14
from ./bin/cloud-start:9:in `each'
from ./bin/cloud-start:9

Mike I think you mentioned something abouth this in an earlier mail?
I'm running from a simple 'git clone' of the master.

In any case, it seems that the cloud was in fact started, because I
can now do:

./bin/cloud-list
*** Listing cloud hello_world
****** Active instances
master 174.129.183.90 i-70187719

Trying to ssh to the instance first revealed a problem with the
permissions of the keypair file:

~/poolparty$ ./bin/cloud-ssh
master 174.129.183.90 i-70187719
Warning: Permanently added '174.129.183.90' (RSA) to the list of known
hosts.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for '/Users/emiltin/poolparty/keypair' are too open.
It is recommended that your private key files are NOT accessible by
others.
This private key will be ignored.
bad permissions: ignore key: /Users/emiltin/poolparty/keypair
ro...@174.129.183.90's password:

I changed the perm to 600 on the keyfile using 'chmod 600 keypair',
and tried again:
~/poolparty$ ./bin/cloud-ssh
master 174.129.183.90 i-70187719

At this point, os x pops up a dialog and ask me for the password for
the keyfile. I didn't set any, so here things go wrong, and I'm once
again asked for a password on the remove server:

ro...@174.129.183.90's password:

This is problably just a problem with the way I created the keyfile.

Shutting down - no problem:

~/poolparty$ ./bin/cloud-terminate
Shutting down i-70187719
~/poolparty$ ./bin/cloud-list
*** Listing cloud hello_world
****** Active instances

~/poolparty$

What's the best way to stay updated with poolparty - pulling from the
master?

Thanks!
Emil Tin

[Jørgen Orehøj Erichsen]

Mike,

The updated wiki page looks good!

Unfortunately, I am not able to run the hello world cloud-pool-thingie.

I did  

  ec2-add-keypair poolparty_keypair > ~/.ec2/id_rsa-poolparty_keypair

and for the keypair part in clouds.rb:

  keypair "/Users/joe/.ec2/poolparty_keypair"

But when I do a

  cloud-start -s clouds.rb 

I get

*** Starting cloud hello_world

0 running instances (1 - 1)

/opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.7/lib/EC2.rb:261:in `ec2_error?': The key pair 'id_rsa' does not exist (EC2::InvalidKeyPairNotFound)

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.7/lib/EC2.rb:199:in `make_request'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/1.8/net/http.rb:543:in `start'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.7/lib/EC2.rb:173:in `make_request'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.7/lib/EC2.rb:224:in `response_generator'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.7/lib/EC2/instances.rb:108:in `run_instances'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/../lib/poolparty/net/remoter_bases/ec2/ec2.rb:42:in `launch_new_instance!'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/../lib/poolparty/net/remoter_base.rb:51:in `launch_new_instance!'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/../lib/poolparty/poolparty/cloud.rb:55:in `send'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/../lib/poolparty/poolparty/cloud.rb:55:in `method_missing'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/../lib/poolparty/net/remoter/cloud_control.rb:9:in `launch_instance!'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/cloud-start:14

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/cloud-start:9:in `each'

        from /opt/ruby-enterprise-1.8.6-20090201/lib/ruby/gems/1.8/gems/poolparty-1.1.3/bin/cloud-start:9

        from /opt/ruby-enterprise-1.8.6-20090201/bin/cloud-start:19:in `load'

        from /opt/ruby-enterprise-1.8.6-20090201/bin/cloud-start:19

Does it look into my .ssh directory or why does it complain about id_rsa?

Hope I can get this thing going so I can start helping out Emil.

Best,

Jørgen

[Ari Lerner]

See below: (inline comments)

On Apr 15, 2009, at 3:40 AM, Emil Tin wrote:

>
> Hi,
>
> Thanks for updating the wiki. I gave it another try. Here's what
> happened.
>
> I created the ec2 keypair manually using the ec2-add-keypair, and
> updated clouds.rb to point to the new keypair file.
>
> When starting the cloud I now got a bit further, but got this error:
>

Make sure you have the latest PoolParty.

Yup, cloud start will do three things: start, provision and configure.
It is not a transaction, so if one succeeds and the next fails, it's
the next step taht fails. It looks like from above it started, but
didn't provision. You can type:

cloud provision

to try again from a failed provision cloud

>
>
> Trying to ssh to the instance first revealed a problem with the
> permissions of the keypair file:
>
> ~/poolparty$ ./bin/cloud-ssh
> master 174.129.183.90 i-70187719
> Warning: Permanently added '174.129.183.90' (RSA) to the list of known
> hosts.
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ WARNING: UNPROTECTED PRIVATE KEY FILE! @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> Permissions 0644 for '/Users/emiltin/poolparty/keypair' are too open.
> It is recommended that your private key files are NOT accessible by
> others.
> This private key will be ignored.
> bad permissions: ignore key: /Users/emiltin/poolparty/keypair
> ro...@174.129.183.90's password:
>
>

You have to chmod 600 the file to use it as you've done below.

> I changed the perm to 600 on the keyfile using 'chmod 600 keypair',
> and tried again:
> ~/poolparty$ ./bin/cloud-ssh
> master 174.129.183.90 i-70187719
>
> At this point, os x pops up a dialog and ask me for the password for
> the keyfile. I didn't set any, so here things go wrong, and I'm once
> again asked for a password on the remove server:
>
> ro...@174.129.183.90's password:
>
> This is problably just a problem with the way I created the keyfile.
>
>
>
> Shutting down - no problem:
>
> ~/poolparty$ ./bin/cloud-terminate
> Shutting down i-70187719
> ~/poolparty$ ./bin/cloud-list
> *** Listing cloud hello_world
> ****** Active instances
>
> ~/poolparty$
>
>
> What's the best way to stay updated with poolparty - pulling from the
> master?
>
>

I'd say stick with the gem, we release the gem periodically to stay
current with the latest working poolparty code, however if it doesn't
work, it's probably a setup issue which we are available usually at
all odd hours on IRC. #poolpartyrb @ irc.freenode.net

Thanks!
Ari Lerner

[Ari Lerner]

On Apr 15, 2009, at 1:50 AM, Jørgen Orehøj Erichsen wrote:

> Mike,
>
> The updated wiki page looks good!
>
> Unfortunately, I am not able to run the hello world cloud-pool-
> thingie.
>

Which hello world clouds.rb? On the site?

> I did
> ec2-add-keypair poolparty_keypair > ~/.ec2/id_rsa-poolparty_keypair
>

Make sure you chmod 600 on it.

> and for the keypair part in clouds.rb:
> keypair "/Users/joe/.ec2/poolparty_keypair"
>

This needs to either be a full path to the file or a full name. In
your case, you can just give it the full name as it's in a filepath PP
expects it to be:

keypair "id_rsa-poolparty_keypair"

It looks into your ~/.ssh directory because it can't find the keypair
you gave it above. It no longer looks for a prepended/appended name of
the file, as did 1.0. Hope this helps!

Ari

[Mike Wadhera]

As Ari said, you need to change access mode to 600 on your keypair
(will add this to the wiki)

To elaborate on the keypair error -- keypair
"/Users/joe/.ec2/poolparty_keypair" means you have a keypair
registered with amazon called "poolparty_keypair" saved to
/Users/joe/.ec2/poolparty_keypair -- remove the id-rsa- prefix & it
should work

[Emil Tin]

also you might need to use 'sudo chmod 600' instead of just 'chmod
600'. this causes problems for me.

[Jørgen Orehøj Erichsen]

Hi,

Changing the access permissions to 600 and renaming the file did it.

So now I get:

cloud-ssh
master 75.101.243.204 i-ec137d85
Hello World!

Yiehaa - that's great! Thanks guys.

/Jørgen

[koso...@gmail.com]

I'm still having the keypair error with the latest version of
poolparty from the git repo.



*** Starting cloud hello_world
0 running instances (1 - 2)
/usr/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.8/lib/EC2.rb:261:in
`ec2_error?': The key pair 'poolpartykeypair' does not exist
(EC2::InvalidKeyPairNotFound)
from /usr/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.8/lib/
EC2.rb:199:in `make_request'
from /usr/lib/ruby/1.8/net/http.rb:543:in `start'
from /usr/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.8/lib/
EC2.rb:173:in `make_request'
from /usr/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.8/lib/
EC2.rb:224:in `response_generator'
from /usr/lib/ruby/gems/1.8/gems/grempe-amazon-ec2-0.3.8/lib/
EC2/instances.rb:108:in `run_instances'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/../lib/
poolparty/net/remoter_bases/ec2/ec2.rb:42:in `launch_new_instance!'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/../lib/
poolparty/net/remoter_base.rb:83:in `launch_instance!'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/../lib/
poolparty/net/remoter_base.rb:97:in `launch_instance!'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/../lib/
poolparty/poolparty/cloud.rb:55:in `send'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/../lib/
poolparty/poolparty/cloud.rb:55:in `method_missing'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/cloud-
start:14
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/cloud-
start:9:in `each'
from /usr/lib/ruby/gems/1.8/gems/poolparty-1.1.5/bin/cloud-
start:9
from /usr/bin/cloud-start:19:in `load'
from /usr/bin/cloud-start:19








On Apr 16, 10:55 pm, Jørgen Orehøj Erichsen

<jorgen.ore...@erichsen.net> wrote:
> Hi,
>
> Changing the access permissions to 600 and renaming the file did it.
>
> So now I get:
>
> cloud-ssh
> master  75.101.243.204  i-ec137d85
> Hello World!
>
> Yiehaa - that's great! Thanks guys.
>
> /Jørgen
>
> On Apr 17, 2009, at 3:37 , Mike Wadhera wrote:
>
>
>
> > As Ari said, you need to change access mode to 600 on your keypair
> > (will add this to the wiki)
>
> > To elaborate on the keypair error -- keypair
> > "/Users/joe/.ec2/poolparty_keypair" means you have a keypair
> > registered with amazon called "poolparty_keypair" saved to
> > /Users/joe/.ec2/poolparty_keypair -- remove the id-rsa- prefix & it
> > should work
>

[Ari Lerner]

That's an amazon ec2 error. Did you do:

ec2-add-keypair poolpartykeypair

and save the output?

Ari
#poolpartyrb

[koso...@gmail.com]

What do I use to create poolpartykeypair?

I see on the install page it says use this command.. "cloud add-
keypair" ... However.. The version of "cloud" command I have install
does not have that option.

To tell you the truth.. The docs are extremely confusing..

-brady

On Apr 21, 1:14 pm, Ari Lerner <email.ariler...@gmail.com> wrote:
> That's an amazon ec2 error. Did you do:
>
> ec2-add-keypair poolpartykeypair
>
> and save the output?
>
> Ari
> #poolpartyrb
>

[Ari Lerner]

We know. :(

We are having a community documentation push tomorrow afternoon for
just that reason. In fact, if you are interested, we'll be online in
#poolpartyrb/irc.freenode.net and probably using acrobat as a good
over the net collaboration. If you are in LA and are interested: http://wiki.github.com/auser/poolparty/documentation-hackathon
.

don't worry about cloud add-keypair, just use:

ec2-add-keypair poolpartykeypair

Hope that helps... we are also in the room pretty much always and if
not, there are a bunch of helpful people in there as well.
Thanks!
Ari Lerner