similar to: mongrel cluster prefix question

I''m playing with the mongrel clustering, and am having a problem getting 2 mongrels to start up reliably. This should be a pretty simple cluster, with just 2 instances running. My mongrel config (mongrel_cluster.yml) looks like: cwd: /deployment/installed/myapp/current log_file: log/mongrel.log port: "8000" environment: production address: 127.0.0.1 pid_file:

Hi all I got a vps setup amazingly fast using the deprec recipes on Ubuntu edgy, but now I''m having a minor issue where my site loads for the main domain when I only want it accessible from the subdomain. This is a pretty typical setup, apache 2.2.3 -> mongrel_proxy_balancer -> mongrel cluster. I''m sure I''m missing something obvious in the config... I have the

Hello, I am trying to deploy on to OS X Server with capistrano+mongrel+apache2, etc. I''m trying to do a "cap cold_deploy" as recommended here: http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ I had a devil of a time getting cap to find the mongrel_rails command (which is in /opt/local/bin) on the server. I set the

Hello all After installing Mongrel, Mongrel Cluster and all it''s dependencies via gems under FreeBSD. Next I have configured all config/mongrel_cluster.yml for each Rails app, then: % mkdir /usr/local/etc/mongrel_cluster and likend each railsapp.yml to it''s refering app/config/mongrel_cluster.yml My question is, after preparing all base configs now I need to add some rc.d

Hi all, I am out of my head here... I have a 3 node cluster with 10 mongrels running on each. When I deploy, I break all the mongrels every time. I have tried just about everything. I can restart my mongrels without a hitch manually, it''s only when I use cap deploy. Maybe I am missing something here... so if I can get some help it would be appreciated. The errors are the typical mongrel

hey all, I''m trying to do a mongrel_cluster+apache2 config. this is my testapp.conf: <VirtualHost *:80> Include /etc/apache2/conf.d/testapp.common # ErrorLog logs/testapp_errors_log # CustomLog logs/testapp_log combined </VirtualHost> this is my testapp.common: ServerName myapp.com DocumentRoot /home/patcito/testapp/public/ <Directory

I just created a test rails app, and am having very wierd issues with mongrel cluster. Here''s what I''m doing: rails test sudo chown -R mongrel:mongrel test cd test sudo mongrel_rails \ cluster::configure -e production \ -p 8000 -N 3 -a 127.0.0.1 --user mongrel \ --group mongrel It correctly writes the mongrel_cluster.yml file to the config directory. Now,

I posted this to the rails list before by mistake, and only later realized that there is a specific mongrel list. Uff, I got lost. I had mongrel_cluster 0.1working fine, even with capistrano (my own hack). Then came mongrel_cluster 0.1.1 and I tried to set it up, but somehow I messed up things and nothing worked anymore. So here is what I did: on production machine: (debian linux, rails 1.1)

I have installed mongrel and mongrel_cluster fine and have them running great with my app. I tried using the init.d script provided with mongrel_cluster 2.1 to start it up on boot but it doesn''t. mongrel_cluster_ctl works fine for me by hand and so does /etc/init.d./mongrel_cluster start. I am on Debian so I installed the service links with sudo update-rc.d mongrel_cluster defaults. And

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

Hi, I''m running CentOS 4.3 and the latest Mongrel (0.3.13.3) and mongrel_cluster (0.2.0). I have set up a cluster, following the instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I created a symbolic link in the directory /etc/mongrel_cluster . When I run mongrel_rails cluster::start -c test.yml, the mongrel servers start up. But at boot, the command

I?m knew to rewrites on apache in combination with mongrelcluster. It?s urgend for me, because the server has an loadaverage about 10 :-((((( Ok so I?m using 3 mongrel-server on an mongrelcluster. The Loadbalancer ist apache I think, that my rewrites are not correct. Please can anybody check my rewrites ? That?s in my /etc/apache2/conf.d/rails.proxy_cluster.conf <Proxy

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

I''m in the process of setting up a mongrel cluster at the moment, and I''m running into a bit of an issue. Even worse is that I''m not sure whether this is a mongrel thing, or an Apache thing. While I''m inclined to think that this might be a balancer thing, I decided there was a higher chance hearing back from mongrel-users than from apache-users, so I''d

I''m currently working on 4 different RoR apps all using mongrel cluster and each with their own config file in /etc/mongrel_cluster. I would like the ability to stop|start|restart a single app. Anyone working on something like this? I''d be happy to code it up and contribute this if there''s a need. Basically I would like this: sudo /etc/init.d/mongrel_cluster restart

Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file

I wanted to show a Rails site to someone so I set up Mongrel and it ran fine, This is my mongrel_cluster.yml, port: ?80" environment: production pid_file: log/mongrel.pid servers: 4 Now, after going back to Apache/Tomcat I can''t get the Mongrel site up and running again...? Any suggestions? (When I run Mongrel, I stop Apache first) Jim

Hi, I''ve configured mongrel_clusters behind an Apache 2.2 proxy using named virtual host. Session are saved as ActiveRecordSession. But the cookies created on client side doesn''t correspond to session data saved in database (keys are different). The RoR app react just like it doesn''t have a session at all. If I don''t use Apache as a proxy/load balancer

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212