Troubleshooting

Introduction

We all love AppScale, but like all software, it once in a while has problems. This post outlines what to do when you run into a problem with AppScale, how to debug it, and how to fix it. Of course, you can always ask us for help on IRC (#appscale on freenode.net).

AppScale didn't come up successfully

If you ran "appscale up" to start AppScale and it didn't start, it could have failed for any of the following reasons:

• (VirtualBox) AppScale hung at "Please wait for AppScale to start your machines."
• (EC2) You're using Spot Instances but AppScale is hung at "Waiting for machines to become available."
• (Eucalyptus) AppScale hung at "Waiting for machines to become available."

Let's look at each of these individually.

AppScale on VirtualBox

AppScale on EC2

AppScale on Eucalyptus

Forcefully cleaning up AppScale state

Log into all nodes and run the following:

ruby /root/appscale/AppController/terminate.rb

You can ignore any of the output of this script. Then verify that no Python, Java, or Ruby processes are running. You may have to set "force : True" in your AppScalefile to tell the AppScale Tools to ignore any local state on the machine you ran the tools from.