similar to: Mongrel 0.3.13.4 Pre-Release -- All Fixed Up Now

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

Whilst monitoring my host I noticed that there were three mongrel_rails processes running for a single (non mongrel_clustered) application. Is this normal? Do the processes share the memory top indicates they''re each using? Cheers, -- Dave Murphy (Schwuk) http://schwuk.com

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

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:

Hi there I have a rails application that has been deployed with mongrel_cluster. My application contains a model "Cluster.rb" and now I run into namespacing problems when accessing the Cluster class (the Mongrel:Cluster module get''s to try to resolve method calls which leads to a embarrassing NoMethodFound errors) I have started renaming my model, but I wonder what the

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

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/

I''m using the instructions from http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/to configure mongrel_cluster with apache mod_proxy_balancer. Everything works fine, except when I try to link to a pdf file to be opened in a new window, it displays the contents of the pdf as text instead of opening it as a pdf document through Acrobat.

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 list, Some time ago I was looking for apache (as non balanced proxy) + mongrel configurations. Almost everybody seemed to use similar approaches (one of these could be found @ mongrel.rubygorge.org docs) with mod_rewrite. I don''t use proxy_balancer because I don''t need it at the moment (my site has pretty low traffic). This is apache configuration that I''m using

Hi all, If you are using Pound / Pen or another load balancer, I believe you should read this: http://blog.teksol.info/articles/2006/08/25/subversion-metadata-exposure-on-mongrel My article refers to Dan Benjamin''s http://hivelogic.com/articles/2006/04/30/preventing_svn_exposure My point is that even though we are preventing Apache from serving anything except a select few file

Hi *, What''s the best way to find out on which port mongrel is running from within Rails? I have a cluster of mongrels behind a balancer (Pen) behind a webserver (Apache). In Rails, request.port return 80 and request.env[''SERVER_PORT''] returns 3000 (the port of Pen) Any ideas? Cheers, Max

Recently while i turned on USR1 debugging...mongrel running behind Apache2.2threw following debugging messages: Thu Sep 07 15:58:30 IST 2006: 0 threads sync_waiting for /charts/%5EBSESN, 1 still active in mongrel. Thu Sep 07 15:58:40 IST 2006: 0 threads sync_waiting for /images/tab_but_normal1.png, 3 still active in mongrel. Thu Sep 07 15:58:40 IST 2006: 0 threads sync_waiting for

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

Hello, I''m experiencing a strange, but very bad behavior with Mongrel 0.3.13.4 and Pound 1.8. Every 6 hours or so one of our nine (not consistent on which one) application servers ( each one running several mongrel processes ) will start leaving lots of socket connections with pound open. This leads to "Too many open files" errors. I''ve set pound to close connections

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

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

Hey all - I''ve got a question that I haven''t seen addressed anywhere and was wondering if anyone has put any thought into it or not... Here''s my setup... I have several *small* sites running apache/mongrel. Each has a single mongrel instance. Most don''t get any traffic (no one reads my blog :). And I was thinking, I could host a couple of more

We have been searching for a Rails deployment architecture which works for us for some time. We''ve recently moved from Apache 1.3 + FastCGI to Apache 2.2 + mod_proxy_balancer + mongrel_cluster, and it''s a significant improvement. But it still exhibits serious performance problems. We have the beginnings of a fix that we would like to share. To illustrate the problem, imagine a