similar to: Mongrel and MemcacheSessionStore

I''m a bit surprised I can''t find anything about this in the mailing list archives. Basically since Mongrel 1.0.1 I''ve had Mongrels fall asleep without any real cause. A deep sleep, actually more like a coma. The mongrel in question (I''m using a cluster of three) can not be revived. A cluster::stop, then cluster::start is nessesary. A ::restart would not

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

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 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,

Hello everyone, I did some initial tests and it seems that mongrel does not support byte-range requests. Is this correct? The reason I ask is that the iPhone requires byte-range requests to work in order to stream audio or video from a web server. Thanks in advance, alan

Greetings, I posted this not on the Rails mailing list and didn''t get a definitive response so I thought I''d post it here, since I figure lots of you are using mongrel with Rails apps. Any suggestions would be greatly appreciated. I''ve been using file-based fragment caching and DB-based session caching quite extensively. I decided to try out memcached for both to

I''m looking for the most reliable setup for Mongrel. Reliable meaning avoiding things like sending too many requests to a single mongrel process, or sending requests to a mongrel process that has hung for some reason. The handler will most likely be rails, but it might be a custom handler. SSL is also a requirement, which limits the options a bit but it can''t be done away

When I run rake test:units I get this error: 292 tests, 350 assertions, 2 failures, 13 errors rake aborted! Command failed with status (1): [/usr/local/bin/ruby -I"lib:test" "/ usr/loc...] This error just showed up yesterday --- I have no idea how I caused it. Here is my gem list in case that helps: actionmailer (2.3.2, 2.2.2) actionpack (2.3.2, 2.2.2) activerecord (2.3.2, 2.2.2)

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.

I''ve just committed fastthread 0.5.3, which finally gives us a working SizedQueue (which hadn''t really ever worked in previous versions). Mostly it was just a matter of refactoring Queue and SizedQueue into a single class behind the scenes, so I could move the signalling of the SizedQueue-specific condition variable inside the queue''s critical section. Failing to do so

Well, just when I thought I was out of the fastthread business... Okay, in brief: fastthread is a Ruby extension which re-implements the primitives in Ruby''s thread.rb in C. It was merged into 1.8.6, replacing the old thread.rb implementation, but the version that was merged had a couple serious bugs. So -- now I release fastthread 1.0, which is basically the Ruby 1.8.6 version with

It looks like I got too creative in 0.6.1 and consequently ran afoul of a bug in the Ruby interpreter. 0.6.2 works around the bug and should be entirely stable at this point. Thanks to Young Hyun for his help in coming up with test cases. == what? fastthread is a Ruby library which provides a faster (and non-memory-leaking) C implementation of the concurrency primitives from stdlib''s

I''m running jruby trunk which has integrated rubygems 1.0.0 and when I try and install mongrel with gem it blows up when the fastthread dependency tries to do a native compilation. I couldn''t find a copy of the gemspec in the svn checkout but looking at the one installed when gem installing mongrel didn''t show any platform differentiation. There is platform

I''m confused. Wasn''t threading fixed in 1.8.6, negating the need for fastthread? Why is fastthread still a requirement of Mongrel? Just curious. :)

Hi all, I''d really appreciate some help with this... As you see below, I tried to install mongrel after updating my gems, but I get the error shown: sudo gem install mongrel Select which gem to install for your platform (i486-linux) 1. mongrel 1.0.1 (ruby) 2. mongrel 1.0.1 (mswin32) 3. mongrel 1.0 (mswin32) 4. mongrel 1.0 (ruby) 5. Skip this gem 6. Cancel installation > 1

Hey folks, I''m working on the Mongrel book with Zed, and wanted to get some feedback from the core users (this list) about how they use Mongrel. That sounds a bit vague, but I''m interested in hearing things about frustrating problems / workaround, preferred configurations, if you have a particular way you set up / store your config files when developing / deploying an

Hi, I just did a clean install of Ruby 1.8.5 Rubygems 0.9.0 and the Mongrel and Mongrel_Cluster gems. I used only the Debian Etch package manager, nothing compiled myself. Now, on a testapp when I do a script/server, I get the: ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix warning. But it''s not serving my app. Ruby is immediately on 100% CPU load (and 0.7%

Hi, A quick search didn''t explain what fastthread is, and how it relates to mongrel. Why would I want to install fastthread? Thanks, Joe

I''m taking a stab at creating a parser to parse the server response using the mongrel parser as a base. Never having used a parser like Ragel before in my life, I''d like some input on the following for parsing an http server response. This is part of my modified version of http11_parser.rl. In particular what would be better than using ''any'' to match the

Heya Folks- This is mainly for Zed and Mentalguy. I have been playing with the new release of rubygems 0.9.0.8 and I have a major problem with the requirement that fastthread needs to be required before thread. Just requiring rubygems and then requiring fastthread right after that will throw the error: ez _blog $ ruby require ''rubygems'' require