similar to: Shared listening sockets

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

Rails instances themselves are almost always single-threaded, whereas Mongrel, and it''s acceptor, are multithreaded. In a situation with long-running Rails pages this presents a problem for mod_proxy_balancer. If num_processors is greater than 1 ( default: 950 ), then Mongrel will gladly accept incoming requests and queue them if its rails instance is currently busy. So even

Jeff try adding to your mongrel_cluster.yml :docroot: /var/radiant/domainA.com/public -- Together we can solve any issue.

Most of my machines have apache+mongrel running but the mongrels are using the localhost. In my production environment, I have 4 boxes. I have setup 2 http servers ( apache 2.2.4 ) and 2 app servers. They are currently using lighttpd+fastcgi. Which I am changing this week. I want to get advice from you guys before I actually do this since this is my production env. I have installed apache on the

I tried a bunch of tools and ended up using Jakarta J-Meter b/c it works cross-platform (Unix/Windows in my situation) and has a gui which shallows the learning curve. I''ve been quite satisfied with it.. Search the archives on this list and you should be able to find some great info Zed and others wrote a while back on How to Load Test Correctly. I found that series of posts to be

Hi, I''ve configured a rails application on my VPS to run on two mongrels. When I run curl on localhost, the starting page comes up fine. That is, mongrel is serving the app perfectly. The problem arises when trying to access the app on my ip through apache. I get a 403 error. Just to test things out, I''ve set generous permissions on the entire rails directory structure

I just finished updating our internal site, which hosts multiple Rails apps, to Apache 2.2.3. It also has a TWiki rewritten into the root, ViewVC mounted on /cvs, and /server-status and /server-info. <VirtualHost *:80> ServerName int.example.com ServerAlias int CustomLog /var/www/logs/int.example.com/access.log combined ErrorLog /var/www/logs/int.example.com/error.log [...]

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:

A question about mongrel, apache and authentication. I''ve got a Rails site with I think a very typical setup: a mongrel cluster behind an Apache proxy. So Apache''s handling the static stuff and it hands off dynamic content to mongrel. I want to put the site temporarily behind Apache''s basic authentication. What I get when I do this is that is a password prompt which

Hello everyone, I did some initial tests and it seems that mongrel does not support byte-range requests. Is this correct? The reason I ask is that the iPhone requires byte-range requests to work in order to stream audio or video from a web server. Thanks in advance, alan

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''ve configured mongrel_clusters behind an Apache 2.2 proxy using named virtual host. Session are saved as ActiveRecordSession. But the cookies created on client side doesn''t correspond to session data saved in database (keys are different). The RoR app react just like it doesn''t have a session at all. If I don''t use Apache as a proxy/load balancer

I am followint this article, http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ ...but I keep getting this error in the log...not sure what to try next... ** Daemonized, any open files are closed. Look at log/mongrel.8000.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8000

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,

Apologies, this may be off-topic. I''ve been wrestling with upload issues and Apache 2.2.2 / mod_proxy_balanacer / mongrel_cluster / Mongrel on Mac OS X Server 10.4.5. Typically the first upload would be fine but the next would make the mongrel instance remain running (ps state = "R") essentially locking up that instance. Apache would then eventually do: [Fri Jun 16 16:45:54

I?m knew to rewrites on apache in combination with mongrelcluster. It?s urgend for me, because the server has an loadaverage about 10 :-((((( Ok so I?m using 3 mongrel-server on an mongrelcluster. The Loadbalancer ist apache I think, that my rewrites are not correct. Please can anybody check my rewrites ? That?s in my /etc/apache2/conf.d/rails.proxy_cluster.conf <Proxy

After a lot of work (and much promising) I have written instructions on various methods to deploy Rails applications in a Windows environment. For those of you who are not stuck with Windows, this won''t matter too much to you, but I think this is really useful for those in Windows shops. Topics covered: * Serving Multiple Rails Applications on Windows with Apache and Mongrel * Integrate

Good morning everyone, I am running apache 2.2.3 compiled from source and proxy load balancer as described on the mongrel site. I have a total of three sites, this setup works really well for two of them but for one of them, I keep getting "Forbidden" errors and this error in the apache logs: [warn] proxy: No protocol handler was valid for the URL /. If you are using a DSO version of

If this was in the docs, I''ve missed it. How can I have multiple mongrel clusters on a server? All the documentation that I am seeing seems to assume that I am only running one cluster.

I''d like to use Mongrel_cluster with SSL on a green-field application (it can be configured however is best - initially, "ease of setup" is important, but then soon after will be scaling and response time). I''ve read a lot of emails on this topic, and checked out the Mongrel pages, etc, but I''m left with this question of what is recommended: For a