HostingRails.com

One other quick question:

I'm following the tutorial on setting up a mongrel cluster, and have gotten to the part where I edit the crontab.  I guess since I'm on a dedicated server, it already has some mysterious stuff in it.  Should I not edit the file, append what I need to add to the end of it, or just replace it altogether?

Hi - On your server you need to configure the Mongrel as the  user and not as root. Please login to the server as a user and try starting the mongrel.

Also regarding the Crontab - you need to log to the server as the user to set it up

As root you can list the crontab of the user using the command

crontab -l -u <username>

And edit the crontab using the command

crontab -e -u <username>

I did configure the mongrel as the user and not the root, but I did it again to make sure.  What I did now was log in as root, then tried 'ps aux | grep ruby', and it showed two mongrel processes already running under root.  I assume these were the two processes serving content while the user Mongrel processes were not running.  So, I killed them.  Then I su'd into the user and did mongrel_rails cluster::start, and the user Mongrel processes started right up.  So now the only Mongrel processes running are those of the user.  Now, however, navigating to my IP gives a 503 Service Temporarily Unavailable error.  So it seems that the IP is somehow linking to an expected root Mongrel cluster instead of the user one.  How do I fix this?

Hi - Now you need to change port numbers in your apache configuration file. Open the file

/usr/local/apache/conf/userdata/std/2/<username>/<domain-name>/custom.conf

In this file you will be able to see entires like

BalancerMember http://127.0.0.1:4****

There you need to add more entires following the same pattern. (for each mongrel) Make sure to replace the **** with the correct port numbers. Restart apache after making the changes

Please let us know if you need any further assistance on this.

Hi again,

I added the two additional processes to the file and restarted apache.  I'm still getting a 503 at http://208.101.54.41/.  The four Mongrel processes are running under the user.

Hi - The port numbers were not correctly configured in the custom.conf. I have made the required changes and the site seems to loading fine now. Please verify,

Thanks for your help.  If you remember, what was wrong in the config file?

Hi - The Port numbers mentioned were wrong. You had given 4000 instead of 40000.

Rats, I was sure I had those right.  Thanks again!