similar to: Mongrel and memory usage

Hello. I just seen some errors in my mongrel application log: It seems related to the httpd OPTIONS keyword Example: Processing LoginController#login (for .30.5.208 at 2007-12-10 09:00:23) [OPTIONS] and our ruby application does not know what to do with it. and finally send an error Does mongrel (which is the http server) is supposed to deal with these kind of request ? I think these

I''ve been trying to track down the culprit of erratic behaviour and crashes on my production server (which is split into a number of Xen instances), so set up a staging server so that I could really try to get to the bottom of it. The staging server (also split with Xen) is set up pretty much identically as far as the mongrel_cluster server is concerned (the production box has two

I heard about a new mongrel plugin or version that''s single threaded and uses non-blocking IO with events. It''s called something like "swifty fly". Anyone have a link for it? Thanks.

I''m trying to sent a file to the iphone (which requires byte-range request support) using the rails send_file method. However, this fails, I think because of mongrel. I think so because if I send the iphone a file handled by nginx, it plays it fine. But then when I serve the file with rails the iphone can''t play it. Any ideas? Alex

forgive me if this has been resolved already... I have an app that is using sendfile to return large files to customers. We can''t use regular Apache to handle this static content since the files are what the customers are paying for - so it wouldn''t be cool for anyone else to get access to them. The issue is that the mongrel mem footprint gets bloated when the files are

Hi, I''ve done some benchmarking on our new servers (being built now), AMD X2 5600, gentoo-hardened. With the same CFLAGS (safe cflags: -march=k8 -O2) I''ve tested the following configs: 1, emerge ruby rubygems, then gem install mongrel (or emerge mongrel, the performance was similar) 2, download the same ruby version, untar, ./configure, make, make install, download rubygems,

So here''s a random question: if a (Ruby) multi-threaded rails server could exist (bug free), would it be faster than using a mongrel cluster? (I.e. 10 mongrel processes versus 10 Ruby threads). I''m not sure if it would. RAM it might save, though. Any thoughts? -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL:

Is the dashboard output of 1.2.1 supposed to validate (I get numerous failures)? I''m seeing some issues that I hadn''t been running into before my upgrade. The first time I load the dashboard I''m seeing a blank area at the top and first button isn''t styled. When the refresh triggers the all of the projects except the first are duplicated and the

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

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

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

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,

I read this in a previous post ( http://rubyforge.org/pipermail/mongrel-users/2006-December/002354.html) .... First, Mongrel accepts remote clients and creates one Thread for each request. Mongrel also enforces a single request/response using Connect:close headers because Ruby only supports 1024 files (so far). If Mongrel doesn''t do this then people like yourself can write a simple

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

Hi, I was wondering if this is normal or if it something i need to wonder about. I get Monit alerts that my mongrels PID files have changed. Changed Service MONGREL_2 Date: Tue, 09 Oct 2007 14:19:38 +0000 Action: alert Host: sa.greenling.com Description: ''MONGREL_2'' process PID changed to 18368 Your faithful employee, monit

Hi all, Is there any integration with testing tools such as RSpec or Test::Unit planned? I see that the cruise task is run correctly, but the tests show up underneath the build log. Ideally I''d like them to show up the same way that they do in ''java'' CruiseControl, in their own section of tests. Will.

greetings, i am getting the below error message in my mongrel log and I want to turn that 22 levels into a full trace. but i am unsure where or how to configure the debug level for mongrel. any advice? thanks - john /usr/lib/ruby/gems/1.8/gems/ruby-debug-0.9.3/cli/ruby-debug/ interface.rb:24:in `join'': can''t convert nil into String (TypeError) from

As of now, I can create a project from Git repository, run a builder on it, and even run the dashboard. Build pages look ugly because build.label in git is very long, a bunch of unit tests is failing, and I had to disable some functionality, namely displaying source control errors in the dashboard. SourceControl::AbstractAdapter#execute_with_error_log (formerly known as

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212

Hi all, My environment is ruby-1.8.4, rails 1.2.2, mongrel 1.0.1, linux 2.6. Now, i have a problem on memory leaks with mongrel. My site is running 5 mongrel processes on a 2G RAM machine, the memory of each process grows from about 20M to about 250M, but it never recover to the initial 20M, so i had to restart the mongrel processes once per day. The load is about 1M hits per day. Waiting for