similar to: esi cache server built on mongrel

Hi list, I downloaded and tried to install Mongrel (latest stable version) from the -win32 gem. Platform is Win2K. It said it needed daemons so got and installed that. Then it said it needed cgi_multipart_eol_fix (I think that was the name, not at my machine now, can confirm later and repost if needed). Googled for that but couldn''t find it. (Don''t have net connectivitity for a

I just switched to Mongrel, and it''s been working much better than my previous lighttpd/fastcgi setup. So thanks for the awesomeness. My current problem: once or twice an hour, I get following error in production Mongrel timed out this thread: too many open files I never get it in testing or on our staging server. Any ideas what would cause that? It doesn''t *appear*

I have been getting this error on the production server after rails was updated to 2.0.2 and moreover this worked perfectly in the development mode. This crash occurs when no one is using the app for an hour or so. This is the error that I get in the logs. (nohup.out file). The production log doesnt show anything unusual. Please help me out guys.

I am having a problem with mongrel just stopping inside a periodically_call_remote function so I ran mongrel with debug enabled Mongrel seg faults after a few minutes The mongrel filelog shows 5 files open when this happens. Same log files that are open all the time. Wed Dec 19 15:10:21 -0700 2007 FILES OPEN BEFORE REQUEST /calibration/ackAdjustDistance --- log/mongrel_debug/objects.log: 2

Hopefully that gets everyone''s attention. Evan Weaver has whined enough to make me do a release to change the requirements on the Mongrel gem so that it doesn''t need the cgi_multipart_eof_fix anymore. *************************** THIS ALSO MEANS THAT MONGREL WILL HAVE TO REQUIRE RUBY 1.8.6 OR GREATER! NO EXCEPTIONS! *************************** I know Debian guys like to hack

Hi folks, I have a problem with a storage web service our group wrote using Mongrel::HttpHandler We have a consistent problem when using http PUT to this service when the data is larger than about 4 GB. The web service actually retrieves and processes the data, but the clients hang - the TCP connection is still in the ESTABLISHED state on the client side, but the TCP session no longer exists on

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,

Hello Zed, I was just wondering if there were any roadmap/changes coming for Mongrel in the future. Are there any plans to put the attachment parsing code back in, or just anything else to be on the lookout for? Honestly everything''s been working fine for me, so I shouldn''t care, but I''m one of those guys who loves new toys every few months. Thanks for making my job

Hi All, I''m a newbie and I''m soooo confused at the moment! Here''s my setup: 1) I''ve installed Ruby 1.8 on an Ubuntu 7.10 platform. I used apt to install that. 2) I downloaded rubygems_1.1.1 and installed that (tar -xzf, then ruby setup.rb) 3) I installed rails (gem install rails --include-dependencies) 4) I installed mongrel (gem install mongrel

Howdy -- I''ve been tracking down mem leaks (oh, the fun...), and I think there is a clue in objects.log. There are a few mentions of this file, but usually Zed saying "look at this file and it will help you". Can anyone clue me in to what the actual columns mean? 18,Float,143952,256821,112869,,, 18,String,39543,41693,2150,24.727076,55.526376,2308.000000

Hello. Some time ago I committed a Rubinius assembly-based HTTP parser generated from Ragel to the Rubinius git repository. Yesterday I made a Mongrel gem which installs and works on Rubinius. This basically involved commenting out anything to do with fastthread or the http11 C extension. If there''s interest in releasing a Rubinius-targeted gem, I can make changes to the Rakefile to

Hi, I''m doing development with Mongrel 1.0.1 on Ruby 1.8.4 / OS X 10.4.10, and I''ve found that often when I shut down my server with ^C, it hangs for a while, gobbling up all CPU. Sometimes it stops after a few seconds, sometimes it''s run for several minutes at least. This happens across all the apps I develop on, but it seems to hang longer after

SqueezeBox is a simple file system based routing framework for erubis templates. It aims for a couple of niceties as well: Instead of putting your logic inside your template, like you would with PHP, SqueezeBox recognizes a separate logic file to be called before it loads the template. This allows you room to load ActiveRecord models or do calculations. These logic files return to the webserver

Hi I posted this to the Ruby on Rails Talk group but I thought I''d post it here too as it''s probably a more appropriate group. Hope this is ok. I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are

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

This class provides a CookieJar object for Mongrels. Just initialize with response and request objects and then treat like a hash. Does not depend on cgi.rb ry -------------- next part -------------- A non-text attachment was scrubbed... Name: cookies_for_mongrels.rb Type: text/x-ruby-script Size: 4776 bytes Desc: not available Url :

I have a rails application that runs on multiple mongrels and I would like to make the log files non-interlacing. Are there any logging modifications/other loggers out there that I could use to create process safe logging? Thank you, Matt Margolis

Ok, my little experiment proved my point. Ruby 1.8.6 is not viable for production. Requiring it and dropping the cgi fix back patch isn''t an option. It''s not even clear whether the latest 1.8.6 has any remaining fixes. So, crisis averted. Mongrel WILL NOT require 1.8.6 and now I''m going to dig out where these security fixes are coming from and how to host this kind

I seem to have a (recent) problem with mongrel on NetBSD. I''m running a development release of NetBSD (called NetBSD-current 4.99.34). When I start mongrel, it listens on the IPv6 wildcard address, but not on the IPv4 wildcard: => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with

I just found a vulnerability in one of my web apps that was running Mongrel 1.1.2 where I could go to URIs like /.%252e/.%252e/.%252e/.%252e/.%252e/.%252e/.%252e/etc/passwd and it would serve the actual /etc/passwd file. The issue seems to be in lib/mongrel/handlers.rb in the change from 1.0.3 to 1.0.4 req_path = HttpRequest.unescape(path_info) - if @path - req_path =