similar to: [Mongrel?] Reload on file upload stalls process

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

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

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

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

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

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

I was able to find some information about this in the list archives, but it ended with a possible patch being submitted for Mongrel. I tried to follow a few of the instructions, but I''m still kind of stuck, since I''m not sure if what I''m seeing is the proper results. I have an application running on a cluster of mongrel servers, which is behind pen, which in turn is

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 One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

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

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

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

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

When developing applications, Webrick will automatically reload controllers, models, etc. if the source changes. For obvious reasons, it doesn''t do this for plugins, which makes it a pain to develop said plugins. I was hoping Mongrel might have some facility to say "watch this directory too and reload any changes". Obviously, re-init''ing all plugins would be

We have a Centos server with a number of virtual hosts, and my rails app runs under one of those virtual hosts using mongrel_rails. The app lives in /home/mydomain/railsapp where /home/mydomain/railsapp/public is the rails root. It runs under mongrel on port 8008, so to get to it users invoke the url http://www.mydomain.com:8008/ - all is fine to this point. Now I have some users whose

Hi all, I''ve been spending quite a lot of time trying to install a decent RoR server on my dedicated server (Ubuntu 6.06 LTS), and now, everything works. However, the performances are not really what I had expected... I would like to know what you think about it. Here is my config: 2GHz VIA proc, 1Gb RAM, SATA-II HD. I have apt-got ruby 1.8.4, mysql5 and installed rails 1.1.4 by

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