similar to: Mongral cluster issue

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: -----------------

Hello, I have a cluster of three Mongrels running behind Pound. All is running well except when I restart the cluster (mongrel_rails cluster::restart) any in progress file uploads (handled through mongrel_upload_progress) stop uploading. That is, if I''m uploading a file (via a web app being served by the mongrel cluster) during a restart, my browser will indefinitely pause as if it is

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

I''m using a cluster of mongrels behind an apache 1.3 proxy pass. I''ve been passing the request to pen, which in turn balances the cluster of mongrels. Now, I''d like to be able to use a different server to send the static files created by the rails application, so I tried to replace pen with nginx. Everything seems to work fine except the environment variable REMOTE_ADDR.

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

Greetings all. I have seen a couple of diagrams on the net that look like a computer set up as an nginx server and more than one mongrel server running at once. What is the advantage of having more than one mongrel server running? Is there a good how-to that explains it very well. thanks shawn -- You received this message because you are subscribed to the Google Groups "Ruby on Rails:

Hi, I''m trying to serve the iPhone a video file from my controller using send_file. However, it appears as thought the iPhone requires byte- range request support and rails doesn''t seem to support this. If I give the iPhone a url that points to an actual file (i.e. it''s served by my webserver nginx, instead of rails) it downloads and plays it fine. Here is the proof

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 Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

Hi guys, I''ve been chasing a problem in my web-stack: Lighttpd -> Mongrel -> Rails, and found a problem with the interaction of Lighttpd and Mongrel. If a request takes more than 5 seconds, Lighty will retry it - and then the requests / responses get mixed up in Lighty and it returns a bad response to the client. Not good. I''m convinced that the problem is

If this has already been covered, please point me to that (I didn''t find anything in my searches)... We are using F5 BigIP LTM load balancers. They have many pools of Mongrels they load balance across, and I of course want the F5 to know when a Mongrel goes down or is unavailable, etc. To do that, I need to have an F5 health monitor for HTTP make a request to the Mongrel. We do this

After reading the digital shortcut and the documentation on the web site I''m confused. Which one should I use? pen, balance or nginx ? I don''t want to use a behemoth like appache and ssl is not needed so it reduces my choice to those three only.... What are the pros and cons of each? I don''t have much money, so the less ressources I use the better it is for me.... As

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

Does anyone know how to use Mongrel to create virtual hosts? My production site will have all kinds of domains pointing to it, and I also need to figure out how to do subdomains. Rails should react to the host name, doing a lookup based on the name and pull different records from the database based on this. For example, I''d like www.mysite.com to point back to 127.0.0.1:3000, and the

how does request.host get set? Is there a way to manually set the value in request.host? I have several application servers running rails, each has its own internal address in the request.host, so when calling redirect_to or url_for function, it uses the internal address which is not accessible to the user. what I want is to set request.host to return mysite.com, no matter which application

Hi, I''m running a rails (mongrel) based web service behind an apache proxy, on windows 2003. Sometimes I see a POST in the apache log that returned a 404 but nothing about it in the rails log. It doesn''t happen every time, 9 out of 10 times it works just fine. The post (is actually a put) comes from a .NET application uploading a small xml-file. The log message in apache

I tried benchmarking the same site behind an NGINX proxy with both fastcgi and mongrel, and for some reason mongrel is performing pretty poorly in comparison. Any idea what I might be doing wrong? Here''s my benchmarks for 1 fcgi: Server Software: nginx/0.4.0 Server Hostname: eship.com.br Server Port: 80 Document Path: / Document Length: 95

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

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

Lets say you have a site that is serving, oh, around 100k unique visitors a day (plain ole'' browser requests) - plus probably ~ 40k uniques to feeds. Assume this site is 90% read like most of the web, so the traffic looks like your typical news or portal site. There are two web boxes behind a hardware load balancer, each doing apache 2.2.3 -> mongrel_proxy_balancer -> mongrel