similar to: mongrel problems

I''m looking for the most reliable setup for Mongrel. Reliable meaning avoiding things like sending too many requests to a single mongrel process, or sending requests to a mongrel process that has hung for some reason. The handler will most likely be rails, but it might be a custom handler. SSL is also a requirement, which limits the options a bit but it can''t be done away

Hello, I want to install a bunch mongrel servers with an apache in fronthead, all that on OpenBSD. But OpenBSD is released with a homemade Apache 1.3.29 patched by the OpenBSD team. I really want to keep this version of apache and I don''t want to change it to Apache 2.x (because of the security and the license but it''s not the point here). But for having mongrel, it has to be

Hello all. I too found out that I sometimes have some action that can take up to 10 seconds in my rails application. I''ve read all arguments Zed made about polling/and inbox strategies, and I think I just can''t work around my feeling that a "wrong" request that takes up too much time should be able to lock subsequent requests in mongrels queue. That''s what

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

We have been searching for a Rails deployment architecture which works for us for some time. We''ve recently moved from Apache 1.3 + FastCGI to Apache 2.2 + mod_proxy_balancer + mongrel_cluster, and it''s a significant improvement. But it still exhibits serious performance problems. We have the beginnings of a fix that we would like to share. To illustrate the problem, imagine a

I know most people use pound, but has anyone tried using ultramonkey as a load balancing solution between a cluster of mongrels and lighttpd? Thanks, Ray -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email

Hello, I am configuring apache 2.2 to serve my rails app through mongrel at the root of my server. First, I redirect all http traffic to https with the following: ServerName emiliano NameVirtualHost *:80 <VirtualHost *:80> RedirectPermanent / https://emiliano #this server is only accessed internally </VirtualHost> Inside the <VirtualHost *:443> section, I have the following

Is anyone using the setup described at the Rails blog? http://weblog.rubyonrails.org/2006/7/3/pound-makes-lighty-and-mongrel- play-nice I''m using it in production, and the only problem I have is the same as people have described in the comments over there, namely that Rails thinks all requests come from localhost. See http://isabont.com/requestinfo for the headers. Any

Dear all, I am researching solutions for "how do you squeeze as many Rails apps as you can on a cluster" problem. Environment constraints are as follows: * 4 commodity web servers (2 CPUs, 8 Gb of RAM each) * shared file storage and database (big, fast, not a bottleneck) * multiple Rails apps running on it * normally, the load is insignificant, but from time to time any of these apps

Any news on the Apache Best Practice Deployment instructions? I''m getting ready to set up a production server, and would prefer to use Apache and Mongrel/Cluster. Don''t think I''ll be able to get the latest Apache though. Do I have to proxy through Pound or something to handle multiple mongrel instances? Any pointers? Any help appreciated, Brett

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

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

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

Hi everyone, Recently, I''ve been reading about different deployment environments for rails and mongrel. One configuration I''ve started seeing is apache -> pen -> mongrel cluster. See http://errtheblog.com/post/35 as an example. Can someone explain to me the benefit of using Apache and Pen as opposed to either using apache as a load balancer or pen by itself?

We have a load balancer sending requests to one of X boxes and one of N mongrel processes on that box. Since each mongrel processes is multi-threaded but it has a mutex around the section that calls rails, we end up with several requests queued up waiting when they could have gone to another box with a free process. For example, boxA, and boxB. boxA has mongrels 1 through 10 boxB has

Hi all. I''m trying to skip the Rails page cache if the user is logged in: --- # Rewrite index to check for static RewriteCond %{HTTP_COOKIE} !^.*logged_in=yes.*$ RewriteRule ^/$ /index.html [QSA] # Rewrite to check for Rails cached page RewriteCond %{HTTP_COOKIE} !^.*logged_in=yes.*$ RewriteRule ^([^.]+)$ $1.html [QSA] # Redirect all non-static requests to cluster RewriteCond

Hello, I want to install a mongrel rails server with an apache in fronthead, all that on OpenBSD. But OpenBSD is released with a homemade Apache 1.3.29 patched by the OpenBSD team. I really want to keep this version of apache and I don''t want to change it to Apache 2.x (because of the security and the license but it''s not the point here). But for having mongrel, it has to be with

I''m happy to announce that ChaCha.com a new search engine that debuted this week and it runs on a mongrel cluster. Warning, promo follows. :) ChaCha.com is unlike any other search engine since it allows you to connect to a "guide" with experience in the field(s) of knowledge you are searching in. (Based on your keywords) Check it out at http://www.chacha.com Now on to my

Greetings, I posted this not on the Rails mailing list and didn''t get a definitive response so I thought I''d post it here, since I figure lots of you are using mongrel with Rails apps. Any suggestions would be greatly appreciated. I''ve been using file-based fragment caching and DB-based session caching quite extensively. I decided to try out memcached for both to

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