similar to: Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem

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

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, This is a short announce to get people to try the 0.3.13.4 pre-release with their applications. This release features a few things that folks have asked for, and a backport of an enhancement from the 0.4 release coming later. The features are: 1) A new --prefix command line option for people who want to mount their rails app at a different base URI. Thanks to Scott for the

This patch: - adds --prefix option to service::install in mongrel-service plugin - fixes bug with config values merging in the service - enables gemplugins in the service. Questions: - why the load_plugins command was commented out? It seems working for me. - why bin/mongrel_rails_service and bin/mongrel_rails_svc still in the main package? - a lot of code is duplicated in both versions

I''m running a Rails (r4720) app on OS X 10.4.6. Mongrel 0.3.13.3 works perfectly for me. Mongrel 0.3.13.4, not so much. Redirects don''t work, for one thing. This rails code : redirect_to :action => ''login'' correctly redirects me on 0.3.13.3. Here''s the header I get back : HTTP/1.1 302 Moved Temporarily Content-Length: 93 Connection: close

Hello Folks, After all the troubles people have had with Debian I realize that what I''ve done still isn''t enough for smooth sailing. I''m now going to hold back the 0.3.13.4 release in order to put an end to the Debian problem once and for all. I''m currently planning the following changes: 1) Specific documentation for Debian. Debian will become the only

Hi Everyone, Just want to get out another ping on the Mongrel pre-release saga. I''ve updated a bunch of the documentation to include documents people have donated and to beef up the FAQ for most of the questions people have asked over the past month. INSTALL gem install mongrel --source=http://mongrel.rubyforge.org/releases/ CHANGES * Fixed memory leak by switching to Sync rather

Hi, I wanted to set port in config file (via mongrel_rails -C config/config.yaml), and it seems to not take it into account. I''ve looked into the code, (line 58), and it reads: settings = conf.merge(settings) Now settings contain all the possible (important) keys (possibly with nil values, line 49, and lib/mongrel/command.rb, line 46) so everything from conf get overwritten with

So, do these new shiny 0.3.13.4 releases have the previously mentioned upload progress stuff baked in and ready to use? H

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

upgraded to 0.3.13.4 this morning in order to correct the above titled problem but mongrel is still not writing the pid file when starting with a config file verified i am running 03.13.4 with --version if i run this command: mongrel_rails start -p 3000 -e production -d --user mongrel --group webdev mongrel DOES create the pid file if i run the same, and include -G config/mongrel.conf, the

Hi, why are the gemplugins commented out in mongrel_service? What was the problem with them? I''m curiuos because I''ve used them without problems since the revision 338 (-win32 suffix patch, 31/08). However, my site is a small internal one, so it doesn''t mean any heavy testing. Jano

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

Hi! I am new to Mongrel but really like it so far. We''ve been running a single instance for our test server for about a week now. When one of our editors accesses the site, they receive a blank white page in Firefox and/or IE6/Win. In Mongrel logs we see this: Wed Aug 09 16:25:30 PDT 2006: BAD CLIENT (192.168.2.42): Invalid HTTP format, parsing fails. Wed Aug 09 16:25:31 PDT

Hey Folks, I''ve been rather absent lately, but I now have this week slated for full-time Mongrel development. The goal is to get a few big fixes into 0.3.13.4 and release that, and then get a pre-release of 0.4 out for folks to test against. Please make sure you put any outstanding bugs into: http://rubyforge.org/tracker/?atid=5145&group_id=1306&func=browse And any feature

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

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby

Hi All/Zed, win32 : Is there an Installer/setup for Mongrel along with rails(1.1.6 security patches included) ? Thank you, BR, ~A -----Original Message----- From: Zed Shaw [mailto:zedshaw at zedshaw.com] Sent: Friday, August 11, 2006 11:59 AM To: mongrel-users at rubyforge.org Cc: ruby-talk ML; rails at lists.rubyonrails.org Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- PID Files

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 been running a proxied mongrel-hosted app behind apache 2.0 (don''t need clustering) for several months, and loving it. In that instance, I am proxying the root of the virtual host to mongrel. I am now in a situation where I need to proxy a directory name to mongrel for a new application, and not having any success. I saw Zed''s mention of the --prefix option in 0.3.13.4,