similar to: how many mongrel daemons to launch

There is a big difference if you are not running a pure rails site. I am doing auth apache-side because I serve static content, perl scripts via cgi and feed the mongrel pack from Apache. The REMOTE_USER variable value can be passed to rails using a technique described deep down in one of the informative pieces on the Mongrel website. Bill On Mon, 12 Mar 2007 17:54:07 -0700, Matte Edens wrote:

Hello everyone- I am considering using Mongrel and I have read this list pretty extensively. I know that the Apache/mod_proxy_balancer/mongrel approach is the preferred one right now, with Apache serving the static content via mod_rewrite and such. However, in my hardware arsenal, I already have an old and trusty LocalDirector, which I would be inclined to at least try first as a

Hi, I run a medium-sized website that uses mongrel/rails in the following configuration: -frontend reverse proxy to a cluster of 7 app servers -each app server runs apache 2.2 with mod_proxy_balancer that balancers the requests out into a mongrel cluster of 35 servers. -each mongrel is version 1.0.1 the mongrel cluster config looks like: port: "1620" environment: production address:

I recently moved an app. from lighttpd + fastcgi to apache 2.2 + mod_proxy_balancer + Mongrel. On lighttpd, I was using basic authentication with a configuration like this: auth.backend = "htpasswd" auth.backend.htpasswd.userfile = "/path/to/htpasswd" auth.require = ("/" => ("method" => "basic", "realm" => "My

Hi - I''ve got a pretty popular Rails app on a Mongrel cluster with Apache and mod_proxy_balancer. How do I decide how many Mongrel servers to put in the cluster? I don''t have stats for the number of requests hitting the server yet, but I should have that data soon. The server has 2GB of RAM and has to do a lot of work with RMagick, including generating and storing lots of

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

Thanks for the answer on server::start...that makes sense, just wanted to make sure I was not doing anything incorrectly. I am now running 3 mongrel servers as windows services (mongrel_cluster is not supported for windows). I have apache configured with with mod_proxy_balancer from the instructions at http://mongrel.rubyforge.org/docs/apache.html. I am able to access my app without a port

I''d like to implement output compression in Mongrel (ala Apache''s mod_deflate). I have found a Rails plugin that, with minor modification, works. Is there even an advantage to moving the output compression from the Rails app to a Mongrel handler? Unless, of course, someone knows how to configure mod_proxy_balancer with mod_deflate... == Will Green Web Developer & IT

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

Cheers, I''ve just published a blog post about scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel. This way you do not need another proxy server or load balancer for Mongrel. Just use Apache 2.2 and mod_proxy balancer. http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel Jonathan -- Jonathan Weiss

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

First off: Our clusters are LVS balanced Apache 2.2.3 + mod_proxy_balancer + gem mongrel 0.3.13.3 / mongrel_cluster 0.2 + memcached / gem memcache_client + gem rails 1.1.6 on debian boxen, and a pgcluster backend. On 2 of our deployed clusters, we are getting the "spinning mongrel" problem. As the clusters are very low volume right now, it takes days to collect a spinner, making it

Hi We''re running mongrel on CentOS 4.2 with Apache httpd 2.2 mod_proxy_balancer, mongrel_cluster-0.2.0, Rails 1.1.6, Ruby 1.8.4, Pg 8.1.4 backend. We are on the verge of going live with our site and I am stress testing the server. What we are seeing is under heavy loads, our mongrels will seg fault and die one by one. Following the advice in a previous thread (http://www.mail-

Is anyone using ferret with Mongrel/Mongrel-cluster? The first one or two times I access the ferret index it works fine, but then it throws a write lock error StandardError (: Error occured at <index_rw.c>:703 Error: exception 6 not handled: Could not obtain write lock when trying to write index ): I need to do more testing on this to narrow down the problem/solution but just wanted to

I am using Apache2.2 + mod_proxy_balancer + mongrel setup and my mongrel.conf file(for apache is like this) 2 3 <Proxy balancer://mongrel_cluster> 4 BalancerMember http://127.0.0.1:9000 5 BalancerMember http://127.0.0.1:9001 6 BalancerMember http://127.0.0.1:9002 7 </Proxy> 8 9 <VirtualHost *> 10 ServerAdmin rags at

I''m trying to do some initial benchmarking of our setup, mainly just to establish baselines. I''m essentially using the process Zed outlines in a previous message: http://rubyforge.org/pipermail/mongrel-users/2006-May/000200.html What I''m running into is that Mongrel appears only half as fast as Apache when serving a small static HTML file. If I then add in Apache with

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:

Hello, For some reason when i change the "environments" line in mongrel_cluster.yml to use production, ActiveRecord Sessions stop working. Changing this line to development yield the correct result. Entries in database.yml are correct, and confirmed that the sessions table exists in both environments and that production is indeed working (production.logbeing filled up). Any idea why

more info just 1 server webserver + appserver + dbserver On 9/14/07, Yan Meng <dreamwords at gmail.com> wrote: > > Hi, Guys > > Our team is running a web2.0 finance site in China > > http://www.caibangzi.com/ > > We use APACHE + mod_proxy_balancer + mongrel to deploy our application, it > workd super in the past few monthes. > > However, just from last

The company I work for is launching a new web site tomorrow. News of our launch will be published in major publications throughout the week so I want to make sure we are prepared for the load. Production Environment: HP Proliant server w/ 8GB RAM and dual AMD64 Opterons Memcache is used as the session and fragment store (512MB for it) MySQL is running on a seperate server in the same rack We use