similar to: first request always fails

Hi, Are there any recommendations as to what is currently the most stable setup is for mongrel & apache? I read somewhere (probably here) that you should avoid using PStore for sessions. Are there any more of such recommendations? Also, what is currently the safest version of mongrel to use in production? Jeroen

This GemPlugin will gzip your HTTP responses from mongrel if the client says that it supports it (eg, most modern browsers). I''ve tested it in IE6, Firefox 1.5 and Firefox 2.0RC3 Install: gem install gzip_filter --source http://edenli.com Configure (assuming rails): cd RAILS_ROOT echo ''uri "/", :handler => plugin("/handlers/gzipfilter")''

First off, a big thank you to Zed and the development team for mongrel and mongrel cluster. I''ve deployed it for two apps (through an apache 2.2 proxy) and it''s amazing how much snappier everything is. Previously we were using lighttpd and lighttpd-fastcgi proxying through apache 2.0, which was turning into a hassle for lots of reasons, most notably the ruby fcgi

Hi, I''m halfway developing a tiny plugin that allows people to scrub flash video files. I''ve got my plugin setup to monitor a directory /movies. Whenever a .flv file is requested within that directory, some stuff should happen, if not, the request should be processed as usual. I don''t know how to do the latter.. require ''mongrel'' require

Calling All Mongrel Minions! I wanna have some fun and would like this as a Christmas present. The site http://www.workingwithrails.com/ has this lame popularity system that''s kind of irking some of the main Ruby contributors. I think it''s kind of funny, but would like to demonstrate what an army of motivated people can do to these kinds of popularity contests. So, as a

I''m spending today writing documentation. I''ll be updating quite a few documents, doing some edits, and adding some user contributed docs. If anyone has documentation suggestions, FAQ questions they''d like included, or things they think are old and stale, then let me know. Swing by the Lingr room: http://www.lingr.com/room/3yXhqKbfPy8 And drop me a line if you want

Hi ! My mongrel just starting spitting out these nice lines: The error occured while evaluating nil.accept. TELL ZED HE''S A MORON. !!!!!! UNHANDLED EXCEPTION! You have a nil object when you didn''t expect it! Not sure what happened or why, but just FYI: Zed, you are a moron :-) Happy holidays! Gitte Wange

Hi Everyone, Just want to get out another ping on the Mongrel pre-release saga. I''ve updated a bunch of the documentation to include documents people have donated and to beef up the FAQ for most of the questions people have asked over the past month. INSTALL gem install mongrel --source=http://mongrel.rubyforge.org/releases/ CHANGES * Fixed memory leak by switching to Sync rather

Hi there what''s the status of the 0.13.4 release on Windows? I want to wrap up a project in the next 2 weeks and I''d wait for the new release if it''s coming in that timeframe. Otherwise I''d stay with the current windows version. thanks Jens-Christian Fischer

Hey folks, I ran into a few people at RubyConf who were having 99% CPU issues. Please contact me if you meet the following criteria: 1. You are running a production site. 2. You are experiencing 99% CPU errors. 3. This is frequent enough that you cannot manage it. Thank you. Please contact me off-list about it. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

I tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

Time for some all time pimpage folks. Me and Matt Pelletier wrote a small PDF book on Mongrel entitled: "Mongrel: Serving, Deploying, and Extending Your Ruby Applications" since we really wanted you to know what it was about. It''s published by Addison Wesley Professional, has just over 100 pages of goodness, and is available for $14.99 at: http://safari.oreilly.com/0321483502

Hi everybody, I just suscribe to the list because I have a problem using mongrel and mongrel_cluster... I setup a server (debian unstable wich provide apache 2.2.3 as a pakage) but I have an error when I try to access my application : ERROR 403 : Forbidden, You don''t have permission to access / on this server. When I check apache''s logs I found that : [warn] proxy: No

Hi, I am having a bit of a problem with my app that is using mongrel. For a particular vendor we use, they are generating links that look like:

Hi, I just gave Mongrel a try on my Rails app. After running ''mongrel_rails start'' everything seems fine. Yet, when I start a request I get the following error message on the console: ERROR: You have a nil object when you didn''t expect it! The error occured while evaluating nil.readpartial That''s it. The application works fine with Webrick and

Hi all, Tried out the mongrel upload progress plugin with Drb and it works great on my OSX development box, but when putting it into production (Ubuntu Dapper), uploads complete but the app isn''t returning any values for upload progress, and uploads are not showing up in the queue when running upload_client.rb. Before anyone asks, yes, I''m running both the mongrel instances and

The company I work for is launching a new web site tomorrow. News of our launch will be published in major publications throughout the week so I want to make sure we are prepared for the load. Production Environment: HP Proliant server w/ 8GB RAM and dual AMD64 Opterons Memcache is used as the session and fragment store (512MB for it) MySQL is running on a seperate server in the same rack We use

Zed, I purchased your book and was reading through it. On page 25 it states: "Mongrel will give precedence to the parameter values in the config file over those in the command line." I was wondering why this is not the other way around, preference given to the command line options. Thanks, ~Wayne

I''m going to make a change to how Mongrel is versioned to help out folks packaging it and tracking it as a pre-release. Previously I just did whatever was simplest, but now I''m going to do a slightly different approach. This is open for comment and suggestions. Here''s the new rules: 1) There are only official and pre-releases. This doesn''t change. 2) The

Here''s my config: :debug: false :daemon: true - mongrel :log_file: log/mongrel.log :pid_file: log/mongrel.pid :environment: development And I start Mongrel with: mongrel_rails -C config/mongrel.yml It starts up fine, and creates and logs to the log file, but I haven''t seen it create a pid file yet. Any idea why? BTW, why does Mongrel generate a config with vars like :var: