similar to: Mongrel setting with Mysql error

I''m on a Win2K server environnement running ruby 1.8.5 and mongrel I''ve followed the tutorial and everything went fine until I start the service... Here is the output I''m getting : C:\ruby\bin??>mongrel_rails service::start -N inventaire One moment, start pending One moment, stopped One moment, stopped One moment, stopped One moment, stopped One moment, stopped

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

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

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

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/

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

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

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 -

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

I have a small intranet app with only 20 or so users. I''m currently using lighttpd w/ssl for production and mongrel for dev. I don''t think Mongrel supports ssl, but what is the easiest front-end to put in front of it? Pound? Thanks Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century

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

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

I''ve moved an application that was running under apache2/fcgi to apache2/mongrel(mod_proxy). under the original setup i had no problems with sessions. now under mongrel, the users are experiencing application errors. after looking at the logs, I am seeing that a piece of code that relies on a session variable is what is causing the error. It seems that the session variable no longer

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

Hi all, I just wanted to let you know that I built some Debian (Sarge) packages to allow an apt-get only installation of Mongrel, Ruby and friends. Also contained is an init script that is capable of managing multiple applications. Support for the Pen load balancer is also included. More info can be found there:

Am i wrong or do ActiveRecord observers not work in mongrel? Is there a work around for this? I am 100% sure of this because in my observer i put raise "whatever". Whenever I try update the model using the mongrel server I get a successful save. If I do it in webrick I get an exception raised. Any ideas what I should do? Because webrick is pretty annoying to work with. Thank

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