similar to: Mongrel/Rails weird problem with methods becoming private

Hi Zed, > > NoMethodError in Profiles#change_interests > > private method `equal?'' called for #<Interest:0xb767ae8c> > > On another box with the same mongrel gem versions, it works fine. A > > week later I''m asking in desperation, what have I broken?! > If it works in one place, but not in another, then you have to find out what the difference

I''m having a strange problem accessing a 1.7GB Ferret index from within Mongrel (1.0.1) on Linux. On OSX a Ferret search through Rails takes a fraction of a second. From the command line, bypassing Mongrel, the search takes about the same amount of time. On Fedora Core 4 a Ferret search from the command line takes a fraction of a second, but the same search through Mongrel never

I''m having a strange problem accessing a 1.7GB Ferret index from within Mongrel (1.0.1) on Linux. On OSX a Ferret search through Rails takes a fraction of a second. From the command line, bypassing Mongrel, the search takes about the same amount of time. On Fedora Core 4 a Ferret search from the command line takes a fraction of a second, but the same search through Mongrel never

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

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

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

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

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

Howdy, I''m trying to debug a situation where a Rails app running on Mongrel +Apache stops listening to requests. Restarting Mongrel and Apache brings it back to life. First off, here''s some info on versions, etc...: Red Hat Enterprise Linux ES release 3 (Taroon Update 8) ruby 1.8.5 (2006-12-04 patchlevel 2) [x86_64-linux] Mongrel 1.0.1 Rails 1.2.1 fastthread (0.6.2)

What''s a rule of thumb for guesstimating how many Mongrels to use in a cluster for an app? I have an app that gets about 5000 unique visitors per day. I figured I''d give it plenty of Mongrels -- twenty to be specific. After running out of memory and hitting the swap periodically, I scaled it back to five and it still seems to serve up visitors fine. So, is there some super-secret

Does anyone know whether the mongrel upload progress plugin works with nginx? It works fine for my app under pound, but not with nginx. I am using DRb to handle the uploads as detailed at http://mongrel.rubyforge.org/docs/upload_progress.html . If I am using pound I can see the uploads with irb -r lib/upload_client.rb , but cannot if I am using nginx. Does anyone know anything more about this

Hi, I run a medium-sized website that uses mongrel/rails in the following configuration: -frontend reverse proxy to a cluster of 7 app servers -each app server runs apache 2.2 with mod_proxy_balancer that balancers the requests out into a mongrel cluster of 35 servers. -each mongrel is version 1.0.1 the mongrel cluster config looks like: port: "1620" environment: production address:

We''re almost done with our migration from Apache+FastCGI to Apache+mongrel_cluster. There have been a few bumps in the road, mostly deploy issues that have nothing to do with mongrel (we don''t have root access on our production server). This is for a RedHat Enterprise Linux 4 setup. Zed, would you want the process we went through for the docs section of the site? Right now

Is it possible to have mongrel not advertise itself or at least its version in response headers ie. Server: Mongrel 0.3.13.4 Sorry if I missed this directive in the docs but I couldn''t find it anywhere. Thanks GW -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20061219/025d1383/attachment.html

A totally idle mongrel seems to wake up about once a second doing a little stuff like: select(4, [3], [], [], {0, 999696}) = 0 (Timeout) gettimeofday({1176400534, 112594}, NULL) = 0 select(4, [3], [], [], {0, 0}) = 0 (Timeout) time(NULL) = 1176400534 time(NULL) = 1176400534 gettimeofday({1176400534, 113841},

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

Hello, I have problem with Mongrel 0.3.14 on unix I can not use the "-B" (debug) with the "--prefix" flag the mongrel_debug/logs files are being created but never update. Do anyone have a work around for this ? Yves

Hello Mongrels around the world! Been thinking a way to unify the issue I described in the subject. For those who aren''t aware, mongrel (actually, mongrel_rails) only generate the log file if daemonize was used (-d) That means no log file under windows, due his lack of fork/daemonization capabilities. Now, users that need to run mongrel on windows cannot report and fill the empty