-
Notifications
You must be signed in to change notification settings - Fork 54
Troubleshooting
You can find help on this page, in the google groups
and on IRC channel #poolpartyrb at irc.freenode.net.
Please include pointers to gists for the following in order to quickly resolve problems.
- Clouds.rb
- Gem versions (output of “git list”)
- Trace of the error
Please also check the open issues to see if it has already been fixed or being worked on. Leave a comment.
Errors belong to four broad classes:
- EC2 deployment
- Specific deployment setup (clouds.rb)
- Specific gems/modules on which PoolParty is dependent on
- PoolParty itself
See the EC2 AMI Tools for setup and testing.
You should be able to run
ec2-describe-instancesand see
RESERVATION r-d6188cbf 148400002807 default INSTANCE i-83ea9fea ami-7cfd1a15 ec2-67-202-20-159.compute-1.amazonaws.com domU-12-31-38-01-D1-21.compute-1.internal running app 0m1.small 2009-04-29T16:43:02+0000 us-east-1a aki-a71cf9ce ari-a51cf9ccThere is no easy way to detect this except from the errors that are shown. Make sure that the trace, sequence of commands, clouds.rb are all included. If you are using chef recipes, make sure that it is not a Chef related issue. Most Chef recipes can be independently tested and verified.
PoolParty is under active development. Make sure that your source is the latest. To install the latest version:
git clone git://github.com/auser/poolparty.git cd poolparty rake poolparty:vendor:setup rake poolparty:vendor:update rake build rake installThe above process builds and gem and installs it. If you are having gem building problems
cd poolparty rake gemspec:generate rake buildPoolParty is under active development. There are many bugs are that are being ironed out. Please follow the directions above so that problems can be speedily solved.
If you have a fix, the preferred way is to fork the repository
make the modifications and let the core developers know the repository and branch. They will be happy
to incorporate the code in.