HostingRails.com

503 Error - Service Temporarily Unavailable

This is a wiki article created by HostingRails users. Please login or signup to make edits.

If you're seeing this error message then it means your Mongrel server or Mongrel cluster is down.  YOU need to get it up - this is not support's problem (although they'd be glad to assist you if you need help).  

To get it back up:

1) SSH in your account

2) cd /path/to/your/rails/app

3) issue your

mongrel_rails start -p <your_port> -e production -d

or

mongrel_rails cluster::start

4) If that doesn't work, your mongrel.pid files are likely still in your log/ folder.  You need to clear those out

cd /path/to/your/rails/app/log 
rm mongrel.log

if you're running a cluster you'll need to clear out all the mongrel.4XXXX.pid files

5) On very strange and bizarre situations you'll get your mongrel(s) up and then you won't be able to stop them.  If this is the case issue 'ps' in your account and note the process IDs of your mongrel_rails processes.  You'll then need to manually 'kill -9 <pid>' those guys and then you can start up your mongrel(s).  


NOTE: mongrel_rails cluster commands do not work in your crontab!  You need to act like you have a bunch of single mongrels (which, if you think about it, you do) so only the "mongrel_rails start -p <your_port> -e production -d" bits will work there.