similar to: layout not seen by some clustered mongrel instances

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

I have developed a rails application for my company. It will be used by upto 3o people at a time. I have just read that Mongrel will only process 1 request at a time (rails is only in 1 controller at a time). Does this mean that to get good performance i need to run mongrel many times on different ports? How many different instances of mongrel is recommended? If this is true then it

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

I have a Apache proxying to a number of Mongrel''s on different physical machines. What I need to do next is share files between the Rails instances. I am creating dynamic files which will be created by Rails and stored on disk. The file is then recovered and served at a later date by an ajax request. But because of the proxying the ajax call my be routed to a different machine.

Hi everyone, I would like to know if there''s a way to synchronize the actions in a mongrel cluster. Basically, how do I make sure that a specific controller action gets executed by only one mongrel server at one time? I obviously cannot use Mutex::synchronize, because we''re talking about different processes. I looked into using optimistic and pessimistic locking. I

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

Hi,will appreciate any advice from ruby guru : I found strange behavior on mongrel cluster. Below are my installation details : #ruby -v ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-linux] #rails -v Rails 2.3.5 I use mongrel cluster 1.0.5 on Debian lenny (5.0). Also got the same problem in ubuntu 8 LTS, with similar config. when running just mongrel , it works properly. But when I tried to use

Just so you know, I''ve read the manual :) http://mongrel.rubyforge.org/docs/choosing_deployment.html No php or ssl needed - that is me - simple. So I should be good to go but thought I''d ask. BTW, sorry about the stupid subject. Listening to BNL, you know ;) On 6/27/06, mongrel-users-request at rubyforge.org <mongrel-users-request at rubyforge.org> wrote: > Send

Hi folks. Using mongrel_rails and the mongrel_cluster capistrano recipes, I often encounter a situation where some of the mongrel processes don''t die in time to be restarted. The output of capistrano will tell me something like "mongrel on port 8001 is already up", but that''s only because capistrano/mongrel_rails failed to take it down in the first place. The solution

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

Hello Folks, This is the big release of Mongrel that''s been in the works for a while now (well, like a week). It is chock full of changes and features, but mostly it syncs up the Win32 side of things, and validates that Edge Rails works without problems. It also features a more extensive and useful example of the GemPlugins called mongrel_config. First the usual stuff for people

Hello all, I''m attempting to test/tune a mongrel cluster according to the tuning instructions on the mongrel site (using httperf). Anecdotally, the site itself ''feels'' snappy, but testing it with httperf reveals what appears to be terrible throughput. I''m kind of at a loss to describe the results, and was hoping someone could verify that I''m testing

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 have a two instance mongrel cluster, running behind apache mod_proxy_balancer on a linux VPS. Mongrel_cluster is 1.01, mongrel is v1.02, rails 1.2.3, ruby 1.8.6. I seem to have enough memory. About 2 minutes after I start the cluster, one of my instances dies - it could be either one. The log file indicates that it received a TERM signal. The instance does die cleanly, removing its pid

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 have been running a proxied mongrel-hosted app behind apache 2.0 (don''t need clustering) for several months, and loving it. In that instance, I am proxying the root of the virtual host to mongrel. I am now in a situation where I need to proxy a directory name to mongrel for a new application, and not having any success. I saw Zed''s mention of the --prefix option in 0.3.13.4,

Hello all, So, I''ve been using monit with mongrel for a while now, since the 0.3.x days (I think it was). It used to work fine, but now I seem to be having some trouble. I''m currently using mongrel 1.0.1 and I am using the same monit configuration I''ve always been using, yet everytime monit should restart mongrel, I get "Execution failed". For the start

I''m trying to understand the ''Big Picture'' of how Ruby on Rails applications are deployed and operate in distributed environment (one deployment server, many remote servers). I follow AWD by Dave Thomas'' explanation from pages 624-626. From reading these pages I have these questions; 1. How does the RonR instance on the ''remote'' server gain

Hello All Mongrel Users, For the unintiated, Mongrel is a web server that runs Ruby web applications really fast. Read http://mongrel.rubyforge.org/ to get find out more about it. This is the Iron Mongrel release. It is the result of trying to trash Mongrel until it can''t move and then fixing anything that comes up. The work was done on EastMedia''s and VeriSign''s

hi all, i''m working on deploying my app w/ apache and a mongrel cluster. i''ve started by copying the instructions and code from the agile rails book and everything seems to be working fine but apache isn''t forwarding my requests to mongrel the way i expect it should. there''s nothing in the rewrite logs and nothing but 404 errors in the apache error logs.