similar to: Apache Load Balancer Manager With Mongrel

Had to make a couple of changes to the config from the mongrel site to get the load balancer manager working: changed # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] to # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME}

Posted this on rubyforge, thought I would put it here at as well. I just started playing around with mongrel. I am currently using apache + fastcgi. I am running a windows box and I followed the directions at http://mongrel.rubyforge.org/docs/win32.html. I am able to install the service fine and also start the service from the windows service control panel. However, when I try to start the

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

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

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

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

Our group has several web apps developed in ColdFusion, PHP, and Rails. The ColdFusion and PHP apps are on an older server, and the Rails apps on a new server. Ideally, we''d like them all to share the same server. Our current setup for the Rails server is Apache2.2 with mod_proxy_balancer and mongrel_cluster. We''d like to have specific directories be processed and served by

Hi I just setup a server (Apache 2.2, mod_proxy_balancer, mongrel_cluster) with 2 Rails applications according to this excellent Post: http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you Everythings works great, but after a long inactive period (say one night), the first 3 connections allways get an Error 500 Excerpt from production.log: ...

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

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:

I followed the tutorial from Coda Hale[1] on setting up Mongrel/Mongrel_cluster and Apache to move away from my current Apache+FastCGI setup. The mongrels are all working fine, and Apache is proxying all dynamic requests through to the cluster using proxy balance. Strange thing is now, that all my images in public/images aren''t loading at all, if I access them directly I just get a

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 newbie to mongrel, I''m not able to config mongrel_cluster in order to host multiple web sites added/remove as apache VirtualHost. I followed codahale http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ mixed with Wiki Radiant (I use Radiant as a rails apps to be deployed, 1 domain 1 radiant sites with its own document tree

Hi all, I''ve been spending quite a lot of time trying to install a decent RoR server on my dedicated server (Ubuntu 6.06 LTS), and now, everything works. However, the performances are not really what I had expected... I would like to know what you think about it. Here is my config: 2GHz VIA proc, 1Gb RAM, SATA-II HD. I have apt-got ruby 1.8.4, mysql5 and installed rails 1.1.4 by

Hey guys, Ok, basically I coded a ruby on rails CMS to manage a bunch of media files. I am finding that a lot of people are "hot linking" to these media files and would like to prevent this to save bandwidth. Usually in the past, it hasn''t been a problem, I would add something like the following to my .htaccess file RewriteEngine on RewriteCond %{HTTP_REFERER} !^$

Hi all, I encounter timeout errors during file uploads in my Rails application. I think the problem may be in the Mongrel configuration. Here is my setup: * Load balancer (Cisco CSM, my provider''s Catalyst 6509) * Apache 2.2.3 with mod_proxy_balancer * Mongrel 0.3.13.3 * Rails 1.1.6 * Ruby 1.8.4 * MySQL 5.0.22 * file_column I host an application in which users may upload medium files

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 have an Apache2.2 SSL setup with vhosts on my server with fastCGI running several applications. The applications all work except IE hangs any time the network traffic isn''t perfect. I have very few problems with firefox. When I run native Mongrel on a port and point the browser to that port it runs much much better. When I try pointing Apache to that port either using ProxyPass or

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

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: