similar to: Passing environment to mongrel apps

I have a ror project which has been productized. There are several web sites in one ror project I need to set an "enviroment variable" to run different sites, can I do that using mongrel? I tried to use mongrel''s -S option and set the enviroment variable in that file but it seems mongrel runs that file after it calls enviroment.rb I also used apache''s

Hello, I''m running mongrel behind apache via proxypass. Every now and then, a spammer tries to proxy traffic through apache, and for some reason, apache forwards the request to mongrel, even though it''s not a site being hosted by me. At times this seems to cause mongrel to become unresponsive, and all requests to the site then fail with a proxy error until mongrel is

Hi guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

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 posted this to the Ruby on Rails Talk group but I thought I''d post it here too as it''s probably a more appropriate group. Hope this is ok. I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

Anybody seen this message before? I see it over and over in one of my mongrel processes log files. I''ve never seen it before today. /usr/local/bin/mongrel_rails:16Mon May 14 20:44:30 +0000 2007: Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Mongrel timed out this thread: shutdown>Thread #<Thread:0x2ae6288dbc40 sleep> is too old, killing. Thanks, Pete

Hi guys, Does anyone know if mongrel has a built-in timeout for requests that take too long? If so, how do you increase it? I''ve found that some server requests are timing out. Complicated requests are already being farmed out to asynchronous processes. But some of the more basic requests are timing out when we have our peak server load in the mornings (the bottleneck is the

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

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

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

Is there anything mongrel cluster gives you that monit doesn''t? I''ll be using monit to monitor a number of other services anyways, so it seems logical to just use it for everything including mongrel. Chris

Hello, I''ve been trying (unsuccessfully) to hack my mongrel_cluster to re-ststart in an alternating manner. Specifically, this soluiton: http://blog.carlmercier.com/2007/09/07/a-better-approach-to-restarting-a-mongrel-cluster/#content Which means I an call to mongrel_rails cluster::restart to do this: mongrel_rails start 8001 mongrel_rails stop 8001 mongrel_rails start 8002

All, I''m wanting to initialize an ActiveRecord object. I understand that there is a method called after_initialize that appears to get called right after the ActiveRecord object is instantiated. Is after_initialize a Ruby thing or a Rails thing? Where is after_initialize documented? Can I pass parameters to it? If so, how? I want to initialize the "belongs_to" attribute of

All, I have a quick question - is the purpose of implementing after_initialize to allow custom attribute initialization for AR descendants? I have been overriding initialize whenever I require custom setup of my model classes, like so: def initialize(attributes = nil) super self.Status = ''G'' end So I have a couple of questions: 1) Could I achieve the same

Hi y''all; A quick note to announce the release of mongrel_cluster, a gem_plugin for Mongrel. This plugin provides commands for managing multiple Mongrel processes behind a reverse-proxy server and load balancer. To install: gem install mongrel_cluster Configure (use -h to options): mongrel_rails cluster::configure Start: mongrel_rails cluster::start I''ve posted a quick

Hi list, I have a problem with Mongrel which is really bugging me. I would really appreciate any help that anyone can provide to help me in solving this problem. 1. My setup: Apache front_end with mod_proxy_balancer in front of 4 mongrel/rails instances of my application. Rails 1.2.5 Ruby 1.8.6 Mongrel 1.1.1 2. I noticed that the CPU consumption on my server was 100% being consumed by ruby so I

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

Hi, I''m doing development with Mongrel 1.0.1 on Ruby 1.8.4 / OS X 10.4.10, and I''ve found that often when I shut down my server with ^C, it hangs for a while, gobbling up all CPU. Sometimes it stops after a few seconds, sometimes it''s run for several minutes at least. This happens across all the apps I develop on, but it seems to hang longer after

I''ve done a clean install of Ubuntu 7.04 server in 2 different machines and everytime I reboot the machine or manually run /etc/ init.d/mongrel_cluster restart/start the mongrels won''t start correctly. I have to manually start them by using mongrel_rails cluster::start from each app folder. I''ve been searching around and it looks like mongrel has some problems