deploy: mongrel cluster problem

Hello, I don't know if this is really the right forum to be asking about Rails deployment, but just in case someone has experience with this...

I'm attempting to deploy a rails site for the first time, using mongrel, mongrel clusters, and capistrano. So far, I have been able to deploy the files to the site and start up the mongrel server, viewing the files on port 3000.

The problem happens when I go to fire up the clusters. From the command line, they appear to be running fine, showing up when I do a 'ps aux | grep mongrel'. But when I try to view in a browser, they don't show up.

I have add to my httpd.conf file to look like this:

<VirtualHost *:80> ServerName dev.mydomain.com ServerAlias dev.mydomain.com DocumentRoot /var/www/html/dev/mydomain/current/public ProxyPass / http://127.0.0.1:80 ProxyPassReverse / http://127.0.0.1:8000 ProxyPreserveHost on </VirtualHost>

The symlink setup by Capistrano works, so I don't think it's that.

One strange thing: At one point, the files were visible on the 8000-80003 ports, but I noticed they were pointing to a specific cap release. Once that release was cleaned up from the subsequent file releases, the pages broke. I only mention this because, although I've redone the cap setup, I wonder if this is a related issue that still remains.

fyi, here are some of the reference i'm using: mongrel.rubyforge.org/docs/mongrel_cluster.html mongrel.rubyforge.org/docs/apache.html capify.com peepcode.com

I'm really new to to rails deployment, so any thoughts/feedback are appreciated.

Hello, I don't know if this is really the right forum to be asking about Rails deployment, but just in case someone has experience with this...

I'm not sure about the answer to your question (I only know enough about apache to do stuff with our setup, which is a little different and uses mod_proxy_balancer) but thought I'd point out that there's a special rails-deployment list. In the spirit of checking the obvious, what does your mongrel_cluster.yml file say ?

Fred

Thanks for the response. the yml looks like this:

user: mongrel cwd: /var/www/html/dev/mydomain/current log_file: log/mongrel.log port: "8000" environment: production group: mongrel address: 127.0.0.1 pid_file: tmp/pids/mongrel/pid servers: 2

I'm still trying to retrace my steps of why it's there, but I also have a yml file in my etc/mongrel_cluster/ directory titled <domain>.yml with the same config.

raph

I'm not an expert by any means but shouldn't this line

pid_file: tmp/pids/mongrel/pid

be

pid_file: tmp/pids/mongrel.pid

The file in /etc/mongrel_cluster should be a symbolic link to the mongrel_cluster.yml file in your config dir. I'm also using mod_proxy_balancer for several production sites and I would recommend you check that option out.