similar to: Mongrel 0.3.1 -- New Site/Runs Right

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

This is a super quick announcement for a new Mongrel plugin called mongrel_console. It was inspired by a request from Tobias L?tke who wanted to tail out logs while Mongrel was running. What mongrel_console does is combine the Rails script/console with Mongrel so that you can control a mongrel server while using script/console. Sounds weird but it''s quite awesome for development

Hello Folks, This is the long awaited release of the Mongrel HTTP library that supports *Ruby On Rails*. I know tons of people have been waiting for it, so I''ve got a few things to lay down first before you get all excited: 1) It''s very very ALPHA support for Rails. It will run a Rails app, and runs my simple apps, but it''s not fast or correct as it needs to

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

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hey folks, I ran into a few people at RubyConf who were having 99% CPU issues. Please contact me if you meet the following criteria: 1. You are running a production site. 2. You are experiencing 99% CPU errors. 3. This is frequent enough that you cannot manage it. Thank you. Please contact me off-list about it. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/

I tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

I''m using the latest Mongrel (0.3.13.4) and restarting causes Mongrel to die. From mongrel.log: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails start -C config/mongrel.yml /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in `exec'': Operation not supported - ruby

Hey, I did some pre-compiled gems for both Mongrel and win32 service, wrote some quick instructions, and threw everything onto a (Mongrel hosted) temp site. Please go hit: http://zedshaw.homelinux.org:3000/files/win32_howto.html And give the instructions a shot. Luis should have the stuff moved around and then we''ll have a nice clean install and set of instructions for all this. Any

Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is http://mongrel.rubyforge.org/docs/howto.html and it covers: * All the start command options including the fresh -G option to generate a config for -C. * The format and usage of the MIME type file (-m

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

Sometime my mongrel server threads..would simply stop responding to the requests...and in the logs i get following error: Tue Sep 05 03:56:40 IST 2006: ERROR: Transport endpoint is not connected - getpeername(2) Tue Sep 05 03:59:21 IST 2006: ERROR: Transport endpoint is not connected - getpeername(2) Tue Sep 05 03:59:21 IST 2006: ERROR: Transport endpoint is not connected - getpeername(2) Tue Sep

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

Hello Everyone, Today''s Mongrel is the first release to sport spiffy pre-built win32 gems. This comes thanks to Wilson Bilkovich donating some Rakefile magic that does the stuff for me. Everyone who uses win32 should send Wilson a thank-you since without him you''d be a victim of my laziness for at least a few more weeks. People who are testing and trying Mongrel out should

I do some indexing using acts_as_ferret in a rails app. I need to do some preloading of the index''s sort fields so that the first request that sorts doesn''t take 5 minutes to complete. I tried sticking my preload code in config/environment.rb and that worked but it gets ran in rake migrations, tests, etc, when it''s not really needed. Is there anything specific 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

Hi, I just gave Mongrel a try on my Rails app. After running ''mongrel_rails start'' everything seems fine. Yet, when I start a request I get the following error message on the console: ERROR: You have a nil object when you didn''t expect it! The error occured while evaluating nil.readpartial That''s it. The application works fine with Webrick and

Following is the output of top command at my server and i find the high usage very much alarming. We are basically a team of three developers working on same machine(remotely), so we run mongrel_rails servers from out ~/public/app directories. We also run a cluster of mongrel servers using apache2.2. Is this much memory use normal? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+

Hello Windows Users! I have finally got my new computer with it''s win32 build working and have just done the first pre-release for 0.3.13 that has win32 support. *** All win32 users should try to grab the pre-release and tell me if it works. *** You can install it with: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ >From EITHER win32 or any other platform

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