similar to: The Debian Plan

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 Folks, I''ve been getting reports of people with serious stability problems in Mongrel. These problems go away instantly when they remove ruby-sendfile. If your mongrel starts up saying that you have "sendfile installed" and that it is using it then **you are wrong**. Remove the gem and don''t use it. I''ll be investigating why it doesn''t really

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

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:

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

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

Hi mongrel users! I just posted a bad-ass capistrano file that automates *everything* for setting up an apache2+mod_proxy_balancer and mongrel+mongrel_cluster -- including apache2 setups. It''s based off Coda Hale''s guide and all Bradley''s work at fluxura and RailsMachine (thanks Coda and Bradley!). It''s, well, bad-ass, if I must say so myself. My favorite

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

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

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

I would like first to introduce my self to the community. I am Steve Beyer and I am interested in learning Ruby, ROR, and how to set up a production server. I am going to use OSX for my client/developement system but I would like to get some advice on what operating system you would recommend for a production server. I want to use Mongrel to start and then move up the ladder as my

Hello all, My Rails app is logging some rather strange requests: Processing StoreController#index (for ::1 at 2006-07-03 13:18:48) [GET] Session ID: ed5e2a0e5b4b9290835a969cdd749e6e Parameters: {"action"=>"index", "controller"=>"store"} Completed in 0.08174 (12 reqs/sec) | Rendering: 0.07951 (97%) | DB: 0.00000 (0%) | 200 OK [http://127.0.0.1/]

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

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

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

I followed the tutorial from Coda Hale[1] on setting up Mongrel/Mongrel_cluster and Apache to move away from my current Apache+FastCGI setup. The mongrels are all working fine, and Apache is proxying all dynamic requests through to the cluster using proxy balance. Strange thing is now, that all my images in public/images aren''t loading at all, if I access them directly I just get a