similar to: Mongrel 0.3.17 PR -- Big Work Day, 1.0 RC1 Very Close

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

I''m running a site that gets ~30k to 40k page hits per day. In the last 4 days my mongrel processes have been jumping into high CPU usage a couple of times a day to the point where my site becomes unresponsive (database on a diff machine with no load). The only way for me to resolve the problem and reduce load on the machine is to delete my rails cache directory (I have plenty of space

Hello Minions! It''s *finally* here. Mongrel 1.0 RC1 for everyone to test, even the win32 folks. I managed to get everything to build on windows, including fastthread, and even cleaned up the "releases source":http://mongrel.rubyforge.org/releases/ so that it should install cleaner. Win32 will have to try and report problems, as it seems rubygems is real finicky on win32.

Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel

Hello all, For the past couple of weeks I have been spending some time debugging a couple of issues I was having with Mongrel when I put load on it. I have seen two distinct issues: 1. Mongrel stopped responding as if in an endless loop. 2. Mongrel crashed when severely loaded. I believe to have resolved these two issues and have attached patches which shows the resolution (simple as it is).

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

Hi all, We use mongrel behind apache (using mod_proxy_balancer) to run an internal app for our business. Lately we''ve been seeing frequent errors from some of our mongrel processes. [Sun Dec 16 08:48:47 2007] [error] [client <CLIENT1>] (70007)The timeout specified has expired: proxy: error reading status line from remote server 127.0.0.1, referer:

Hi, I''ve got to active project both running on the last Apache 2.2 and on Mongrel 0.3.13.3. One is running perfectly, the other gets (always on the same pages, but not after each request, it seems to be random) a ProxyError every now and then which leads to the mongrel process being called to die and subsequently slowing down the whole web site. I have to restart the mongrel

Another fancy release with just a few little changes from yesterday: * Set-Cookie, Set-Cookie2, Warning, and WWW-Authenticate are allowed as duplicate headers. * mongrel_rails stop now has a --wait option to go with --force. It will wait for either the given timeout in SECONDS or the PID file to go away. If the PID file goes away it just exits. If the timeout happens then it does a kill -9 on

Hello Guys, Been testing fastthread (known on previous releases as optimized_locking) for soon to be released 0.3.18 mswin32 gems (official ones). Attached to this message is the ruby script I used for the test results shown on graphics [1] and [2] The idea of the script is simulate what Mongrel do with threads creating a simple workload for testing Ruby VM stability. [1] refers to normal,

Hi list, I''m having some issues getting backgroundrb to play nice with more than one mongrel. When I run my app on a single mongrel instance it works fine. I have two different problems show up in my backgrounrb_server.log. The top of the backtrace is shown here: 20070130-12:03:03 (92473) failed to find slave socket - (RuntimeError) 20070130-12:03:03 (92473)

Hi, I am getting some problem while installing mongrel on GoDaddy(fedora) server. Env is :: [root at ip-97-74-86-181 bin]# gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.3.4 - RUBY VERSION: 1.8.6 (2008-03-03 patchlevel 114) [i386-linux] - INSTALLATION DIRECTORY: /usr/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /usr/bin/ruby - EXECUTABLE DIRECTORY: /usr/bin - RUBYGEMS

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

Thanks for the help Sean. I managed to get the install fixed, but I''m still having problems. When I do mongrel_rails start, the process just gets stuck and never completes. If I interrupt it I get the following... ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix /usr/lib/ruby/1.8/rubygems/source_index.rb:186:in `search'': Interrupt from

Is anybody testing mongrel on ruby 1.9. I just tried installing mongrel on trunk 1.9 and trunk rubygems and got this error compiling fastthread: /Users/stephen/dev/ruby/1.9_trunk/bin/ruby extconf.rb install mongrel --no-rdoc creating Makefile make gcc -I. -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9/i686-darwin8.10.1 -I/Users/stephen/dev/ruby/1.9_trunk/include/ruby-1.9 -I.

Hello Mongrel Fans, After about a Month of busy work, bad computers, moving half my house across the country, and other dramas, I''m finally pushing out the next release of Mongrel. This pre-release has lots of little goodies and the start of some documentation that should get everyone primed for the big "Mongrel 0.4 Enterprisey Edition 1.2" coming real soon now. INSTALLING

Hi all, I''m getting a strange, intermittent Thread deadlock in production: deadlock 0x2a988d7008: sleep:F(3) - /opt/ruby/default/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723 CPU usage spikes to a full core and Apache 502''s on requests that got handed to that particular listener each time. I tried attaching with gdb, and gdb twisted itself into a knot. Anyone have

Hi, I can''t install Mongrel on Ruby 1.8.6 (patchlevel 279), using Windows XP. My environment: C:\ruby18>gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-07-17 patchlevel 279) [i386-mingw32] - INSTALLATION DIRECTORY: c:/ruby18/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby18/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby18/bin -

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby

Hi All, I''m try to gem install mongrel, but one of its dependencies fails to compile ''cause gcc doesn''t like the -mtune parameter. Is there a way to remove this parameter or cause gcc to ignore it, etc.? make gcc -I. -I/usr/lib/ruby/1.8/i386-linux -I/usr/lib/ruby/1.8/i386-linux - I. -fPIC -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -Wall -fPIC - c fastthread.c