similar to: mongrel 0.3.13.3 in debug mode chewing up memory

Hello Everyone, This is the official 0.3.13.3 release of Mongrel. Mongrel is now released under the *Ruby license* instead of the LGPL. I''m hoping this increases the adoption of Mongrel even further and hopefully I can start pushing to get Mongrel included in Ruby directly. INSTALL As usual, you install it with your friendly gem install method of choice: gem install mongrel Or

Hi Everyone, I have a small pre-release for Mongrel that will eventually be the 0.3.13.3 release, but it needs some quick testing before I make it official. There''s a bug for only some folks and I need to find out what''s causing it. The bug is that the object_id method gets the signature: def object_id(param) end Which is incredibly evil. Normally this does nothing to

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes

I have apache 1.3 with mod_ssl in front of mongrel/rails. Apache is setup to require client certification, and I''m trying to figure out how to pass the ssl env variables to mongrel. Here is the apache config to proxy requests to mongrel. I haven''t tried to pass env variables like this before so I''m not sure if it''s the apache config I have wrong, if mongrel

Hello, I''m trying to get a new application running with mongrel. I''ve been running a number of applications already using it and it''s been working fine, however now I can''t get mongrel to start. The only difference I can think of is that I''m using postgresql for this and not mysql. However, I am able to run the application using webrick. When

Newbie question here: I''m hitting my rails app and killing mongrel. Any ideas? Here''s the error: /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:628:in `accept'': Software caused connection abort (Errno::ECONNABORTED) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in `join'' from

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

Alright, it seems that I am having a bit of a problem with mongrel. My mongrel processes have been crashing pretty often and twice last night. I''m really not sure why, but I really need to fix it. I am running 0.3.13.3. Here is the mongrel.log file. Any ideas, things to look at, etc... is appreciated. Thanks, Carl PS, do all the broken pipe lines mean Mongrel is serving the static

Bradley Taylor shot me this *goldmine* of ugly ugly ugly dogs: http://www.sonoma-marinfair.org/uglydogvote.shtml I *have* to use one of these for the Mongrel BUGS Mascot. He''ll go on our bug list page and replace the little beetles on the left. Pick the dog you think best represents a lovable but defective pooch and reply to this with your +1. Let the voting begin! -- Zed A. Shaw

Hello all, new convert to Mongrel here and am trying to get things going. Right now I can start mongrel up just fine and it seems to work great, but I''m trying to use the nifty console I heard about and can''t seem to get it going. `mongrel_rails console` Cannot run the console script: unititialized constant RailsConfigurator Any ideas? I just installed everything yesterday

Hello, I have a working mongrel cluster and want to use Lighty as the frontend webserver. I want ligthttpd to deliver the static content. So I did gem install sendfile --remote Everything installed. But if I run the tests like gem check sendfile --test --debug i get the following error message: Exception `Errno::ENOSYS'' at ./test/test_sendfile.rb:75 - Function not implemented -

Apologies for the formatting, but this is the error I get when I try to start up mongrel. The app does work under webrick, so I''m not real sure what''s going on here. Thanks for any insight into what''s going on. -j ** Starting Mongrel listening at 0.0.0.0:3000 /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register'': undefined method

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

Hey Folks, There''s a nasty little bug in 0.3.13.3 when running in development mode which could cause all sorts of problems. Please grab the pre-release of 0.3.13.4 and tell me if it works for you: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need

Hello Everyone, I just posted another pre-release of Mongrel that fixes a bug which caused Mongrel to claim it was getting parsing errors because the QUERY_STRINGs were too long. In actuality it was shift in the parser that made empty queries (/test?) become negative. This is fixed up now. Here''s the full list of changes: * It has a couple of fixes for win32, but I still have to

Just thought I''d let you know that your http parser worked great for creating an http protocol handler for Eventmachine. It wouldn''t take that much effort to use Eventmachine for Mongrel, might be worth a shot just to see how it does. A few things would need to be restructered, like HttpRequest where you read the rest of the body, and calling the handler. But it

We tried to give Mongrel a go running our application which has moderate traffic. We got mongrel up and running easy enough but 3 times in a short period(2hours) mongrel just died with the following error when we went live to production with it. As you can see we are running mongrel-0.3.13.3. /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:576:in`peeraddr'': Transport endpoint

Alright, this time a small announce going out to *just* the mongrel list so I can get some early testing. There''s a new pre-release of 0.3.13.4 out that includes the win32 version of the gem. ** WIN32 USERS SHOULD INSTALL THIS AND TEST.*** ***** BUT NOT ON PRODUCTION SYSTEMS. ****** As usual, you install it with: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/

Hi, what is the preferd way to configure/start mongrel? [ ] with Mongrel::Configurator => HttpServer [ ] @var = HttpServer.new(...) @var.run I ask because the only debug methode i have found was in Mongrel::Configurator ;-) @Zed: are you also subscribed on nitro list?! regards Alex

Hi, I''m pretty newb at Rails deployement stuff. I''m setting up a Mongrel web server on windows following the tutorial on the official site. My app works except when there''s interaction with MySQL. I get this error : "Uninitialized constant Mysql" Now i''m pretty lost and i''m sure i''m doing something wrong. I''ve tried