similar to: Mongrel 0.3.20 -- 5 Hours Deadline

Hello All, I''m putting out a quick half-release because there''s some work on the MIME types I''ve included that needs to be done by all of you. Read at the end to understand your role in what you started. This release features two major capitulations on Mongrel''s stance of not being a full web server. The first is Mongrel now sports a YAML file with 739 MIME

Hello Everyone, We''re hard at work getting the hot new win32 service Luis wrote out and ready for production. We''re hoping to have that included in the 1.0 RC1 release we make very soon. This pre-release is just to make sure that we didn''t step on any toes. Install it with: $ gem install fastthread --source=http://mongrel.rubyforge.org/releases $ gem install

On 1/23/07, mongrel-users-request at rubyforge.org < mongrel-users-request at rubyforge.org> wrote: > > > Date: Mon, 22 Jan 2007 21:48:21 -0800 > From: "Zed A. Shaw" <zedshaw at zedshaw.com> > Subject: [Mongrel] [ANN] Mongrel 1.0.1 Officially Released > To: mongrel-users at rubyforge.org > Message-ID: <20070122214821.4804e941.zedshaw at zedshaw.com>

Alright folks, I put in a fix for camping and added the patch by Thomas Hurst for the accf_http deferred accept settings for FreeBSD. As usual, please test this release out and let me know if it has any additional problems. I''ll be working on win32 builds today and tomorrow with Luis. Install with: sudo gem install fastthread --source=http://mongrel.rubyforge.org/releases sudo gem

Hi Everyone, There''s quite a few of you who have contacted me about Mongrel suddenly stopping. After a lot of investigation, I found that the common thread between all of you is memcache and Eric Hodel''s memcache-client. People who were running this combination would have intermittent pauses and investigating the stalled mongrels showed that memcache-client was waiting for

Hey Everyone, Topfunky (Geoffry) has created a great PeepCode screencast on using httperf to performance measure your web applications: http://nubyonrails.topfunky.com/articles/2007/03/05/peepcode-page-caching-and-httperf http://peepcode.com/products/benchmarking-with-httperf Topfunky put a ton of work into this and really got it right. The attention to detail is very good and he researched

I just created a test rails app, and am having very wierd issues with mongrel cluster. Here''s what I''m doing: rails test sudo chown -R mongrel:mongrel test cd test sudo mongrel_rails \ cluster::configure -e production \ -p 8000 -N 3 -a 127.0.0.1 --user mongrel \ --group mongrel It correctly writes the mongrel_cluster.yml file to the config directory. Now,

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

Hi, I have installed mongrel gem and when i tried to start mongrel_rails start its causing me following problem mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... Requiring REXML /usr/local/lib/ruby/gems/1.9.1/gems/activesupport-3.0.10/lib/ active_support/dependencies.rb:239:in `require'': no such file to load --

temporary fix write in ./config/environment.rb RAILS_GEM_VERSION = '2.1.1' unless defined? RAILS_GEM_VERSION and "gem install rails --version"=2.1.1"" > I've figured out fixes for the installer portion for ovirt on Fedora > 11 just running into this problem currently with the > ovirt-mongrel-rails service, It will start but there are errors in the >

Hello world, I''m having some problems setting up a new Debian deployment box...just installed the rails stack, mongrel, etc... When I go to start mongrel I''m getting a weird error I can''t figure out. Some help please? -> mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000

I've figured out fixes for the installer portion for ovirt on Fedora 11 just running into this problem currently with the ovirt-mongrel-rails service, It will start but there are errors in the log and can't access /ovirt in the browser. Just wanted to get some input, I've tried a few fixes from google with no success and I'm no rails expert :) ** Daemonized, any open files are

Hi, I am working on deplying my Rail app to QA and then move to production. Since on our QA servers, there is no internet access and also for production servers, internet access is strictly prohibited. As a result, there is no way to install mongrel by use "gem install mongrel" command. The first option I tried is to put mongrel and all other gems under the vendor directly in my app,

Hello everyone, Mongrel now has plugins that are based entirely on RubyGems. This feature was so slick that I decided to bust it out into a separate project called GemPlugin (more on that later). What the new plugin system does is makes it so that people can distribute Mongrel plugins as just plain gems, and mongrel will load them on the fly if people install them. There''s no

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

This release of Mongrel is coming at you with lots of very little but important features and fixes. The big highlights are: * Initial beginning of the plugin support that will let people write their own handlers and other things for Mongrel. * Timeout now works again but couldn?t find an alternative to the buggy Timeout class. * SwitchTower friendly signal handling for

Sorry if this is the wrong place to ask, but when I run mongrel evented using swiftiply and then send it the USR2 signal to restart it, it dies. Without eventing, USR2 restarts mongrel as expected. Anyone else seen this? Here''s a dump: $ EVENT=1 mongrel_rails start -d -P /tmp/m.pid -p 4321 Using Evented Mongrel ** Ruby version is up-to-date; cgi_multipart_eof_fix was not loaded $ kill

Hi folks, Getting much much much closer to the 1.0 release. I have some documentation to work on tonight, and I need to go through the patch queue one more time, but I''ve put up another pre-release for people to test. What this pre-release does is pull together the various patches, monkey patching, and alternatives that make Mongrel either faster or more stable. It is also the start

Hello, I''ve been trying (unsuccessfully) to hack my mongrel_cluster to re-ststart in an alternating manner. Specifically, this soluiton: http://blog.carlmercier.com/2007/09/07/a-better-approach-to-restarting-a-mongrel-cluster/#content Which means I an call to mongrel_rails cluster::restart to do this: mongrel_rails start 8001 mongrel_rails stop 8001 mongrel_rails start 8002