similar to: Do I really need a cluster?

Hi, I''ve started a new project that uses Mongrel. It basically lets you defer requests to it until other Mongrels in your (Rails) pool becomes free. Rubyforge project page: http://rubyforge.org/projects/qrp/ gems, tarballs and git repo in case they haven''t hit the mirrors yet: http://bogomips.org/ruby/ I should also add that nginx 0.6.7 or later is required for the

Hi mongrelians, I found myself with an unloaded full production server recently which presented an opportunity to run some performance tests against Mongrel and nginx. I thought this list might have some interest in the results of my tinkering! I actually ran two sets of studies, and Wayne Seguin kindly provided a lot of guidance and support in getting them running. Thanks Wayne! Also,

Hi All, I am new to the mongrel mailing list and I have a question (and I didn''t find any answer in the archives). I have successfully installed the apache2.2 proxy balancer with mongrel cluster and that works just fine. For a single rails app I have started 2 mongrels which consume about 100M (ps says 5.0% for each and I have 1G RAM). It seems a bit much but OK. However that would

Hi everybody, I have installed mongrel and mongrel cluster in a new linux box .... at the end of the day I was able to lunch mongrel (mongrel_rails start -e production) and all is working fine with. However, when I tried to set a mongrel cluster the command mongrel_rails cluster::start get the following output : starting port 8000 starting port 8001 starting port 8002 But when I lunched the

On 10/23/07, Robert Mela <rob at robmela.com> wrote: > Several years back I accidentally discovered that multiple processes can > listen on the same TCP/IP socket. The trick of course is that all the > processes are in the same process group, and the socket is opened by a > shared parent. The OS somehow was managing queuing up the various > calls to accept() on that

Hi, I have a ruby on rails website. Server configuration is: 1. Nginx 2. 4 mongrel clusters running on different ports. After a long idle time few of the mongrel clusters stops responding. I have set "ActiveRecord::Base.verification_timeout = 14400" in environment.rb file, but still it''s not working. On executing "lsof -i -P | grep CLOSE_WAIT" command, I usually

This may be a nginx issue more than a mongrel one but I though folks in this list might be interested. Anyway, I have a mongrel_cluster with 2 front nginx workers as proxy. I recently replaced apache/mod_proxy for nginx, and I wasn''t aware of the 60 seconds default proxy_read_timeout so I went a head and tried to run a process via http GET. Normally because of the 60 seconds the GET I

Hello! Today I''m announcing a "soft but official" release of Mongrel 0.3.13.4 for the Unix fans in the crowd. It''s been running stable for quite some time now for many people, and should be great for nearly everyone. You can read the announce at: http://mongrel.rubyforge.org/ This release includes new versions of mongrel_upload_progress and mongrel_cluster.

Hello list. I''ve (hopefully) gotten nginx and mongrel up and running, and copied the startup script found on http://reductivelabs.com/trac/puppet/wiki/UsingMongrelPound to enable starting puppetmaster by issuing "mongrel_puppetmaster 18140". This makes sure that mongrel i started. But how do I make sure nginx is automatically started? As of now I manually issue the

Hi all, We use mongrel behind apache (using mod_proxy_balancer) to run an internal app for our business. Lately we''ve been seeing frequent errors from some of our mongrel processes. [Sun Dec 16 08:48:47 2007] [error] [client <CLIENT1>] (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1, referer:

Does anyone know whether the mongrel upload progress plugin works with nginx? It works fine for my app under pound, but not with nginx. I am using DRb to handle the uploads as detailed at http://mongrel.rubyforge.org/docs/upload_progress.html . If I am using pound I can see the uploads with irb -r lib/upload_client.rb , but cannot if I am using nginx. Does anyone know anything more about this

We have a development environment that every morning requires a restart because Mongrel just stops responding. I noticed this older thread...but I still experience the problem http://rubyforge.org/pipermail/mongrel-users/2006-August/000950.html We are running nginx..but I also have the mongrel ports open to our IPs..both going through nginx proxy and directly through mongrel fails...then

Folks- James Cox, Alexy Kovyrin and I all huddled up and got nginx working perfectly with mongrel cluster and rails page caching. So all static and cached files are served fast by nginx and anything not static gets sent to mongrel. http://brainspl.at/articles/2006/09/12/new-nginx-conf-with-rails-caching Cheers- -Ezra

Hey All, This is probably a gotcha of some kind. That is to say I''ve missed a configuration somewhere. I''ve recently moved over to using mongrel as the puppet server type and having nginx proxy to one of four mongrel instances. What I''m seeing though is that when I try to run a new node (one that has been created post moving to mongrel/nginx) is that it returns with the

Hi, I could never find out what''s the difference between nginx and mongrel. All my searches say "nginx is a HTTP server ..." and "Mongrel is a fast HTTP library and server for Ruby....". For me they both mean "...HTTP server...". I kept up with this question for some time till I came across this santence from the guys at Friend for Sale: -----------------

Hi, I''ve created two Nginx patches (see at the end of this message) to allow a simpler Nginx configuration for your Mongrel puppetmasters. The two main issues with Nginx in front of puppet were: * no CRL support * no optional certificate verification (and thus we''re forced to have two separate configs on two different ports, and to use --ca_port). Now, it is as simple as

Has anybody had any luck getting Cucumber, Webrat and Selenium to play nicely together for SSL sites? My test environment: - nginx front-end accepting SSL requests, proxying them to mongrel back-end - mongrel back-end accepting normal HTTP requests - application routes configured with ":protocol => ''https''" so that URLs generated with "_url"

You may have heard of Slowloris and Nkiller2 (if not check them out), but there is also david: http://git.bogomips.org/cgit/david.git I wasn''t comfortable with announcing this two years ago when I wrote it. I''m OK now since Slowloris and Nkiller2 are similar (ok, Nkiller2 is lower-level and meaner) and attacks of this type should be well-known by now. I''m sure some

Hi, I want to optimize my home page load as long as a user is not logged in. I currently use Rails fragment caching but still, I want to avoid going to Rails if the user is not logged in because the page to be rendered is really just static. I can''t use page caching really because I can''t apply any logic as that would require going to Rails. Could I use a cookie that gets

Thanks Bill for the answer ! In fact, my application is working well with webrick and also with a single mongrel instance lunched via the command : mongrel_rails start When I check what is the difference in the gem loaded in both cases (mongrel_rails start and mongrel_rails cluster::start) it seems that mongrel_rails cluster::start does not load all the gems that the first command is loading. So