Directory Listing

From maurizio at gmail.com Tue Aug 1 05:30:29 2006 From: maurizio at gmail.com (Maurizio Balestrieri) Date: Tue, 1 Aug 2006 11:30:29 +0200 Subject: [Mongrel] Mongrel crash Message-ID: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> Hi. A mongrel/rails installation (proxyed through apache) is crashing for some reason with the following error found in the mongrel.log: ERROR: meta.c (179): wmf_header_read: this isn't a wmf file /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i386-linux] Fedora 5 mongrel: 0.3.13.3 Apache/2.2.0 Any ideads? TIA. --M From pedro at pedrocr.net Tue Aug 1 05:40:07 2006 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte-Real?=) Date: Tue, 1 Aug 2006 10:40:07 +0100 Subject: [Mongrel] Mongrel crash In-Reply-To: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> References: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> Message-ID: <62e8012c0608010240l4d52b1e1x93aa8e0009bd1663@mail.gmail.com> On 8/1/06, Maurizio Balestrieri wrote: > Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn't a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > > Fedora 5 > mongrel: 0.3.13.3 > Apache/2.2.0 > > Any ideads? TIA. If ruby is crashing it's probably a bug in the C extension it's using. Check where that meta.c is from. Seems to be something for video files? WMF? Pedro. From lapomme00 at gmail.com Tue Aug 1 05:47:36 2006 From: lapomme00 at gmail.com (Brett Walker) Date: Tue, 1 Aug 2006 17:47:36 +0800 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> References: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> Message-ID: On 7/31/06, Dave Murphy wrote: > I've got a brief guide here (must get around to writing it up properly): > > http://schwuk.com/articles/2006/06/13/hosting-rails-applications-with-mongrel-apache-2-mod_proxy-on-debian-stable > > You will need a load balancer if you're not using Apache 2.2. Dave, thanks for the pointer. This will help. It looks like you're running only one Mongrel instance, is that right? Cheers, Brett From jason.young at eXtension.org Tue Aug 1 08:11:03 2006 From: jason.young at eXtension.org (Jason Young) Date: Tue, 1 Aug 2006 08:11:03 -0400 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: References: Message-ID: <94859C73-B65E-4C9B-AE9E-C2857FFC44B2@eXtension.org> On Jul 30, 2006, at 11:36 PM, Brett Walker wrote: > Any news on the Apache Best Practice Deployment instructions? I'm > getting ready to set up a production server, and would prefer to use > Apache and Mongrel/Cluster. Don't think I'll be able to get the > latest Apache though. Do I have to proxy through Pound or something > to handle multiple mongrel instances? Any pointers? I basically do the same that Dave did - actually - I just basically do the same thing as: http://mongrel.rubyforge.org/docs/mongrel_cluster.html basically for the init script and configuration file-based start/stop. And: ProxyPass / http://127.0.0.1:mongrelport/ ProxyPassReverse / http://127.0.0.1:mongrelport/ in the configuration file for each Vhost I'm running on the box that Apache and the Mongrel+Rails app is located at, and where mongrelport corresponds to the configuration for mongrel+mongrel_cluster ( Where X depends on which port I defined in the yml file mongrel_cluster) It actually just turns out to be *that* simple. (simple enough that I'm perpetually worried I completely missed something) I'm using Red Hat's Apache 2 distribution (actually the beta stack version: 2.0.55) Jason -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jason Young -- Systems Manager, eXtension http://about.extension.org/wiki/Jason_Young ______________________________________ From jason.young at eXtension.org Tue Aug 1 08:12:15 2006 From: jason.young at eXtension.org (Jason Young) Date: Tue, 1 Aug 2006 08:12:15 -0400 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> References: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> Message-ID: <7514A96F-1AB1-4781-8F46-26A04C376E5B@eXtension.org> On Jul 31, 2006, at 3:21 AM, Dave Murphy wrote: > You will need a load balancer if you're not using Apache 2.2. Why exactly? I have relatively low traffic sites, but I'm not load- balancing - and as far as I know (which is one of the biggest self- lies in system administration I know) - I'm not having any delivery problems. At what traffic point ls LB really necessary? Jason -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jason Young -- Systems Manager, eXtension http://about.extension.org/wiki/Jason_Young ______________________________________ From me at seebq.com Tue Aug 1 08:50:25 2006 From: me at seebq.com (Charles Brian Quinn) Date: Tue, 1 Aug 2006 08:50:25 -0400 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <7514A96F-1AB1-4781-8F46-26A04C376E5B@eXtension.org> References: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> <7514A96F-1AB1-4781-8F46-26A04C376E5B@eXtension.org> Message-ID: <3a2de0cd0608010550k31359d8dx9d2b8db31cd4605c@mail.gmail.com> I would assume two requests coming in at the same time would really be the first point you would consider getting a load balancer in some form or fashion. If you have a lot of long web requests (searches, big calculations, etc.) you tie up the web request for any users. Of course, if the web request completes in a matter of milleseconds, you've made your user wait milliseconds. Probably not a big deal. Load Balancing has the connotation of requiring Big Hardware, but can be as simple as Apache's mod_proxy_balancer looking at incoming requests and deciding which mongrel instance in a mongrel_cluster to route to. I personally have 2 instances running on several low traffic sites, and you can see in the Apache built in mod_proxy_balancer manager screen that the 2nd one hardly ever kicks in. There are some most excellent docs that even tell you how to mod_deflate and have the Apache instance serve up static content (one thing that mongrel does well, but not as well as it serves up ruby) and configure a 3 mongrel_cluster setup. Coda Hale's comes to mind: http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ Only using httperf or ab or siege or anything to simulate the kind of traffic you expect will tell you if you need a load-balancer. I wouldn't add one before at least doing that. On a side note, if you do have long running web requests, might I suggest using backgrounDRb to free up the web request. Cheers, -- Charles Brian Quinn self-promotion: www.seebq.com Highgroove Studios: www.highgroove.com Slingshot Hosting: www.slingshothosting.com On 8/1/06, Jason Young wrote: > > On Jul 31, 2006, at 3:21 AM, Dave Murphy wrote: > > > > You will need a load balancer if you're not using Apache 2.2. > > Why exactly? I have relatively low traffic sites, but I'm not load- > balancing - and as far as I know (which is one of the biggest self- > lies in system administration I know) - I'm not having any delivery > problems. At what traffic point ls LB really necessary? > > Jason > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Jason Young -- Systems Manager, eXtension > http://about.extension.org/wiki/Jason_Young > ______________________________________ > > > > > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From josh at besquared.net Tue Aug 1 15:01:45 2006 From: josh at besquared.net (Josh Ferguson) Date: Tue, 01 Aug 2006 14:01:45 -0500 Subject: [Mongrel] Mongrel crash In-Reply-To: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> References: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> Message-ID: <44CFA519.7070205@besquared.net> Maurizio I'm fighting with the same problems on a production machine. They are with radiant, and most likely with caching on RHEL/FC with the apache 2.2/mongrel 0.3.13 combo. Are you running this radiant on a virtual server or a machine that is all your own? Josh Maurizio Balestrieri wrote: > Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn't a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > > Fedora 5 > mongrel: 0.3.13.3 > Apache/2.2.0 > > Any ideads? TIA. > > --M > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From josh at besquared.net Tue Aug 1 15:03:17 2006 From: josh at besquared.net (Josh Ferguson) Date: Tue, 01 Aug 2006 14:03:17 -0500 Subject: [Mongrel] Mongrel crash In-Reply-To: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> References: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> Message-ID: <44CFA575.5010408@besquared.net> Maurizio I'm fighting with similar problems with radiant on a production machine where mongrel segfaults for various reasons at different times. It seems random to me so my guess it that the problem is with caching on RHEL/FC with the apache 2.2/mongrel 0.3.13 combo which is what I'm running. Are you running this radiant on a virtual server or a machine that is all your own? Josh Maurizio Balestrieri wrote: > Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn't a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > > Fedora 5 > mongrel: 0.3.13.3 > Apache/2.2.0 > > Any ideads? TIA. > > --M > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From maurizio at gmail.com Tue Aug 1 14:26:57 2006 From: maurizio at gmail.com (Maurizio Balestrieri) Date: Tue, 1 Aug 2006 20:26:57 +0200 Subject: [Mongrel] Mongrel crash In-Reply-To: <44CFA519.7070205@besquared.net> References: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> <44CFA519.7070205@besquared.net> Message-ID: <1c7fecb90608011126le4f3e56m23240f1e2f470317@mail.gmail.com> On 8/1/06, Josh Ferguson wrote: > They are with radiant, and most likely with caching on RHEL/FC with the > apache 2.2/mongrel 0.3.13 combo. Are you running this radiant on a > virtual server or a machine that is all your own? Josh, It's a VPS on rimuhosting with 256MB RAM, and the same system software stack you mentioned (including radiant). From zedshaw at zedshaw.com Tue Aug 1 15:03:50 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Tue, 01 Aug 2006 12:03:50 -0700 Subject: [Mongrel] Mongrel Week! Message-ID: <1154459030.9131.13.camel@localhost.localdomain> 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 requests into: http://rubyforge.org/tracker/?atid=5148&group_id=1306&func=browse So that I can triage and put them into the right versions. Finally, everyone please try out the pre-release (especially if you get segfaults): sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And tell me how it works for you. Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From gethemant at gmail.com Tue Aug 1 16:32:32 2006 From: gethemant at gmail.com (hemant) Date: Wed, 2 Aug 2006 02:02:32 +0530 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) Message-ID: 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 here and there. MissingSourceFile no such file to load -- /home/foo_fighter/public_html/foobar/config/routes.rb RAILS_ROOT: /home/foo_fighter/public_html/foobar/config/.. Application Trace | Framework Trace | Full Trace /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.1/lib/action_controller/routing.rb:574:in `reload' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:67:in `prepare_application' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:37:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/rails.rb:73:in`process' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:551:in`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:550:in`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:636:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:636:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:625:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:956:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:955:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:127:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in`run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 /usr/bin/mongrel_rails:18 /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.1/lib/action_controller/routing.rb:574:in `reload' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:67:in `prepare_application' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:37:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/rails.rb:73:in`process' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:551:in`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:550:in`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:636:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:636:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:625:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:956:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:955:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:127:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in`run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.1/lib/action_controller/routing.rb:574:in `reload' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:67:in `prepare_application' /usr/lib/ruby/gems/1.8/gems/rails-1.1.2/lib/dispatcher.rb:37:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/rails.rb:73:in`process' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:551:in`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:550:in`process_client' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:636:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:636:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:625:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:956:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:955:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:127:in `run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in`run' /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 /usr/bin/mongrel_rails:18 This error occured while loading the following files: /home/foo_fighter/public_html/foobar/config/../config/routes.rb -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060802/de6dfbc2/attachment.html From carl.lerche at verizon.net Tue Aug 1 17:35:38 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Tue, 01 Aug 2006 14:35:38 -0700 Subject: [Mongrel] Mongrel Week! In-Reply-To: <1154459030.9131.13.camel@localhost.localdomain> References: <1154459030.9131.13.camel@localhost.localdomain> Message-ID: <0994EF57-DE62-44BA-ABFD-BC4B2BCFC6A8@verizon.net> Great news :) I can't wait to play with 0.4. Quick question, I believe in your last release you mentioned that the upload progress plugin was fixed? Am I remembering right or should I wait until 0.4 is out to start playing around with this? Thanks, -carl On Aug 1, 2006, at 12:03 PM, Zed Shaw wrote: > 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 requests into: > > http://rubyforge.org/tracker/?atid=5148&group_id=1306&func=browse > > So that I can triage and put them into the right versions. > > Finally, everyone please try out the pre-release (especially if you > get > segfaults): > > sudo gem install mongrel > --source=http://mongrel.rubyforge.org/releases/ > > And tell me how it works for you. > > Thanks! > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From technoweenie at gmail.com Tue Aug 1 21:35:16 2006 From: technoweenie at gmail.com (Rick Olson) Date: Tue, 1 Aug 2006 20:35:16 -0500 Subject: [Mongrel] Mongrel Week! In-Reply-To: <0994EF57-DE62-44BA-ABFD-BC4B2BCFC6A8@verizon.net> References: <1154459030.9131.13.camel@localhost.localdomain> <0994EF57-DE62-44BA-ABFD-BC4B2BCFC6A8@verizon.net> Message-ID: <48fe25b0608011835y2dd29567taf15d45b5478e066@mail.gmail.com> On 8/1/06, Carl Lerche wrote: > Great news :) > > I can't wait to play with 0.4. Quick question, I believe in your last > release you mentioned that the upload progress plugin was fixed? Am I > remembering right or should I wait until 0.4 is out to start playing > around with this? > > Thanks, > -carl It's working, but you need some javascript to get the client side stuff working. I have a sample rails project, but the important bits are javascript: http://svn.techno-weenie.net/projects/mongrel_upload_progress/ I'll work on getting some documentation written this week. I just wanted to make sure I wasn't doing anything stupid in the actual mongrel code. -- Rick Olson http://techno-weenie.net From lapomme00 at gmail.com Wed Aug 2 05:50:00 2006 From: lapomme00 at gmail.com (Brett Walker) Date: Wed, 2 Aug 2006 17:50:00 +0800 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <3a2de0cd0608010550k31359d8dx9d2b8db31cd4605c@mail.gmail.com> References: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> <7514A96F-1AB1-4781-8F46-26A04C376E5B@eXtension.org> <3a2de0cd0608010550k31359d8dx9d2b8db31cd4605c@mail.gmail.com> Message-ID: Just ran across this blog post by Ezra (from a couple months ago) that could come in handy: http://brainspl.at/articles/2006/06/12/apache2-2-vhost-template-for-mongrel-clusters Cheers, Brett From shubham.singal at gmail.com Wed Aug 2 06:38:59 2006 From: shubham.singal at gmail.com (Shubham Singal) Date: Wed, 2 Aug 2006 16:08:59 +0530 Subject: [Mongrel] Modifying Mongrel Examples Message-ID: <860243270608020338u6854b80fra709ac7e9c9b7251@mail.gmail.com> Hi, I am tryinig to work on the Mongrel examples. I am trying to modify the HttpResponse. def process(request, response) response.start do |head,out| if request.params["REQUEST_METHOD"] == OPTIONS" else end end One can detect that the request is OPTIONS like this, but how does one generate the custom response by using HttpResponse. Please help. Shubham From aidanf at gmail.com Wed Aug 2 06:47:17 2006 From: aidanf at gmail.com (Aidan Finn) Date: Wed, 2 Aug 2006 11:47:17 +0100 Subject: [Mongrel] Mongrel crashes whenever an exception is raised Message-ID: <4836d4ce0608020347t56c18ffbpa6d7cc529c4a9dd2@mail.gmail.com> Hi all, I have a rails app running on mongrel on freebsd using mongrel 0.3.13.3 with ruby 1.8.4. Mongrel dies every time the application generates an exception. I have the same setup running on a linux box without any problems. Mongrel crashes with the following error: Bus error (core dumped) And the following message in /var/log/message kernel: pid 57638 (ruby), uid 0: exited on signal 10 (core dumped) Anyone seen this before or got any idea what is causing it? cheers, AF -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060802/ce376357/attachment.html From gitte at wange.dk Wed Aug 2 08:37:52 2006 From: gitte at wange.dk (Gitte Wange) Date: Wed, 2 Aug 2006 14:37:52 +0200 Subject: [Mongrel] mongrel to execute ruby script? Message-ID: <803F9B1F-9696-491C-ABE9-4471A85BE309@wange.dk> Hello, I've spent a couple of hours now searching for (what I thought) was pretty straightforward. I'm using mongrel together with RoR and need to execute a .rb file located in my public folder (cgi style). But mongrel just can't do that out-of-the-box - or am I missing something? I really don't get how I'm supposed to configure mongrel for this task so I'm hoping to find some help here :-) Greetings, Gitte Wange -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1881 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060802/864143f8/attachment.bin From aidanf at gmail.com Wed Aug 2 09:11:26 2006 From: aidanf at gmail.com (Aidan Finn) Date: Wed, 2 Aug 2006 14:11:26 +0100 Subject: [Mongrel] Mongrel crashes whenever an exception is raised In-Reply-To: <4836d4ce0608020347t56c18ffbpa6d7cc529c4a9dd2@mail.gmail.com> References: <4836d4ce0608020347t56c18ffbpa6d7cc529c4a9dd2@mail.gmail.com> Message-ID: <4836d4ce0608020611p9f7004cv1cb0d96c9e7c0eef@mail.gmail.com> Hi all, Turns out the problem was with pthreads on freebsd. Installing ruby with pthreads disabled solved the problem. The version of ruby installed had pthreads enabled. Recent versions of the ruby freebsd port have pthreads disabled by default or else you can use the ruby18-nopthreads port. Cheers, AF On 8/2/06, Aidan Finn wrote: > > Hi all, > > I have a rails app running on mongrel on freebsd using mongrel 0.3.13.3with ruby > 1.8.4. > > Mongrel dies every time the application generates an exception. I have > the same setup running on a linux box without any problems. > > Mongrel crashes with the following error: > Bus error (core dumped) > > And the following message in /var/log/message > kernel: pid 57638 (ruby), uid 0: exited on signal 10 (core dumped) > > Anyone seen this before or got any idea what is causing it? > > > cheers, > > AF > -- ------------------------------- http://www.aidanf.net ------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060802/6d403018/attachment.html From zedshaw at zedshaw.com Thu Aug 3 02:47:08 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 02 Aug 2006 23:47:08 -0700 Subject: [Mongrel] mongrel to execute ruby script? In-Reply-To: <803F9B1F-9696-491C-ABE9-4471A85BE309@wange.dk> References: <803F9B1F-9696-491C-ABE9-4471A85BE309@wange.dk> Message-ID: <1154587628.6047.33.camel@localhost.localdomain> Yeah, Mongrel doesn't support this unless you write a Handler to do it. Take a look at the documentation on the site and if you can't figure it out then I'll help. You'll want a small mongrel.conf with code in it that makes an HttpHandler which you can pass to mongrel_rails -S. That should get you started. On Wed, 2006-08-02 at 14:37 +0200, Gitte Wange wrote: > Hello, > > I've spent a couple of hours now searching for (what I thought) was > pretty straightforward. > I'm using mongrel together with RoR and need to execute a .rb file > located in my public folder (cgi style). > > But mongrel just can't do that out-of-the-box - or am I missing > something? > I really don't get how I'm supposed to configure mongrel for this > task so I'm hoping to find some help here :-) > > Greetings, > Gitte Wange > _______________________________________________ Mongrel-users mailing list Mongrel-users at rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users From zedshaw at zedshaw.com Thu Aug 3 02:48:35 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 02 Aug 2006 23:48:35 -0700 Subject: [Mongrel] Mongrel crashes whenever an exception is raised In-Reply-To: <4836d4ce0608020611p9f7004cv1cb0d96c9e7c0eef@mail.gmail.com> References: <4836d4ce0608020347t56c18ffbpa6d7cc529c4a9dd2@mail.gmail.com> <4836d4ce0608020611p9f7004cv1cb0d96c9e7c0eef@mail.gmail.com> Message-ID: <1154587715.6047.35.camel@localhost.localdomain> Thanks Aidan, it's on the list for FAQ questions. I'll also look at why this might be. On Wed, 2006-08-02 at 14:11 +0100, Aidan Finn wrote: > Hi all, > > Turns out the problem was with pthreads on freebsd. Installing ruby > with pthreads disabled solved the problem. The version of ruby > installed had pthreads enabled. Recent versions of the ruby freebsd > port have pthreads disabled by default or else you can use the > ruby18-nopthreads port. > > Cheers, > > AF > > On 8/2/06, Aidan Finn wrote: > Hi all, > > I have a rails app running on mongrel on freebsd using mongrel > 0.3.13.3 with ruby 1.8.4. > > Mongrel dies every time the application generates an > exception. I have the same setup running on a linux box > without any problems. > > Mongrel crashes with the following error: > Bus error (core dumped) > > And the following message in /var/log/message > kernel: pid 57638 (ruby), uid 0: exited on signal 10 (core > dumped) > > Anyone seen this before or got any idea what is causing it? > > > cheers, > > > AF > > > > > -- > ------------------------------- > http://www.aidanf.net > ------------------------------- > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From schwuk at gmail.com Thu Aug 3 02:48:49 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 07:48:49 +0100 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: References: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> Message-ID: <2e60a9e60608022348y60261f2cs4c721783eee02fad@mail.gmail.com> On 01/08/06, Brett Walker wrote: > Dave, thanks for the pointer. This will help. It looks like you're > running only one Mongrel instance, is that right? Yes. Because of low memory on the host, I decided to stick with one instance. Cheers -- Dave Murphy (Schwuk) http://schwuk.com From zedshaw at zedshaw.com Thu Aug 3 02:49:38 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 02 Aug 2006 23:49:38 -0700 Subject: [Mongrel] Modifying Mongrel Examples In-Reply-To: <860243270608020338u6854b80fra709ac7e9c9b7251@mail.gmail.com> References: <860243270608020338u6854b80fra709ac7e9c9b7251@mail.gmail.com> Message-ID: <1154587778.6047.38.camel@localhost.localdomain> On Wed, 2006-08-02 at 16:08 +0530, Shubham Singal wrote: > Hi, > > I am tryinig to work on the Mongrel examples. I am trying to modify > the HttpResponse. > Like this: out.write("my stuff") That's it. The out param is just a IO object you write your response to and then Mongrel packs it up and goes. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 3 02:53:09 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 02 Aug 2006 23:53:09 -0700 Subject: [Mongrel] [WARNING] don't use ruby-sendfile Message-ID: <1154587989.6047.41.camel@localhost.localdomain> 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 work as advertised, and really it's not worth the hassle for just a 20% perf boost on static files (and ONLY static files, no other requests at all). Really, if you need fast static files use a real web server instead. Thanks! P.S. Almost through my e-mail queue. Man. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From schwuk at gmail.com Thu Aug 3 02:54:55 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 07:54:55 +0100 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <7514A96F-1AB1-4781-8F46-26A04C376E5B@eXtension.org> References: <2e60a9e60607310021o25fb8cb9qfb371b49add5e971@mail.gmail.com> <7514A96F-1AB1-4781-8F46-26A04C376E5B@eXtension.org> Message-ID: <2e60a9e60608022354o62c9e4afh91b0a91530efc9f4@mail.gmail.com> On 01/08/06, Jason Young wrote: > > You will need a load balancer if you're not using Apache 2.2. > > Why exactly? I have relatively low traffic sites, but I'm not load- > balancing - and as far as I know (which is one of the biggest self- > lies in system administration I know) - I'm not having any delivery > problems. At what traffic point ls LB really necessary? Sorry I should have qualified that with "if you want load balancing". I've avoided it due to memory constraints and have not had any real problems on a low traffic site. My rule of thumb for load balancing would be anything where it is going to cause you pain/embarassment/financial loss if a user has to wait for a unresponsive site. Cheers, -- Dave Murphy (Schwuk) http://schwuk.com From zedshaw at zedshaw.com Thu Aug 3 02:54:59 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 02 Aug 2006 23:54:59 -0700 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) In-Reply-To: References: Message-ID: <1154588099.6047.44.camel@localhost.localdomain> On Wed, 2006-08-02 at 02:02 +0530, hemant wrote: > 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 Have you solved this yet? I'm working up my bug list. Try the following things: 1) remove ruby-sendfile if you have it installed. 2) try the pre-release: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ 3) try your app with webrick and see if you get the error. 4) tell me what OS and mongrel version this happens with. sorry if you gave me this info already, i'm just whipping through my e-mail queue to catch up. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 3 02:56:19 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 02 Aug 2006 23:56:19 -0700 Subject: [Mongrel] Mongrel crash In-Reply-To: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> References: <1c7fecb90608010230t7aff2a58jd203ee23d8d49f7@mail.gmail.com> Message-ID: <1154588179.6047.46.camel@localhost.localdomain> On Tue, 2006-08-01 at 11:30 +0200, Maurizio Balestrieri wrote: > Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn't a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > Did you solve this Maurizio? Did you see a similar posting earlier about RMagick and missing LD_* configurations when run under sudo? -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From schwuk at gmail.com Thu Aug 3 02:59:02 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 07:59:02 +0100 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <94859C73-B65E-4C9B-AE9E-C2857FFC44B2@eXtension.org> References: <94859C73-B65E-4C9B-AE9E-C2857FFC44B2@eXtension.org> Message-ID: <2e60a9e60608022359u21db6640v498bb878074c813a@mail.gmail.com> On 01/08/06, Jason Young wrote: > basically for the init script and configuration file-based start/stop. I've written a howto on rolling your own init scripts for single mongrel instances: http://schwuk.com/articles/2006/06/29/daemonizing-mongrel It could easily be adapted to use config files and/or clusters. > ProxyPass / http://127.0.0.1:mongrelport/ > ProxyPassReverse / http://127.0.0.1:mongrelport/ Because I'm using a bunch of rewrites to enhance caching etc. I not using ProxyPass anymore - I just use a proxying rewrite. I'll write this up on my website as soon as I get the chance. Cheers, -- Dave Murphy (Schwuk) http://schwuk.com From zedshaw at zedshaw.com Thu Aug 3 03:08:23 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:08:23 -0700 Subject: [Mongrel] s/IF_UNMODIFIED_SINCE/IF_MODIFIED_SINCE/ ??? In-Reply-To: <4be80d840607281529u117ff35al24e690604d02c654@mail.gmail.com> References: <4be80d840607281529u117ff35al24e690604d02c654@mail.gmail.com> Message-ID: <1154588903.6047.60.camel@localhost.localdomain> On Fri, 2006-07-28 at 18:29 -0400, Tim Olsen wrote: > I've noticed in the source code that Mongrel handles the > IF_UNMODIFIED_SINCE header. I thought this rather odd, since > IF_UNMODIFIED_SINCE is generally only useful with PUT. Even more odd > is that there is no mention of IF_MODIFIED_SINCE in Mongrel which is > useful with GET (although not as useful as IF_NONE_MATCH of course). > > Is this a bug in Mongrel? Alright, I got Dan's patch in the queue and this will be fixed in the 0.3.13.4 pre-release. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From schwuk at gmail.com Thu Aug 3 03:09:53 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 08:09:53 +0100 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <94859C73-B65E-4C9B-AE9E-C2857FFC44B2@eXtension.org> References: <94859C73-B65E-4C9B-AE9E-C2857FFC44B2@eXtension.org> Message-ID: <2e60a9e60608030009t54593e2enb3c651402037f8b8@mail.gmail.com> On 01/08/06, Jason Young wrote: > ProxyPass / http://127.0.0.1:mongrelport/ > ProxyPassReverse / http://127.0.0.1:mongrelport/ > > in the configuration file for each Vhost I'm running on the box that > Apache and the Mongrel+Rails app is located at, and where mongrelport > corresponds to the configuration for mongrel+mongrel_cluster > > ( Where X depends on which port I defined in the yml file > mongrel_cluster) > > It actually just turns out to be *that* simple. (simple enough that > I'm perpetually worried I completely missed something) I think you are. My impression from reading the above is that a) your using mongrel_cluster and b) you're *not* using mod_proxy_balancer (because it's not available for Apache 2.0). If both of these are true, then all requests are being served by the first member of the mongrel_cluster - the others will never be touched. Is this the case? Cheers, -- Dave Murphy (Schwuk) http://schwuk.com From schwuk at gmail.com Thu Aug 3 03:13:37 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 08:13:37 +0100 Subject: [Mongrel] [WARNING] don't use ruby-sendfile In-Reply-To: <1154587989.6047.41.camel@localhost.localdomain> References: <1154587989.6047.41.camel@localhost.localdomain> Message-ID: <2e60a9e60608030013t4817cd5ao9faf03a62973ae78@mail.gmail.com> On 03/08/06, Zed Shaw wrote: > I've been getting reports of people with serious stability problems in > Mongrel. These problems go away instantly when they remove > ruby-sendfile. You may want to nudge Coda to update his post [1] - I'd never heard of sendfile until I read that, and it's often referred to in the community. [1] http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ Cheers, -- Dave Murphy (Schwuk) http://schwuk.com From zedshaw at zedshaw.com Thu Aug 3 03:13:56 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:13:56 -0700 Subject: [Mongrel] Getting ssl environment to mongrel from apache In-Reply-To: <1f060c4c0607251051p6259b536hf00c529dd9be0c9f@mail.gmail.com> References: <1f060c4c0607251051p6259b536hf00c529dd9be0c9f@mail.gmail.com> Message-ID: <1154589236.6047.62.camel@localhost.localdomain> On Tue, 2006-07-25 at 10:51 -0700, snacktime wrote: > I have apache 1.3 with mod_ssl in front of mongrel/rails. Apache is > setup to require client certification, and I'm trying to figure out > how to pass the ssl env variables to mongrel. Here is the apache > config to proxy requests to mongrel. I haven't tried to pass env > variables like this before so I'm not sure if it's the apache config I > have wrong, if mongrel isn't picking up the env variables I am > setting, or if it's just not possible to do what I'm trying to do. > Any guidance would be appreciated. > Did you get this working yet? -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 3 03:24:58 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:24:58 -0700 Subject: [Mongrel] Mongrel process unexpectedly dying In-Reply-To: <1200dbac0607180908o6ca23864pee88d371b7642778@mail.gmail.com> References: <1200dbac0607180908o6ca23864pee88d371b7642778@mail.gmail.com> Message-ID: <1154589898.6047.70.camel@localhost.localdomain> On Tue, 2006-07-18 at 12:08 -0400, Dallas DeVries wrote: > 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. > BTW, did you have ruby-sendfile installed at all? -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From schwuk at gmail.com Thu Aug 3 03:26:08 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 08:26:08 +0100 Subject: [Mongrel] Mongrel processes Message-ID: <2e60a9e60608030026p6314477j787eae2dd0bfdb32@mail.gmail.com> 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 From zedshaw at zedshaw.com Thu Aug 3 03:26:52 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:26:52 -0700 Subject: [Mongrel] FF1.0 + Prototype Ajax not working in 0.3.13.x In-Reply-To: <64e1f5070607162218k68cf80cakdb27ef7a25765b84@mail.gmail.com> References: <64e1f5070607162218k68cf80cakdb27ef7a25765b84@mail.gmail.com> Message-ID: <1154590012.6047.74.camel@localhost.localdomain> On Mon, 2006-07-17 at 13:18 +0800, choonkeat wrote: > Hi guys, > > I have a funny problem that only occurs in FF1.0.x but works fine and > dandy in FF1.5. I'd thought its me screwing up with the JS... but even > this "What time is it" doesn't work with until I downgrade to Mongrel > 0.3.12.4. I don't like/use FF1.0 too.. but too bad for me... > > Apparently stuff like Rails' link_to_remote or plain new Ajax.request > doesn't work when running with Mongrel 0.3.13.x. Luckily helpful error > messages introduced in 0.3.13.4 solved my mystery: > > BAD CLIENT (127.0.0.1): Sent body size 2 but declared > Content-Length: 0 > > Anyways, to have a (Firefox 1.0+Prototype)-friendly Mongrel, just > change line 203 to: > > if remain == 0 || remain < 0 > > In case anyone else has problems. Hopefully other parts of the sky > don't fall due to this. > Hey, could you file this in the bug tracker so I can work it? Thanks. I'd do it but I'm busy :-) Zed From zedshaw at zedshaw.com Thu Aug 3 03:31:47 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:31:47 -0700 Subject: [Mongrel] crashing mongrel In-Reply-To: References: Message-ID: <1154590307.6047.78.camel@localhost.localdomain> Ben, Did you by chance have ruby-sendfile installed? I'm tracking down a bug that looks like this. Zed On Mon, 2006-07-10 at 13:57 -0500, Ben Moore wrote: > 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 /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in > `join' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:982:in > `join' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:136:in > `run' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > `run' > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > from /usr/local/bin/mongrel_rails:18 > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From zedshaw at zedshaw.com Thu Aug 3 03:34:34 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:34:34 -0700 Subject: [Mongrel] Charset issue In-Reply-To: <082942B9-C091-4809-B6E8-668BA0D0E61B@flydown.org> References: <20060703094601.GY5504@suse.de> <082942B9-C091-4809-B6E8-668BA0D0E61B@flydown.org> Message-ID: <1154590474.6047.80.camel@localhost.localdomain> Did you resolve this Michele? If not could you post it as a bug. Please include: 1) OS used. 2) browser used. 3) mongrel version. 4) important log snippets from mongrel_rails start -e production -B (in log/mongrel_debug). Thanks. On Mon, 2006-07-03 at 12:07 +0200, Michele wrote: > Now, it's serving the right content-type (both HTML and HTTP), but > still not working. > > - michele > > On Jul 3, 2006, at 11:46 , Marcus Rueckert wrote: > > > On 2006-07-03 11:29:32 +0200, Michele wrote: > >> I've included the right content-type in the HTML and both Lighty > >> +Fastcgi and Webrick have no problem with them. > > > > set the correct HTTP header. > > the http header overrules the HTML header. > > > > darix > > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From zedshaw at zedshaw.com Thu Aug 3 03:36:38 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:36:38 -0700 Subject: [Mongrel] Mongrel processes In-Reply-To: <2e60a9e60608030026p6314477j787eae2dd0bfdb32@mail.gmail.com> References: <2e60a9e60608030026p6314477j787eae2dd0bfdb32@mail.gmail.com> Message-ID: <1154590598.6047.82.camel@localhost.localdomain> On Thu, 2006-08-03 at 08:26 +0100, Dave Murphy wrote: > 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? If it's linux then go ask the linux kernel guys why they show processes that way. :-) Otherwise, double check that you really are running just one. Use lsof -i -P | grep ruby to get a better picture. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 3 03:40:32 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 00:40:32 -0700 Subject: [Mongrel] [WARNING] don't use ruby-sendfile In-Reply-To: <2e60a9e60608030013t4817cd5ao9faf03a62973ae78@mail.gmail.com> References: <1154587989.6047.41.camel@localhost.localdomain> <2e60a9e60608030013t4817cd5ao9faf03a62973ae78@mail.gmail.com> Message-ID: <1154590832.6047.89.camel@localhost.localdomain> On Thu, 2006-08-03 at 08:13 +0100, Dave Murphy wrote: > On 03/08/06, Zed Shaw wrote: > > I've been getting reports of people with serious stability problems in > > Mongrel. These problems go away instantly when they remove > > ruby-sendfile. > > You may want to nudge Coda to update his post [1] - I'd never heard of > sendfile until I read that, and it's often referred to in the > community. > > [1] http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ Thanks, contacted him. That seems to be the source. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From gethemant at gmail.com Thu Aug 3 04:13:11 2006 From: gethemant at gmail.com (hemant) Date: Thu, 3 Aug 2006 13:43:11 +0530 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) In-Reply-To: <1154588099.6047.44.camel@localhost.localdomain> References: <1154588099.6047.44.camel@localhost.localdomain> Message-ID: Thanks for following up. I am on Ubuntu server edition, and yes i have sendfile installed. But removing it may create some performance problem won't it? As for the mongrel version, you can already see in the earlier message, it is 0.3.13. I was earlier running, apache2 with fcgi and didn't face this issue. I am myself trying to investigate this problem. On 8/3/06, Zed Shaw wrote: > > On Wed, 2006-08-02 at 02:02 +0530, hemant wrote: > > 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 > > Have you solved this yet? I'm working up my bug list. > > Try the following things: > > 1) remove ruby-sendfile if you have it installed. > 2) try the pre-release: sudo gem install mongrel > --source=http://mongrel.rubyforge.org/releases/ > 3) try your app with webrick and see if you get the error. > 4) tell me what OS and mongrel version this happens with. > > sorry if you gave me this info already, i'm just whipping through my > e-mail queue to catch up. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060803/5e8fd3d0/attachment.html From kraemer at webit.de Thu Aug 3 05:10:56 2006 From: kraemer at webit.de (Jens Kraemer) Date: Thu, 3 Aug 2006 11:10:56 +0200 Subject: [Mongrel] Mongrel and Apache docs? In-Reply-To: <2e60a9e60608022359u21db6640v498bb878074c813a@mail.gmail.com> References: <94859C73-B65E-4C9B-AE9E-C2857FFC44B2@eXtension.org> <2e60a9e60608022359u21db6640v498bb878074c813a@mail.gmail.com> Message-ID: <20060803091056.GN26391@cordoba.webit.de> On Thu, Aug 03, 2006 at 07:59:02AM +0100, Dave Murphy wrote: > On 01/08/06, Jason Young wrote: > > basically for the init script and configuration file-based start/stop. > > I've written a howto on rolling your own init scripts for single > mongrel instances: > > http://schwuk.com/articles/2006/06/29/daemonizing-mongrel > > It could easily be adapted to use config files and/or clusters. > > > ProxyPass / http://127.0.0.1:mongrelport/ > > ProxyPassReverse / http://127.0.0.1:mongrelport/ > > Because I'm using a bunch of rewrites to enhance caching etc. I not > using ProxyPass anymore - I just use a proxying rewrite. I'll write > this up on my website as soon as I get the chance. I already did so some time ago (for Apache 2.0): http://www.jkraemer.net/articles/2006/07/07/mongrel-apache-and-rails-on-debian-sarge In the second half of the post, below Configuration / Apache there's a snippet of Apache config like I use it in my VirtualHost sections. It uses rewrite rules for serving static files via Apache and sends all remaining requests to localhost:8001. What actually listens on that port doesn't matter in terms of Apache configuration - it might be some load balancer like Pen, or just a single Mongrel instance. Jens -- webit! Gesellschaft f?r neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Kr?mer kraemer at webit.de Schnorrstra?e 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 From schwuk at gmail.com Thu Aug 3 05:12:42 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 10:12:42 +0100 Subject: [Mongrel] Mongrel processes In-Reply-To: <1154590598.6047.82.camel@localhost.localdomain> References: <2e60a9e60608030026p6314477j787eae2dd0bfdb32@mail.gmail.com> <1154590598.6047.82.camel@localhost.localdomain> Message-ID: <2e60a9e60608030212k3b20acdfx963c3c6b57c9535c@mail.gmail.com> > Otherwise, double check that you really are running just one. Use lsof > -i -P | grep ruby to get a better picture. Running: $ sudo lsof -i -P | grep ruby ...gave me nothing. With a slight twist: $ sudo lsof -i -P | grep mongrel mongrel_r 7657 root 3u IPv4 9018835 TCP *:3000 (LISTEN) mongrel_r 7658 root 3u IPv4 9018835 TCP *:3000 (LISTEN) mongrel_r 7659 root 3u IPv4 9018835 TCP *:3000 (LISTEN) And finally: $ sudo ps ax | grep mongrel Warning: bad syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html 7657 ? S 490:07 /usr/bin/ruby1.8 /usr/bin/mongrel_rails start -c /home/schwuk/typo -e production -p 3000 -d 7658 ? S 0:00 /usr/bin/ruby1.8 /usr/bin/mongrel_rails start -c /home/schwuk/typo -e production -p 3000 -d 7659 ? S 0:01 /usr/bin/ruby1.8 /usr/bin/mongrel_rails start -c /home/schwuk/typo -e production -p 3000 -d 28223 pts/0 S+ 0:00 grep mongrel Cheers, -- Dave Murphy (Schwuk) http://schwuk.com From kraemer at webit.de Thu Aug 3 05:28:48 2006 From: kraemer at webit.de (Jens Kraemer) Date: Thu, 3 Aug 2006 11:28:48 +0200 Subject: [Mongrel] Mongrel processes In-Reply-To: <2e60a9e60608030212k3b20acdfx963c3c6b57c9535c@mail.gmail.com> References: <2e60a9e60608030026p6314477j787eae2dd0bfdb32@mail.gmail.com> <1154590598.6047.82.camel@localhost.localdomain> <2e60a9e60608030212k3b20acdfx963c3c6b57c9535c@mail.gmail.com> Message-ID: <20060803092848.GB21809@cordoba.webit.de> On Thu, Aug 03, 2006 at 10:12:42AM +0100, Dave Murphy wrote: [..] > And finally: > > $ sudo ps ax | grep mongrel > Warning: bad syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html > 7657 ? S 490:07 /usr/bin/ruby1.8 /usr/bin/mongrel_rails > start -c /home/schwuk/typo -e production -p 3000 -d > 7658 ? S 0:00 /usr/bin/ruby1.8 /usr/bin/mongrel_rails > start -c /home/schwuk/typo -e production -p 3000 -d > 7659 ? S 0:01 /usr/bin/ruby1.8 /usr/bin/mongrel_rails > start -c /home/schwuk/typo -e production -p 3000 -d > 28223 pts/0 S+ 0:00 grep mongrel Seems to depend on the exact kernel you use - or on the Mongrel version. On a 2.6.16-2-xen-686 kernel running 0.3.13.2 I get similar output like the above - 3 processes per Mongrel instance. On a 2.6.8-3-k7 kernel running 0.3.13.4 it's only one entry per Mongrel instance. I don't think there's any difference in terms of memory consumption, imho it's just a difference in how ps shows processes / threads. I remember that back in my old Java days on some systems (2.4 kernels) ps showed each single Java thread, that behaviour disappeared with 2.6 kernels - then ps showed only one process per running application, regardless of any threads it has spawned. Jens -- webit! Gesellschaft f?r neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Kr?mer kraemer at webit.de Schnorrstra?e 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 From jamesludlow at gmail.com Thu Aug 3 08:53:54 2006 From: jamesludlow at gmail.com (James Ludlow) Date: Thu, 3 Aug 2006 07:53:54 -0500 Subject: [Mongrel] [WARNING] don't use ruby-sendfile In-Reply-To: <1154587989.6047.41.camel@localhost.localdomain> References: <1154587989.6047.41.camel@localhost.localdomain> Message-ID: On 8/3/06, Zed Shaw wrote: > I'll be investigating why it doesn't really work as advertised, and > really it's not worth the hassle for just a 20% perf boost on static > files (and ONLY static files, no other requests at all). Really, if you > need fast static files use a real web server instead. In my case, most of my content is static and the performance boost is very significant. I'm using file_column to manage the uploads, so using a "real web server" around this is just a pain. I haven't noticed any stability problems at all either. Is this something that people notice right away (perhaps due to something else in their environment), or will it sneak up on me? -- James From schwuk at gmail.com Thu Aug 3 09:25:50 2006 From: schwuk at gmail.com (Dave Murphy) Date: Thu, 3 Aug 2006 14:25:50 +0100 Subject: [Mongrel] Mongrel processes In-Reply-To: <20060803092848.GB21809@cordoba.webit.de> References: <2e60a9e60608030026p6314477j787eae2dd0bfdb32@mail.gmail.com> <1154590598.6047.82.camel@localhost.localdomain> <2e60a9e60608030212k3b20acdfx963c3c6b57c9535c@mail.gmail.com> <20060803092848.GB21809@cordoba.webit.de> Message-ID: <2e60a9e60608030625k3323e9f6p9da66ae44349253e@mail.gmail.com> On 03/08/06, Jens Kraemer wrote: > I don't think there's any difference in terms of memory consumption, > imho it's just a difference in how ps shows processes / threads. I > remember that back in my old Java days on some systems (2.4 kernels) ps > showed each single Java thread, that behaviour disappeared with 2.6 > kernels - then ps showed only one process per running application, > regardless of any threads it has spawned. I suspected it was threads rather than processes, but I wanted to confirm it. Cheers, -- Dave Murphy (Schwuk) http://schwuk.com From gethemant at gmail.com Thu Aug 3 10:08:58 2006 From: gethemant at gmail.com (hemant) Date: Thu, 3 Aug 2006 19:38:58 +0530 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) In-Reply-To: References: <1154588099.6047.44.camel@localhost.localdomain> Message-ID: Ok...I have removed sendfile and will see if the problem persists. There is one more strange error and this from server running in production mode, using Apache2.2, mod_proxy and mod_proxy_balancer and mongrel. I have a controller price_controller and i call it from main page, using <%= periodically_call_remote(:controller => 'price',:action => 'index',:frequency => 180) %> And sometime i get /appname/price not found errors. On 8/3/06, hemant wrote: > > Thanks for following up. > > I am on Ubuntu server edition, and yes i have sendfile installed. But > removing it may create some performance problem won't it? > As for the mongrel version, you can already see in the earlier message, it > is 0.3.13. > > I was earlier running, apache2 with fcgi and didn't face this issue. I am > myself trying to investigate this problem. > > > > > > > On 8/3/06, Zed Shaw wrote: > > > > On Wed, 2006-08-02 at 02:02 +0530, hemant wrote: > > > 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 > > > > Have you solved this yet? I'm working up my bug list. > > > > Try the following things: > > > > 1) remove ruby-sendfile if you have it installed. > > 2) try the pre-release: sudo gem install mongrel > > --source=http://mongrel.rubyforge.org/releases/ > > 3) try your app with webrick and see if you get the error. > > 4) tell me what OS and mongrel version this happens with. > > > > sorry if you gave me this info already, i'm just whipping through my > > e-mail queue to catch up. > > > > > > -- > > Zed A. Shaw > > http://www.zedshaw.com/ > > http://mongrel.rubyforge.org/ > > http://www.railsmachine.com/ -- Need Mongrel support? > > > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > -- > nothing much to talk > -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060803/293c55e3/attachment.html From zedshaw at zedshaw.com Thu Aug 3 10:23:48 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 07:23:48 -0700 Subject: [Mongrel] [WARNING] don't use ruby-sendfile In-Reply-To: References: <1154587989.6047.41.camel@localhost.localdomain> Message-ID: <1154615028.5989.3.camel@localhost.localdomain> On Thu, 2006-08-03 at 07:53 -0500, James Ludlow wrote: > On 8/3/06, Zed Shaw wrote: > > I'll be investigating why it doesn't really work as advertised, and > > really it's not worth the hassle for just a 20% perf boost on static > > files (and ONLY static files, no other requests at all). Really, if you > > need fast static files use a real web server instead. > > In my case, most of my content is static and the performance boost is > very significant. I'm using file_column to manage the uploads, so > using a "real web server" around this is just a pain. > Measure the performance of both (with sendfile and without), you may find it's not that great (20% is a high estimate). > I haven't noticed any stability problems at all either. Is this > something that people notice right away (perhaps due to something else > in their environment), or will it sneak up on me? It sneaks up on you. Just one day you hit the right load and the OS starts canceling client requests at weird moments and Mongrel crashes for no reason. You're on your own now man. :-) -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 3 10:26:34 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 03 Aug 2006 07:26:34 -0700 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) In-Reply-To: References: <1154588099.6047.44.camel@localhost.localdomain> Message-ID: <1154615194.5989.6.camel@localhost.localdomain> On Thu, 2006-08-03 at 19:38 +0530, hemant wrote: > Ok...I have removed sendfile and will see if the problem persists. > > There is one more strange error and this from server running in > production mode, using Apache2.2, mod_proxy and mod_proxy_balancer and > mongrel. > > I have a controller price_controller and i call it from main page, > using <%= periodically_call_remote(:controller => 'price',:action => > 'index',:frequency => 180) %> > > And sometime i get /appname/price not found errors. > Ok, so removing sendfile fixed problems for you? It's not quite clear from your message. As for the priodically_call_remote I'm thinking it's your code, double check though. The performance difference isn't that great and it isn't worth the stability problems. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From jamesludlow at gmail.com Thu Aug 3 10:40:51 2006 From: jamesludlow at gmail.com (James Ludlow) Date: Thu, 3 Aug 2006 09:40:51 -0500 Subject: [Mongrel] [WARNING] don't use ruby-sendfile In-Reply-To: <1154615028.5989.3.camel@localhost.localdomain> References: <1154587989.6047.41.camel@localhost.localdomain> <1154615028.5989.3.camel@localhost.localdomain> Message-ID: On 8/3/06, Zed Shaw wrote: > On Thu, 2006-08-03 at 07:53 -0500, James Ludlow wrote: > > On 8/3/06, Zed Shaw wrote: > > > I'll be investigating why it doesn't really work as advertised, and > > > really it's not worth the hassle for just a 20% perf boost on static > > > files (and ONLY static files, no other requests at all). Really, if you > > > need fast static files use a real web server instead. > > > > In my case, most of my content is static and the performance boost is > > very significant. I'm using file_column to manage the uploads, so > > using a "real web server" around this is just a pain. > > > > Measure the performance of both (with sendfile and without), you may > find it's not that great (20% is a high estimate). Setting the performance issue aside for a moment, if I have a long download (i.e. streaming video), I'm going to tie up a mongrel process for one user for a relatively long time. This isn't a crisis, because I can just spawn more, and I'm more constrained by the bandwidth at the switch than by memory or CPU time. My use of the word "performance" was pretty vague and imprecise. I'll try it without sendfile, but with more mongrel processes and see what happens. > > I haven't noticed any stability problems at all either. Is this > > something that people notice right away (perhaps due to something else > > in their environment), or will it sneak up on me? > > It sneaks up on you. Just one day you hit the right load and the OS > starts canceling client requests at weird moments and Mongrel crashes > for no reason. > > You're on your own now man. :-) I appreciate the warning. With what seems like a sudden influx of stability problems and now this announcement about sendfile, I'm wondering if something else might be going on though. I'm not saying that ruby-sendfile isn't broken, but maybe something else changed recently that exposed this bug. -- James From gethemant at gmail.com Thu Aug 3 10:52:04 2006 From: gethemant at gmail.com (hemant) Date: Thu, 3 Aug 2006 20:22:04 +0530 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) In-Reply-To: <1154615194.5989.6.camel@localhost.localdomain> References: <1154588099.6047.44.camel@localhost.localdomain> <1154615194.5989.6.camel@localhost.localdomain> Message-ID: Well, at least now i am not getting application.rb and routes.rb file not found error. But I am still getting errors in perdiodically_call_remote. Here is the code snippet:

<%= render_component(:controller => '/price', :action => 'index') %>

<%= periodically_call_remote(:update => 'pricedlist', :url => {:controller => 'price',:action => 'index'}, :frequency => 180)%> Now just forget use of components for a while, I will replace this with widgets.But the point is, when the page loads for the first time, it loads allright. Now, for some ajax calls, i have put as the dummy url and when within this inlined view of price/index, you click somewhere and a "#" is appended to the url, in the next call to perdiodically_call_remote, i get : Recognition failed for "/foobar/public/price" Where foobar is application name. First of, should this call be "/foobar/price"? rather than /foobar/public/price. and i dont have any routes setup for this spefic for this controller. Here is my routes.rb file: ActionController::Routing::Routes.draw do |map| # The priority is based upon order of creation: first created -> highest priority. # Sample of regular route: # map.connect 'products/:id', :controller => 'catalog', :action => 'view' # Keep in mind you can assign values other than :controller and :action # Sample of named route: # map.purchase 'products/:id/purchase', :controller => 'catalog', :action => 'purchase' # This route can be invoked with purchase_url(:id => product.id) # You can have the root of your site routed by hooking up '' # -- just remember to delete public/index.html. map.connect '', :controller => "start" # Allow downloading Web Service WSDL as a file with an extension # instead of a file named 'wsdl' map.connect ':controller/service.wsdl', :action => 'wsdl' # Install the default route as the lowest priority. #map.connect ':controller/:action/:id', :controller => 'start' map.connect ':controller/:action/:id' end so what is the problem? On 8/3/06, Zed Shaw wrote: > > On Thu, 2006-08-03 at 19:38 +0530, hemant wrote: > > Ok...I have removed sendfile and will see if the problem persists. > > > > There is one more strange error and this from server running in > > production mode, using Apache2.2, mod_proxy and mod_proxy_balancer and > > mongrel. > > > > I have a controller price_controller and i call it from main page, > > using <%= periodically_call_remote(:controller => 'price',:action => > > 'index',:frequency => 180) %> > > > > And sometime i get /appname/price not found errors. > > > > Ok, so removing sendfile fixed problems for you? It's not quite clear > from your message. As for the priodically_call_remote I'm thinking it's > your code, double check though. > > The performance difference isn't that great and it isn't worth the > stability problems. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060803/0b957aaf/attachment.html From gethemant at gmail.com Thu Aug 3 10:54:04 2006 From: gethemant at gmail.com (hemant) Date: Thu, 3 Aug 2006 20:24:04 +0530 Subject: [Mongrel] strange bugs while using mongrel, while running in development (and also sometimes in production mode) In-Reply-To: References: <1154588099.6047.44.camel@localhost.localdomain> <1154615194.5989.6.camel@localhost.localdomain> Message-ID: If i dont touch any of the links within price/index view, which may append "#" to the url, then periodically_call_remote works fine. I am sort of sure, it could be a mongrel problem. On 8/3/06, hemant wrote: > > Well, at least now i am not getting application.rb and routes.rb file not > found error. > But I am still getting errors in perdiodically_call_remote. Here is the > code snippet: > >

> <%= render_component(:controller => '/price', :action => 'index') %> >

Message-ID: Really? I guess the setup is similar(I am afraid it is identical) to one given by Coda and Erza on their blogs. Can anbody clarify on this?. What should be the rewrite rules so that, static pages are served by Apache.I have benchmarked, Apache2 with fcgi and Apache 2.2 + mongrel + mod_proxy_balancer. To me, it looks like Apache2 + fcgi is winning the race currently. On 8/5/06, Nauhaie wrote: > > I think the rewrite rules will never be used here... I have run tests > and it appears that cached contents are served by Mongrel instead of > Apache with such a configuration. You should use either proxy pass > exceptions (! rules), or rewrite. But I might be wrong... > > Proxy pass exceptions are faster for everything that is in the excluded > directories, but they just forward everything else to Mongrel, including > cached content... > > But once more, I can be totally wrong... > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails at lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails > -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060809/fe9662d0/attachment.html From mongrel at philip.pjkh.com Tue Aug 8 19:36:14 2006 From: mongrel at philip.pjkh.com (Philip Hallstrom) Date: Tue, 8 Aug 2006 18:36:14 -0500 (CDT) Subject: [Mongrel] [Rails] Re: Fwd: Kubuntu, Apache 2.2, Mongrel, Mongrel Cluster In-Reply-To: References:

Message-ID: <20060808183540.T30892@bravo.pjkh.com> > I guess the setup is similar(I am afraid it is identical) to one given by > Coda and Erza on their blogs. > > Can anbody clarify on this?. > What should be the rewrite rules so that, static pages are served by > Apache.I have benchmarked, Apache2 with fcgi and Apache 2.2 + mongrel + > mod_proxy_balancer. To me, it looks like Apache2 + fcgi is winning the race > currently. We use this to handle rails/mongrel "side-by-side".... RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} -d RewriteRule ^(.+[^/])$ $1/ [R] RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} \.php RewriteRule ^(.*)$ $1 [QSA,L] RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME}/index.html -f RewriteRule ^(.*)$ $1/index.html [QSA,L] RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME}/index.php -f RewriteRule ^(.*)$ $1/index.php [QSA,L] RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} -d RewriteRule ^(.*)[^/]$ $1/ [QSA,L] RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] > > On 8/5/06, Nauhaie wrote: >> >> I think the rewrite rules will never be used here... I have run tests >> and it appears that cached contents are served by Mongrel instead of >> Apache with such a configuration. You should use either proxy pass >> exceptions (! rules), or rewrite. But I might be wrong... >> >> Proxy pass exceptions are faster for everything that is in the excluded >> directories, but they just forward everything else to Mongrel, including >> cached content... >> >> But once more, I can be totally wrong... >> >> -- >> Posted via http://www.ruby-forum.com/. >> _______________________________________________ >> Rails mailing list >> Rails at lists.rubyonrails.org >> http://lists.rubyonrails.org/mailman/listinfo/rails >> > > > > -- > nothing much to talk > From jec at rptec.ch Wed Aug 9 04:21:24 2006 From: jec at rptec.ch (Jean-Eric Cuendet) Date: Wed, 09 Aug 2006 10:21:24 +0200 Subject: [Mongrel] Mongrel and multi apps Message-ID: <44D99B04.2070508@rptec.ch> Hi, I use Mongrel to serve my Rails applications on my server, but how can I serve more than one application with one mongrel server? Thanks. -jec -- Best regards / Salutations. Jean-Eric Cuendet Senior developer / Technical support Riskpro Technologies SA Av. Louis-Ruchonnet 2 CH-1003 Lausanne Switzerland Direct : +41 21 637 0123 Principal : +41 21 637 0110 Fax : +41 21 637 0111 Skype : jec.rptec Web : http://www.rptec.ch -------------------------------------------------------- From christopher.k.hall at gmail.com Wed Aug 9 07:38:07 2006 From: christopher.k.hall at gmail.com (Chris Hall) Date: Wed, 9 Aug 2006 07:38:07 -0400 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: <44D99B04.2070508@rptec.ch> References: <44D99B04.2070508@rptec.ch> Message-ID: in a nutshell, you can't. you'll need (at least) one instance of mongrel for each app, each running on a different port. what you will want to do is run you mongrel instances proxied behind another server, for example, apache. you also have the option of using mongrel_cluster to load balance if necessary. check out the docs on the mongrel site for more detailed info on proxying and clustering mongrel. Chris On 8/9/06, Jean-Eric Cuendet wrote: > Hi, > I use Mongrel to serve my Rails applications on my server, but how can I > serve more than one application with one mongrel server? > Thanks. > -jec > > -- > Best regards / Salutations. > > Jean-Eric Cuendet > Senior developer / Technical support > Riskpro Technologies SA > Av. Louis-Ruchonnet 2 > CH-1003 Lausanne > Switzerland > > Direct : +41 21 637 0123 > Principal : +41 21 637 0110 > Fax : +41 21 637 0111 > Skype : jec.rptec > Web : http://www.rptec.ch > -------------------------------------------------------- > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From me at seebq.com Wed Aug 9 10:37:10 2006 From: me at seebq.com (Charles Brian Quinn) Date: Wed, 9 Aug 2006 10:37:10 -0400 Subject: [Mongrel] IIS proxying to lighttpd/apache to mongrel with SSL Message-ID: <3a2de0cd0608090737u517a73f1n8c5415ac69193a86@mail.gmail.com> This might not be a mongrel question so much as an IIS question, and if so, my apologies. I'm needing to switch a (ASP.NET) web application that's running behind a firewall appliance on IIS on port 8443 under SSL to a rails web application -- a mongrel instance (and perhaps later apache or lighttpd with new mod_core_prox in front of mongrel) on a different server. I remember Apache proxy_pass confs having to foward on a special request to let mongrel know it's SSL, and I've also seen that for IIS forwarding, I'll need to use a reverse_proxy_pass plugin. Are there any other snafus with all that redirection? I see: http://www.napcs.com/howto/rails/deploy/ (Brian Hogan, if you're on here, great work, thanks) Just curious if it's a lot of work, if so, I'll just gladly pay to rekey the SSL cert to apache/lighttpd and be done with it. Thanks, -- Charles Brian Quinn self-promotion: www.seebq.com highgroove studios: www.highgroove.com slingshot hosting: www.slingshothosting.com From _ at whats-your.name Wed Aug 9 11:33:18 2006 From: _ at whats-your.name (carmen) Date: Wed, 9 Aug 2006 15:33:18 +0000 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: References: <44D99B04.2070508@rptec.ch> Message-ID: <20060809153318.GH19432@replic.net> On Wed Aug 09, 2006 at 07:38:07AM -0400, Chris Hall wrote: > in a nutshell, you can't. are you sure you can't? i mean cant you run like 10 MouseHole/Camping apps off a single mongrel? im guessing youd need to investigate mongrel_rails script.. From technoweenie at gmail.com Wed Aug 9 11:38:07 2006 From: technoweenie at gmail.com (Rick Olson) Date: Wed, 9 Aug 2006 10:38:07 -0500 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: <20060809153318.GH19432@replic.net> References: <44D99B04.2070508@rptec.ch> <20060809153318.GH19432@replic.net> Message-ID: <48fe25b0608090838t64dd5495x21faa8e824afd135@mail.gmail.com> > are you sure you can't? i mean cant you run like 10 MouseHole/Camping apps off a single mongrel? im guessing youd need to investigate mongrel_rails script.. Rails is not threadsafe, so you can only have 1 process per mongrel. -- Rick Olson http://techno-weenie.net From _ at whats-your.name Wed Aug 9 11:49:36 2006 From: _ at whats-your.name (carmen) Date: Wed, 9 Aug 2006 15:49:36 +0000 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: <48fe25b0608090838t64dd5495x21faa8e824afd135@mail.gmail.com> References: <44D99B04.2070508@rptec.ch> <20060809153318.GH19432@replic.net> <48fe25b0608090838t64dd5495x21faa8e824afd135@mail.gmail.com> Message-ID: <20060809154936.GI19432@replic.net> > Rails is not threadsafe, so you can only have 1 process per mongrel. according to actionpack/lib/action_controller/base.rb:239: "Action Pack and Active Record are by default thread-safe". plus doesnt mongrel typical run about 4 rails instances? i dont see why you couldnt run 8, and have half of them be another app with a URI prefix? From ezmobius at gmail.com Wed Aug 9 12:17:10 2006 From: ezmobius at gmail.com (Ezra Zygmuntowicz) Date: Wed, 9 Aug 2006 09:17:10 -0700 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: <20060809154936.GI19432@replic.net> References: <44D99B04.2070508@rptec.ch> <20060809153318.GH19432@replic.net> <48fe25b0608090838t64dd5495x21faa8e824afd135@mail.gmail.com> <20060809154936.GI19432@replic.net> Message-ID: On Aug 9, 2006, at 8:49 AM, carmen wrote: >> Rails is not threadsafe, so you can only have 1 process per mongrel. > > according to actionpack/lib/action_controller/base.rb:239: "Action > Pack and Active Record are by default thread-safe". plus doesnt > mongrel typical run about 4 rails instances? i dont see why you > couldnt run 8, and have half of them be another app with a URI prefix? > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users ActionPack and ActiveRecord claim to be thread safe but this is a lie ;) When the whole rails stack is used together it is definitely not thread safe. -Ezra From wyhaines at gmail.com Wed Aug 9 12:18:29 2006 From: wyhaines at gmail.com (Kirk Haines) Date: Wed, 9 Aug 2006 10:18:29 -0600 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: <20060809154936.GI19432@replic.net> References: <44D99B04.2070508@rptec.ch> <20060809153318.GH19432@replic.net> <48fe25b0608090838t64dd5495x21faa8e824afd135@mail.gmail.com> <20060809154936.GI19432@replic.net> Message-ID: On 8/9/06, carmen <_ at whats-your.name> wrote: > > Rails is not threadsafe, so you can only have 1 process per mongrel. > > according to actionpack/lib/action_controller/base.rb:239: "Action Pack and Active Record > are by default thread-safe". plus doesnt mongrel typical run about 4 rails instances? i dont > see why you couldnt run 8, and have half of them be another app with a URI prefix? Someone else can speak to Rails and whether it actually is threadsafe or not. However, you misunderstand Mongrel's handler for Rails. Take a look at the source code. It's clean and easy to read. The Rails handler has a single Rails application instance, and it has a mutex that it uses to limit request processing within Rails to one at a time. The use of this guard mutex can be disabled in the handler, if you want to use Rails multithreaded, but Zed has a strongly worded warning against doing that in the code. Kirk Haines From zedshaw at zedshaw.com Wed Aug 9 14:52:18 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 09 Aug 2006 11:52:18 -0700 Subject: [Mongrel] Mongrel and multi apps In-Reply-To: References: <44D99B04.2070508@rptec.ch> <20060809153318.GH19432@replic.net> <48fe25b0608090838t64dd5495x21faa8e824afd135@mail.gmail.com> <20060809154936.GI19432@replic.net> Message-ID: <1155149538.6001.2.camel@localhost.localdomain> On Wed, 2006-08-09 at 10:18 -0600, Kirk Haines wrote: > On 8/9/06, carmen <_ at whats-your.name> wrote: > > > Rails is not threadsafe, so you can only have 1 process per mongrel. > > > > according to actionpack/lib/action_controller/base.rb:239: "Action Pack and Active Record > > are by default thread-safe". plus doesnt mongrel typical run about 4 rails instances? i dont > > see why you couldnt run 8, and have half of them be another app with a URI prefix? > > Someone else can speak to Rails and whether it actually is threadsafe or not. > > However, you misunderstand Mongrel's handler for Rails. Take a look > at the source code. It's clean and easy to read. The Rails handler > has a single Rails application instance, and it has a mutex that it > uses to limit request processing within Rails to one at a time. The > use of this guard mutex can be disabled in the handler, if you want to > use Rails multithreaded, but Zed has a strongly worded warning against > doing that in the code. > Yes, also known as the Great Katana Suicide Warning. The name should probably tell that you shouldn't use it. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Wed Aug 9 20:15:03 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 09 Aug 2006 17:15:03 -0700 Subject: [Mongrel] Hey, me and some friends want to break typo In-Reply-To: <14b7e5ef0607131247k5920684cm90657ca9af1e43ec@mail.gmail.com> References: <149FFF9F-4D2D-45EB-8D00-2FD4F9A10AB6@feldpost.com> <14b7e5ef0607131247k5920684cm90657ca9af1e43ec@mail.gmail.com> Message-ID: <1155168903.6519.2.camel@localhost.localdomain> Hey Scott, Cool finally meeting you last night. I wanted to see if you were willing to work with me and two other guys in doing a security test of Rails and Typo. Basically, after today's nasty little security hole I got with DHH and two security pros I know and we're looking for a small fun first project to try out a security test with. Since I know you, you wrote typo, typo is popular, I figured it'd be a good start. If you're interested, get ahold of me and we'll start putting this together. I'm thinking you could help them get a good tour of it, help when bugs are found, and just generally learn about how they attack stuff. Thanks. Zed From scott at sigkill.org Wed Aug 9 20:18:18 2006 From: scott at sigkill.org (Scott Laird) Date: Wed, 9 Aug 2006 17:18:18 -0700 Subject: [Mongrel] Hey, me and some friends want to break typo In-Reply-To: <1155168903.6519.2.camel@localhost.localdomain> References: <149FFF9F-4D2D-45EB-8D00-2FD4F9A10AB6@feldpost.com> <14b7e5ef0607131247k5920684cm90657ca9af1e43ec@mail.gmail.com> <1155168903.6519.2.camel@localhost.localdomain> Message-ID: <14b7e5ef0608091718r6741980buc913fef081e3f272@mail.gmail.com> Sounds good to me. As usual, I'm afraid of what they'll find. I'm going to push a new Typo release tonight to deal with the 1.1.5 mess, but after that I should have time to work on this. Contact me off-list for scheduling details :-). Scott On 8/9/06, Zed Shaw wrote: > Hey Scott, > > Cool finally meeting you last night. I wanted to see if you were > willing to work with me and two other guys in doing a security test of > Rails and Typo. > > Basically, after today's nasty little security hole I got with DHH and > two security pros I know and we're looking for a small fun first project > to try out a security test with. > > Since I know you, you wrote typo, typo is popular, I figured it'd be a > good start. > > If you're interested, get ahold of me and we'll start putting this > together. I'm thinking you could help them get a good tour of it, help > when bugs are found, and just generally learn about how they attack > stuff. > > Thanks. > > Zed > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From zedshaw at zedshaw.com Wed Aug 9 20:31:17 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 09 Aug 2006 17:31:17 -0700 Subject: [Mongrel] Hey, me and some friends want to break typo In-Reply-To: <1155168903.6519.2.camel@localhost.localdomain> References: <149FFF9F-4D2D-45EB-8D00-2FD4F9A10AB6@feldpost.com> <14b7e5ef0607131247k5920684cm90657ca9af1e43ec@mail.gmail.com> <1155168903.6519.2.camel@localhost.localdomain> Message-ID: <1155169877.6519.4.camel@localhost.localdomain> On Wed, 2006-08-09 at 17:15 -0700, Zed Shaw wrote: > Hey Scott, > > Cool finally meeting you last night. I wanted to see if you were > willing to work with me and two other guys in doing a security test of > Rails and Typo. > DOH! Not supposed to go to the list, but hey, cat's out of the bag I guess. Zed From wilsonb at gmail.com Wed Aug 9 23:22:42 2006 From: wilsonb at gmail.com (Wilson Bilkovich) Date: Wed, 9 Aug 2006 23:22:42 -0400 Subject: [Mongrel] Uploading/file_column and Mongrel In-Reply-To: References: Message-ID: On 8/5/06, HH wrote: > Howdy, > > I recently switched an app to Mongrel and since the switch, when I upload > files using the file_column plug-in, the files are not uploaded with the > correct permissions. > > I want something like this: > > -rw-rw-rw- file.jpg > > But I am getting: > > -rw------- file.jpg > There might be a cooler trick, but you could start Mongrel with a -S, pointing at a script that sets the umask to 0000 http://www.linuxforums.org/security/file_permissions.html From christophercyll at gmail.com Thu Aug 10 02:45:00 2006 From: christophercyll at gmail.com (Topher Cyll) Date: Wed, 9 Aug 2006 23:45:00 -0700 Subject: [Mongrel] mongrel and comet "implementation" Message-ID: <2599499e0608092345n49b1071bl73e042623175616@mail.gmail.com> Hey folks, I was playing around with adding Comet (a javascript technology used to receive events without AJAX polling) support to Mongrel. More info about Comet here: http://en.wikipedia.org/wiki/Comet_%28programming%29) I sort of got it working. My code is available at: http;//cyll.org/comet.tar.gz Run comet.rb from inside the directory and point your browser at: http://localhost:5555/ The fly in the ointment is that until a Comet request finishes, that URL mount point stops responding. I assume this is because of how thread management happens in Mongrel. Leaving the request unfinished like I do is probably uncool. One way to sort of work around the problem is to use a dispatcher that registers a new handler at a unique URL for each Comet user. You can see that both the main page and: http://localhost:5555/2 work simultaneous. And neither affects other mounted handlers, so you can also access: http://localhost:5555/moose Anyways, I'm not really doing anything with this code and I'm sure it has problems, but I thought I'd put it out there in case anyone else wanted to play around with Mongrel and Comet. Mongrel rocks, Topher Cyll From cjwoodward at gmail.com Thu Aug 10 02:56:46 2006 From: cjwoodward at gmail.com (Carl Woodward) Date: Thu, 10 Aug 2006 16:56:46 +1000 Subject: [Mongrel] Error on Solaris Message-ID: Hi everyone, I'm having a problem starting rails on solaris. I have made the changes suggested in the joyeur article but it doesn't make any difference. The error is below. Does anyone have any idea? /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in `register': undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in `uri' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in `debug' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in `debug' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in `cloaker_' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in `listener' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in `cloaker_' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in `initialize' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in `run' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in `run' from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 from /opt/csw/bin/mongrel_rails:18 Thanks, Carl. From cjwoodward at gmail.com Thu Aug 10 03:45:21 2006 From: cjwoodward at gmail.com (Carl Woodward) Date: Thu, 10 Aug 2006 17:45:21 +1000 Subject: [Mongrel] Error on Solaris In-Reply-To: References: Message-ID: Sorry but I might not be seeing some sort of meta programming hidden around the place because when I look at the URIClassifier is see none of the methods that are described in the documentation: class URIClassifier attr_reader :handler_map # Returns the URIs that have been registered with this classifier so far. # The URIs returned should not be modified as this will cause a memory leak. # You can use this to inspect the contents of the URIClassifier. def uris @handler_map.keys end # Simply does an inspect that looks like a Hash inspect. def inspect @handler_map.inspect end end I'm confused. On 8/10/06, Carl Woodward wrote: > Hi everyone, I'm having a problem starting rails on solaris. I have > made the changes suggested in the joyeur article but it doesn't make > any difference. The error is below. Does anyone have any idea? > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > `register': undefined method `resolve' for nil:Mongrel::URIClassifier > (NoMethodError) > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > `uri' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > `debug' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > `debug' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > `cloaker_' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > `listener' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > `cloaker_' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > `initialize' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > `run' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > `run' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > from /opt/csw/bin/mongrel_rails:18 > > Thanks, > Carl. > -- Carl Woodward 0412218979 cjwoodward at gmail.com From cjwoodward at gmail.com Thu Aug 10 03:53:53 2006 From: cjwoodward at gmail.com (Carl Woodward) Date: Thu, 10 Aug 2006 17:53:53 +1000 Subject: [Mongrel] Fwd: Error on Solaris In-Reply-To: References: Message-ID: Sorry guys, I'm an idiot. Its in C. ---------- Forwarded message ---------- From: Carl Woodward Date: Aug 10, 2006 5:45 PM Subject: Re: Error on Solaris To: mongrel-users at rubyforge.org Sorry but I might not be seeing some sort of meta programming hidden around the place because when I look at the URIClassifier is see none of the methods that are described in the documentation: class URIClassifier attr_reader :handler_map # Returns the URIs that have been registered with this classifier so far. # The URIs returned should not be modified as this will cause a memory leak. # You can use this to inspect the contents of the URIClassifier. def uris @handler_map.keys end # Simply does an inspect that looks like a Hash inspect. def inspect @handler_map.inspect end end I'm confused. On 8/10/06, Carl Woodward wrote: > Hi everyone, I'm having a problem starting rails on solaris. I have > made the changes suggested in the joyeur article but it doesn't make > any difference. The error is below. Does anyone have any idea? > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > `register': undefined method `resolve' for nil:Mongrel::URIClassifier > (NoMethodError) > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > `uri' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > `debug' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > `debug' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > `cloaker_' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > `listener' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > `cloaker_' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > `initialize' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > `run' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > `run' > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > from /opt/csw/bin/mongrel_rails:18 > > Thanks, > Carl. > -- Carl Woodward 0412218979 cjwoodward at gmail.com -- Carl Woodward 0412218979 cjwoodward at gmail.com From scott at sigkill.org Thu Aug 10 03:56:29 2006 From: scott at sigkill.org (Scott Laird) Date: Thu, 10 Aug 2006 00:56:29 -0700 Subject: [Mongrel] Fwd: Error on Solaris In-Reply-To: References: Message-ID: <14b7e5ef0608100056p27ef88eq30ea22d014eb781b@mail.gmail.com> I believe the usual problem with Mongrel on Solaris is caused by mixing Sun's C compiler and GCC. Make sure that Ruby and Mongrel are compiled with the same compiler. Scott On 8/10/06, Carl Woodward wrote: > Sorry guys, I'm an idiot. Its in C. > > ---------- Forwarded message ---------- > From: Carl Woodward > Date: Aug 10, 2006 5:45 PM > Subject: Re: Error on Solaris > To: mongrel-users at rubyforge.org > > > Sorry but I might not be seeing some sort of meta programming hidden > around the place because when I look at the URIClassifier is see none > of the methods that are described in the documentation: > > class URIClassifier > attr_reader :handler_map > > # Returns the URIs that have been registered with this classifier so far. > # The URIs returned should not be modified as this will cause a memory leak. > # You can use this to inspect the contents of the URIClassifier. > def uris > @handler_map.keys > end > > # Simply does an inspect that looks like a Hash inspect. > def inspect > @handler_map.inspect > end > end > > I'm confused. > > On 8/10/06, Carl Woodward wrote: > > Hi everyone, I'm having a problem starting rails on solaris. I have > > made the changes suggested in the joyeur article but it doesn't make > > any difference. The error is below. Does anyone have any idea? > > > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > > `register': undefined method `resolve' for nil:Mongrel::URIClassifier > > (NoMethodError) > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > > `uri' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > > `debug' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > > `debug' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > > `cloaker_' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > > `listener' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > > `cloaker_' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > > `initialize' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > > `run' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > > `run' > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > > from /opt/csw/bin/mongrel_rails:18 > > > > Thanks, > > Carl. > > > > > -- > Carl Woodward > 0412218979 > cjwoodward at gmail.com > > > -- > Carl Woodward > 0412218979 > cjwoodward at gmail.com > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From cjwoodward at gmail.com Thu Aug 10 04:49:59 2006 From: cjwoodward at gmail.com (Carl Woodward) Date: Thu, 10 Aug 2006 18:49:59 +1000 Subject: [Mongrel] Fwd: Error on Solaris In-Reply-To: <14b7e5ef0608100056p27ef88eq30ea22d014eb781b@mail.gmail.com> References: <14b7e5ef0608100056p27ef88eq30ea22d014eb781b@mail.gmail.com> Message-ID: Thanks for that. On 8/10/06, Scott Laird wrote: > I believe the usual problem with Mongrel on Solaris is caused by > mixing Sun's C compiler and GCC. Make sure that Ruby and Mongrel are > compiled with the same compiler. > > > Scott > > On 8/10/06, Carl Woodward wrote: > > Sorry guys, I'm an idiot. Its in C. > > > > ---------- Forwarded message ---------- > > From: Carl Woodward > > Date: Aug 10, 2006 5:45 PM > > Subject: Re: Error on Solaris > > To: mongrel-users at rubyforge.org > > > > > > Sorry but I might not be seeing some sort of meta programming hidden > > around the place because when I look at the URIClassifier is see none > > of the methods that are described in the documentation: > > > > class URIClassifier > > attr_reader :handler_map > > > > # Returns the URIs that have been registered with this classifier so far. > > # The URIs returned should not be modified as this will cause a memory leak. > > # You can use this to inspect the contents of the URIClassifier. > > def uris > > @handler_map.keys > > end > > > > # Simply does an inspect that looks like a Hash inspect. > > def inspect > > @handler_map.inspect > > end > > end > > > > I'm confused. > > > > On 8/10/06, Carl Woodward wrote: > > > Hi everyone, I'm having a problem starting rails on solaris. I have > > > made the changes suggested in the joyeur article but it doesn't make > > > any difference. The error is below. Does anyone have any idea? > > > > > > /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:666:in > > > `register': undefined method `resolve' for nil:Mongrel::URIClassifier > > > (NoMethodError) > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:850:in > > > `uri' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1018:in > > > `debug' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:1016:in > > > `debug' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:108:in > > > `cloaker_' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:832:in > > > `listener' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:96:in > > > `cloaker_' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:750:in > > > `initialize' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:83:in > > > `run' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/command.rb:199:in > > > `run' > > > from /opt/csw/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/mongrel_rails:235 > > > from /opt/csw/bin/mongrel_rails:18 > > > > > > Thanks, > > > Carl. > > > > > > > > > -- > > Carl Woodward > > 0412218979 > > cjwoodward at gmail.com > > > > > > -- > > Carl Woodward > > 0412218979 > > cjwoodward at gmail.com > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Carl Woodward 0412218979 cjwoodward at gmail.com From christopher.k.hall at gmail.com Thu Aug 10 07:17:50 2006 From: christopher.k.hall at gmail.com (Chris Hall) Date: Thu, 10 Aug 2006 07:17:50 -0400 Subject: [Mongrel] mongrel stops responding after period of no use Message-ID: I just moved from apache2/fcgi to apache2.2/mongrel and everything seems to work great except for 2 issues, one being major and one minor. the major issue i am experiencing is that after a period of time where my rails apps are not used, typically overnight, the mongrel processes become unresponsive. I currently have 3 apps running behind an apache2.2 proxy. every morning when i come in to work, all 3 apps no longer respond, either via apache or even if i try to connect directly to the port the app is running on. i start each mongrel instance as: cd mongrel_rails start -e production -p -d i see nothing in any of the log files to indicate a problem other than this is the apache error log i have setup for each app: [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: error reading status line from remote server localhost [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: Error reading from remote server returned by / [Mon Aug 07 06:29:42 2006] [error] (111)Connection refused: proxy: HTTP: attempt to connect to [::1]:3010 (localhost) failed [Mon Aug 07 06:29:42 2006] [error] ap_proxy_connect_backend disabling worker for (localhost) [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection for (localhost) [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection for (localhost) each app is setup in it's own virtual host directive with: ProxyRequests Off ProxyPass / http://localhost:/ ProxyPassReverse / http://localhost:/ ProxyPreserveHost On RewriteEngine On RewriteRule "^(images|stylesheets|javascripts)/?(.*)" "$0" [L] with being the port specific the app. i wind up having to kill each process and restarting, then restart apache. also, the minor issue, is that when i start mongrel_rails with a configuration file, the pid file never gets created, yet the log file does, and they are set to the default location, log/mongrel.log and log/mongrel.pid in this case it's only a minor inconvenience, because i can just run: ps -C mongrel_rails -o pid= |xargs kill -9 to kill the processes so i can restart. i have since switched to starting mongrel from the command line as the pid file will get created when used this way. installed gems: actionmailer (1.2.3, 1.2.2, 1.1.5) Service layer for easy email delivery and testing. actionpack (1.12.3, 1.12.2, 1.11.2) Web-flow and rendering framework putting the VC in MVC. actionwebservice (1.1.4, 1.1.3, 1.0.0) Web service support for Action Pack. activerecord (1.14.3, 1.13.2) Implements the ActiveRecord pattern for ORM. activesupport (1.3.1, 1.2.5) Support and utility classes used by the Rails framework. cmdparse (2.0.0) Advanced command line parser supporting commands daemons (0.4.4) A toolkit to create and control daemons in different ways gem_plugin (0.2.1) A plugin system based only on rubygems that uses dependencies only login_generator (1.1.0) [Rails] Login generator. mongrel (0.3.13.3) A small fast HTTP library and server that runs Rails, Camping, and Nitro apps. rails (1.1.4, 1.1.3, 1.0.0) Web-application framework with template engine, control-flow layer, and ORM. rake (0.7.1, 0.7.0) Ruby based make-like utility. sources (0.0.1) This package provides download sources for remote gem installation any help would be greatly appreciated. Chris From jason at joyent.com Thu Aug 10 07:41:27 2006 From: jason at joyent.com (Jason A. Hoffman) Date: Thu, 10 Aug 2006 04:41:27 -0700 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: References: Message-ID: <4A9D9436-B47B-4F0C-91EA-1484C2A94C64@joyent.com> What's the database backend? Regards, J On Aug 10, 2006, at 4:17 AM, Chris Hall wrote: > I just moved from apache2/fcgi to apache2.2/mongrel and everything > seems to work great except for 2 issues, one being major and one > minor. > > the major issue i am experiencing is that after a period of time where > my rails apps are not used, typically overnight, the mongrel processes > become unresponsive. I currently have 3 apps running behind an > apache2.2 proxy. every morning when i come in to work, all 3 apps no > longer respond, either via apache or even if i try to connect directly > to the port the app is running on. > > i start each mongrel instance as: > > cd > mongrel_rails start -e production -p -d > > i see nothing in any of the log files to indicate a problem other than > this is the apache error log i have setup for each app: > > [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: error > reading status line from remote server localhost > [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: Error > reading from remote server returned by / > [Mon Aug 07 06:29:42 2006] [error] (111)Connection refused: proxy: > HTTP: attempt to connect to [::1]:3010 (localhost) failed > [Mon Aug 07 06:29:42 2006] [error] ap_proxy_connect_backend disabling > worker for (localhost) > [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection > for (localhost) > [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection > for (localhost) > > each app is setup in it's own virtual host directive with: > > ProxyRequests Off > ProxyPass / http://localhost:/ > ProxyPassReverse / http://localhost:/ > ProxyPreserveHost On > RewriteEngine On > RewriteRule "^(images|stylesheets|javascripts)/?(.*)" "$0" [L] > > with being the port specific the app. > > i wind up having to kill each process and restarting, then restart > apache. > > also, the minor issue, is that when i start mongrel_rails with a > configuration file, the pid file never gets created, yet the log file > does, and they are set to the default location, log/mongrel.log and > log/mongrel.pid > > in this case it's only a minor inconvenience, because i can just run: > > ps -C mongrel_rails -o pid= |xargs kill -9 > > to kill the processes so i can restart. i have since switched to > starting mongrel from the command line as the pid file will get > created when used this way. > > installed gems: > > > actionmailer (1.2.3, 1.2.2, 1.1.5) > Service layer for easy email delivery and testing. > > actionpack (1.12.3, 1.12.2, 1.11.2) > Web-flow and rendering framework putting the VC in MVC. > > actionwebservice (1.1.4, 1.1.3, 1.0.0) > Web service support for Action Pack. > > activerecord (1.14.3, 1.13.2) > Implements the ActiveRecord pattern for ORM. > > activesupport (1.3.1, 1.2.5) > Support and utility classes used by the Rails framework. > > cmdparse (2.0.0) > Advanced command line parser supporting commands > > daemons (0.4.4) > A toolkit to create and control daemons in different ways > > gem_plugin (0.2.1) > A plugin system based only on rubygems that uses dependencies only > > login_generator (1.1.0) > [Rails] Login generator. > > mongrel (0.3.13.3) > A small fast HTTP library and server that runs Rails, Camping, and > Nitro apps. > > rails (1.1.4, 1.1.3, 1.0.0) > Web-application framework with template engine, control-flow > layer, > and ORM. > > rake (0.7.1, 0.7.0) > Ruby based make-like utility. > > sources (0.0.1) > This package provides download sources for remote gem installation > > > any help would be greatly appreciated. > > Chris > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From christopher.k.hall at gmail.com Thu Aug 10 08:09:55 2006 From: christopher.k.hall at gmail.com (Chris Hall) Date: Thu, 10 Aug 2006 08:09:55 -0400 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: <4A9D9436-B47B-4F0C-91EA-1484C2A94C64@joyent.com> References: <4A9D9436-B47B-4F0C-91EA-1484C2A94C64@joyent.com> Message-ID: mysql 5.0.22 Chris On 8/10/06, Jason A. Hoffman wrote: > What's the database backend? > > Regards, J > > On Aug 10, 2006, at 4:17 AM, Chris Hall wrote: > > > I just moved from apache2/fcgi to apache2.2/mongrel and everything > > seems to work great except for 2 issues, one being major and one > > minor. > > > > the major issue i am experiencing is that after a period of time where > > my rails apps are not used, typically overnight, the mongrel processes > > become unresponsive. I currently have 3 apps running behind an > > apache2.2 proxy. every morning when i come in to work, all 3 apps no > > longer respond, either via apache or even if i try to connect directly > > to the port the app is running on. > > > > i start each mongrel instance as: > > > > cd > > mongrel_rails start -e production -p -d > > > > i see nothing in any of the log files to indicate a problem other than > > this is the apache error log i have setup for each app: > > > > [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: error > > reading status line from remote server localhost > > [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: Error > > reading from remote server returned by / > > [Mon Aug 07 06:29:42 2006] [error] (111)Connection refused: proxy: > > HTTP: attempt to connect to [::1]:3010 (localhost) failed > > [Mon Aug 07 06:29:42 2006] [error] ap_proxy_connect_backend disabling > > worker for (localhost) > > [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection > > for (localhost) > > [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection > > for (localhost) > > > > each app is setup in it's own virtual host directive with: > > > > ProxyRequests Off > > ProxyPass / http://localhost:/ > > ProxyPassReverse / http://localhost:/ > > ProxyPreserveHost On > > RewriteEngine On > > RewriteRule "^(images|stylesheets|javascripts)/?(.*)" "$0" [L] > > > > with being the port specific the app. > > > > i wind up having to kill each process and restarting, then restart > > apache. > > > > also, the minor issue, is that when i start mongrel_rails with a > > configuration file, the pid file never gets created, yet the log file > > does, and they are set to the default location, log/mongrel.log and > > log/mongrel.pid > > > > in this case it's only a minor inconvenience, because i can just run: > > > > ps -C mongrel_rails -o pid= |xargs kill -9 > > > > to kill the processes so i can restart. i have since switched to > > starting mongrel from the command line as the pid file will get > > created when used this way. > > > > installed gems: > > > > > > actionmailer (1.2.3, 1.2.2, 1.1.5) > > Service layer for easy email delivery and testing. > > > > actionpack (1.12.3, 1.12.2, 1.11.2) > > Web-flow and rendering framework putting the VC in MVC. > > > > actionwebservice (1.1.4, 1.1.3, 1.0.0) > > Web service support for Action Pack. > > > > activerecord (1.14.3, 1.13.2) > > Implements the ActiveRecord pattern for ORM. > > > > activesupport (1.3.1, 1.2.5) > > Support and utility classes used by the Rails framework. > > > > cmdparse (2.0.0) > > Advanced command line parser supporting commands > > > > daemons (0.4.4) > > A toolkit to create and control daemons in different ways > > > > gem_plugin (0.2.1) > > A plugin system based only on rubygems that uses dependencies only > > > > login_generator (1.1.0) > > [Rails] Login generator. > > > > mongrel (0.3.13.3) > > A small fast HTTP library and server that runs Rails, Camping, and > > Nitro apps. > > > > rails (1.1.4, 1.1.3, 1.0.0) > > Web-application framework with template engine, control-flow > > layer, > > and ORM. > > > > rake (0.7.1, 0.7.0) > > Ruby based make-like utility. > > > > sources (0.0.1) > > This package provides download sources for remote gem installation > > > > > > any help would be greatly appreciated. > > > > Chris > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From me at seebq.com Thu Aug 10 08:14:06 2006 From: me at seebq.com (Charles Brian Quinn) Date: Thu, 10 Aug 2006 08:14:06 -0400 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: <4A9D9436-B47B-4F0C-91EA-1484C2A94C64@joyent.com> References: <4A9D9436-B47B-4F0C-91EA-1484C2A94C64@joyent.com> Message-ID: <3a2de0cd0608100514l5c4365bcib6c6fabac121e145@mail.gmail.com> Do you have any special log rotation on apache that occurs nightly? p.s. upgrade rails to 1.1.5 On 8/10/06, Jason A. Hoffman wrote: > What's the database backend? > > Regards, J > > On Aug 10, 2006, at 4:17 AM, Chris Hall wrote: > > > I just moved from apache2/fcgi to apache2.2/mongrel and everything > > seems to work great except for 2 issues, one being major and one > > minor. > > > > the major issue i am experiencing is that after a period of time where > > my rails apps are not used, typically overnight, the mongrel processes > > become unresponsive. I currently have 3 apps running behind an > > apache2.2 proxy. every morning when i come in to work, all 3 apps no > > longer respond, either via apache or even if i try to connect directly > > to the port the app is running on. > > > > i start each mongrel instance as: > > > > cd > > mongrel_rails start -e production -p -d > > > > i see nothing in any of the log files to indicate a problem other than > > this is the apache error log i have setup for each app: > > > > [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: error > > reading status line from remote server localhost > > [Mon Aug 07 06:29:42 2006] [error] [client xx.xx.xx.xx] proxy: Error > > reading from remote server returned by / > > [Mon Aug 07 06:29:42 2006] [error] (111)Connection refused: proxy: > > HTTP: attempt to connect to [::1]:3010 (localhost) failed > > [Mon Aug 07 06:29:42 2006] [error] ap_proxy_connect_backend disabling > > worker for (localhost) > > [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection > > for (localhost) > > [Mon Aug 07 06:29:42 2006] [error] proxy: HTTP: disabled connection > > for (localhost) > > > > each app is setup in it's own virtual host directive with: > > > > ProxyRequests Off > > ProxyPass / http://localhost:/ > > ProxyPassReverse / http://localhost:/ > > ProxyPreserveHost On > > RewriteEngine On > > RewriteRule "^(images|stylesheets|javascripts)/?(.*)" "$0" [L] > > > > with being the port specific the app. > > > > i wind up having to kill each process and restarting, then restart > > apache. > > > > also, the minor issue, is that when i start mongrel_rails with a > > configuration file, the pid file never gets created, yet the log file > > does, and they are set to the default location, log/mongrel.log and > > log/mongrel.pid > > > > in this case it's only a minor inconvenience, because i can just run: > > > > ps -C mongrel_rails -o pid= |xargs kill -9 > > > > to kill the processes so i can restart. i have since switched to > > starting mongrel from the command line as the pid file will get > > created when used this way. > > > > installed gems: > > > > > > actionmailer (1.2.3, 1.2.2, 1.1.5) > > Service layer for easy email delivery and testing. > > > > actionpack (1.12.3, 1.12.2, 1.11.2) > > Web-flow and rendering framework putting the VC in MVC. > > > > actionwebservice (1.1.4, 1.1.3, 1.0.0) > > Web service support for Action Pack. > > > > activerecord (1.14.3, 1.13.2) > > Implements the ActiveRecord pattern for ORM. > > > > activesupport (1.3.1, 1.2.5) > > Support and utility classes used by the Rails framework. > > > > cmdparse (2.0.0) > > Advanced command line parser supporting commands > > > > daemons (0.4.4) > > A toolkit to create and control daemons in different ways > > > > gem_plugin (0.2.1) > > A plugin system based only on rubygems that uses dependencies only > > > > login_generator (1.1.0) > > [Rails] Login generator. > > > > mongrel (0.3.13.3) > > A small fast HTTP library and server that runs Rails, Camping, and > > Nitro apps. > > > > rails (1.1.4, 1.1.3, 1.0.0) > > Web-application framework with template engine, control-flow > > layer, > > and ORM. > > > > rake (0.7.1, 0.7.0) > > Ruby based make-like utility. > > > > sources (0.0.1) > > This package provides download sources for remote gem installation > > > > > > any help would be greatly appreciated. > > > > Chris > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Charles Brian Quinn self-promotion: www.seebq.com highgroove studios: www.highgroove.com slingshot hosting: www.slingshothosting.com From uberkorp at gmail.com Thu Aug 10 08:35:15 2006 From: uberkorp at gmail.com (Scott Mathieson) Date: Thu, 10 Aug 2006 13:35:15 +0100 Subject: [Mongrel] Hey, me and some friends want to break typo In-Reply-To: <1155169877.6519.4.camel@localhost.localdomain> References: <149FFF9F-4D2D-45EB-8D00-2FD4F9A10AB6@feldpost.com> <1155168903.6519.2.camel@localhost.localdomain> <1155169877.6519.4.camel@localhost.localdomain> Message-ID: <200608101335.15503.uberkorp@gmail.com> On Thursday 10 August 2006 01:31, Zed Shaw wrote: > On Wed, 2006-08-09 at 17:15 -0700, Zed Shaw wrote: > > Hey Scott, > > > > Cool finally meeting you last night. I wanted to see if you were > > willing to work with me and two other guys in doing a security test of > > Rails and Typo. > > DOH! Not supposed to go to the list, but hey, cat's out of the bag I > guess. > > Zed > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users even better is the few seconds of panic when i couldn't remember going transcontinental and writing typo, all in the last 24 hours; but i'm ok now From wilsonb at gmail.com Thu Aug 10 11:15:17 2006 From: wilsonb at gmail.com (Wilson Bilkovich) Date: Thu, 10 Aug 2006 11:15:17 -0400 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: References: Message-ID: On 8/10/06, Chris Hall wrote: > I just moved from apache2/fcgi to apache2.2/mongrel and everything > seems to work great except for 2 issues, one being major and one > minor. > > the major issue i am experiencing is that after a period of time where > my rails apps are not used, typically overnight, the mongrel processes > become unresponsive. I currently have 3 apps running behind an > apache2.2 proxy. every morning when i come in to work, all 3 apps no > longer respond, either via apache or even if i try to connect directly > to the port the app is running on. > I ran into this the other day. I'm fairly sure it's an Apache bug, potentially this one: http://issues.apache.org/bugzilla/show_bug.cgi?id=37770 I upgraded from 2.2.2 to 2.2.3, and it happens much less frequently now. From zedshaw at zedshaw.com Thu Aug 10 11:36:04 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 08:36:04 -0700 Subject: [Mongrel] mongrel and comet "implementation" In-Reply-To: <2599499e0608092345n49b1071bl73e042623175616@mail.gmail.com> References: <2599499e0608092345n49b1071bl73e042623175616@mail.gmail.com> Message-ID: <1155224164.5997.10.camel@localhost.localdomain> On Wed, 2006-08-09 at 23:45 -0700, Topher Cyll wrote: > Hey folks, > > I was playing around with adding Comet (a javascript technology used > to receive events without AJAX polling) support to Mongrel. More info > about Comet here: > > http://en.wikipedia.org/wiki/Comet_%28programming%29) > > I sort of got it working. My code is available at: > > http;//cyll.org/comet.tar.gz > Pretty cool. So you're using a chunked encoding to stream out the new data. One thing: @response.write(sprintf("%x;\r\n", size)) ... @response.write("0;\r\n") You don't need the ";". That's only required if you add parameters to the chunked encoding header. Just give the size (in hex). I've contemplated doing chunked encodings for Mongrel, but I still have the problem that frameworks do their headers and body out of order, so it gets ugly (and also most proxies don't grok chunked encoding). > The fly in the ointment is that until a Comet request finishes, that > URL mount point stops responding. I assume this is because of how > thread management happens in Mongrel. Leaving the request unfinished > like I do is probably uncool. > That shouldn't happen. Mongrel isn't locking or anything when running, so you should be able to server multiple requests. I'll take a look at this further. > One way to sort of work around the problem is to use a dispatcher that > registers a new handler at a unique URL for each Comet user. You can > see that both the main page and: > > http://localhost:5555/2 > > work simultaneous. And neither affects other mounted handlers, so you > can also access: > > http://localhost:5555/moose > > Anyways, I'm not really doing anything with this code and I'm sure it > has problems, but I thought I'd put it out there in case anyone else > wanted to play around with Mongrel and Comet. And no idea why that would work. Like I said, no locking in mongrel but I'll look at it. Cool job. If you get a chance to work this further keep sending me feedback and code. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 10 11:39:12 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 08:39:12 -0700 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: References: Message-ID: <1155224352.5997.12.camel@localhost.localdomain> On Thu, 2006-08-10 at 07:17 -0400, Chris Hall wrote: > I just moved from apache2/fcgi to apache2.2/mongrel and everything > seems to work great except for 2 issues, one being major and one > minor. > > the major issue i am experiencing is that after a period of time where > my rails apps are not used, typically overnight, the mongrel processes > become unresponsive. I currently have 3 apps running behind an > apache2.2 proxy. every morning when i come in to work, all 3 apps no > longer respond, either via apache or even if i try to connect directly > to the port the app is running on. > Two things can cause this: apache bug that Wilson mentioned, or that your MySQL adapter needs to be told to reduce it's timeout time. Don't remember the magic incantation but it was mentioned several times in the list (gotta get that in the damn FAQ) > also, the minor issue, is that when i start mongrel_rails with a > configuration file, the pid file never gets created, yet the log file > does, and they are set to the default location, log/mongrel.log and > log/mongrel.pid > Upgrade to the 0.3.13.4 pre-release and this will be fixed: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 10 11:48:51 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 08:48:51 -0700 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: References: Message-ID: <1155224931.5997.16.camel@localhost.localdomain> On Thu, 2006-08-10 at 07:17 -0400, Chris Hall wrote: > I just moved from apache2/fcgi to apache2.2/mongrel and everything > seems to work great except for 2 issues, one being major and one > minor. ActiveRecord::Base.verification_timeout = 14400 This is the option to try in environment.rb -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 10 11:54:26 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 08:54:26 -0700 Subject: [Mongrel] Fwd: Error on Solaris In-Reply-To: References: Message-ID: <1155225266.5997.18.camel@localhost.localdomain> On Thu, 2006-08-10 at 17:53 +1000, Carl Woodward wrote: > Sorry guys, I'm an idiot. Its in C. Also, try installing the pre-release as I've (hopefully) fixed things that cause the Sun C compiler to blow up (because they couldn't read a spec if it was filled with porn). gem install mongrel --source=http://mongrel.rubyforge.org/releases/ -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From tsailipu at gmail.com Thu Aug 10 11:58:33 2006 From: tsailipu at gmail.com (Philip Lipu Tsai) Date: Thu, 10 Aug 2006 08:58:33 -0700 Subject: [Mongrel] Software caused connection abort In-Reply-To: References: Message-ID: Hi Zed or anyone that is also looking at Mongrel, Just want to report something that, although doesn't crash mongrel, is rather annoying. I am running the latest Mongrel 0.3.13.3 - ruby version on cygwin (yeah, poor me). When I start mongrel_rails with ActiveRecord::Base.allow_concurrency = true in environment.rb, I see a lot of "Error sending file /cygdrive/c/[snipped]/[default java scripts].js : Software caused connection abort" While these don't cause any harm, they are concerning... Also, I see the following error more often as well: Lost connection to MySQL server during query [ the exception traces vary but do involve routing; here is an example:] /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.3/lib/active_record/vendor/mysql.rb:1112:in `write' /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.3/lib/active_record/vendor/mysql.rb:1162:in `finalizer' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:54:in `<<' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:548:in `generation_code_for' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:46:in `method_missing' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:19:in `indent' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:46:in `method_missing' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:545:in `generation_code_for' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:488:in `write_generation' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:482:in `write_generation' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:629:in `draw' #{RAILS_ROOT}/config/routes.rb:1 /usr/bin/mongrel_rails:18 When I see such page, refreshing once or twice typically works. With ActiveRecord::Base.allow_concurrency set to false (i.e. the default), everything chugs along pretty well. Don't know whether this problem is particular to cygwin environment or is generic when one turns on ActiveRecord::Base.allow_concurrency (or this is just my system...). Philip From jan.svitok at gmail.com Thu Aug 10 12:24:37 2006 From: jan.svitok at gmail.com (Jan Svitok) Date: Thu, 10 Aug 2006 18:24:37 +0200 Subject: [Mongrel] Software caused connection abort In-Reply-To: References: Message-ID: <8d9b3d920608100924m5ddd3a99pd485f9b03c6ce1e0@mail.gmail.com> On 8/10/06, Philip Lipu Tsai wrote: > Hi Zed or anyone that is also looking at Mongrel, > > Just want to report something that, although doesn't crash mongrel, is > rather annoying. > > I am running the latest Mongrel 0.3.13.3 - ruby version on cygwin > (yeah, poor me). When I start mongrel_rails with > ActiveRecord::Base.allow_concurrency = true in environment.rb, I see a > lot of > "Error sending file /cygdrive/c/[snipped]/[default java scripts].js > : Software caused connection abort" > > While these don't cause any harm, they are concerning... > Also, I see the following error more often as well: > > Lost connection to MySQL server during query > [ the exception traces vary but do involve routing; here is an example:] > /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.3/lib/active_record/vendor/mysql.rb:1112:in > `write' > /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.3/lib/active_record/vendor/mysql.rb:1162:in > `finalizer' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:54:in > `<<' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:548:in > `generation_code_for' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:46:in > `method_missing' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:19:in > `indent' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:46:in > `method_missing' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:545:in > `generation_code_for' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:488:in > `write_generation' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:482:in > `write_generation' > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:629:in > `draw' > #{RAILS_ROOT}/config/routes.rb:1 > /usr/bin/mongrel_rails:18 > > When I see such page, refreshing once or twice typically works. > > With ActiveRecord::Base.allow_concurrency set to false (i.e. the > default), everything chugs along pretty well. Don't know whether > this problem is particular to cygwin environment or is generic when > one turns on ActiveRecord::Base.allow_concurrency (or this is just my > system...). mail by Zed from another thread (mongrel and multi apps): > Someone else can speak to Rails and whether it actually is threadsafe or not. > > However, you misunderstand Mongrel's handler for Rails. Take a look > at the source code. It's clean and easy to read. The Rails handler > has a single Rails application instance, and it has a mutex that it > uses to limit request processing within Rails to one at a time. The > use of this guard mutex can be disabled in the handler, if you want to > use Rails multithreaded, but Zed has a strongly worded warning against > doing that in the code. > Yes, also known as the Great Katana Suicide Warning. The name should probably tell that you shouldn't use it. From tsailipu at gmail.com Thu Aug 10 12:48:20 2006 From: tsailipu at gmail.com (Philip Lipu Tsai) Date: Thu, 10 Aug 2006 09:48:20 -0700 Subject: [Mongrel] Software caused connection abort In-Reply-To: <8d9b3d920608100924m5ddd3a99pd485f9b03c6ce1e0@mail.gmail.com> References: <8d9b3d920608100924m5ddd3a99pd485f9b03c6ce1e0@mail.gmail.com> Message-ID: Nice... I saw some discussion about why-not?'s of turning on this option, so thought of playing with this setting. Probably those "why-not? only applied to WEBrick. I just now found a thread where Zed replied with quite some details on this as well. http://rubyforge.org/pipermail/mongrel-users/2006-May/000302.html Thanks! On 8/10/06, Jan Svitok wrote: > On 8/10/06, Philip Lipu Tsai wrote: > > Hi Zed or anyone that is also looking at Mongrel, > > > > Just want to report something that, although doesn't crash mongrel, is > > rather annoying. > > > > I am running the latest Mongrel 0.3.13.3 - ruby version on cygwin > > (yeah, poor me). When I start mongrel_rails with > > ActiveRecord::Base.allow_concurrency = true in environment.rb, I see a > > lot of > > "Error sending file /cygdrive/c/[snipped]/[default java scripts].js > > : Software caused connection abort" > > > > While these don't cause any harm, they are concerning... > > Also, I see the following error more often as well: > > > > Lost connection to MySQL server during query > > [ the exception traces vary but do involve routing; here is an example:] > > /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.3/lib/active_record/vendor/mysql.rb:1112:in > > `write' > > /usr/lib/ruby/gems/1.8/gems/activerecord-1.14.3/lib/active_record/vendor/mysql.rb:1162:in > > `finalizer' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:54:in > > `<<' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:548:in > > `generation_code_for' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:46:in > > `method_missing' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:19:in > > `indent' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/code_generation.rb:46:in > > `method_missing' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:545:in > > `generation_code_for' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:488:in > > `write_generation' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:482:in > > `write_generation' > > /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/routing.rb:629:in > > `draw' > > #{RAILS_ROOT}/config/routes.rb:1 > > /usr/bin/mongrel_rails:18 > > > > When I see such page, refreshing once or twice typically works. > > > > With ActiveRecord::Base.allow_concurrency set to false (i.e. the > > default), everything chugs along pretty well. Don't know whether > > this problem is particular to cygwin environment or is generic when > > one turns on ActiveRecord::Base.allow_concurrency (or this is just my > > system...). > > mail by Zed from another thread (mongrel and multi apps): > > > Someone else can speak to Rails and whether it actually is threadsafe or not. > > > > However, you misunderstand Mongrel's handler for Rails. Take a look > > at the source code. It's clean and easy to read. The Rails handler > > has a single Rails application instance, and it has a mutex that it > > uses to limit request processing within Rails to one at a time. The > > use of this guard mutex can be disabled in the handler, if you want to > > use Rails multithreaded, but Zed has a strongly worded warning against > > doing that in the code. > > > > Yes, also known as the Great Katana Suicide Warning. > > The name should probably tell that you shouldn't use it. > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From christopher.k.hall at gmail.com Thu Aug 10 13:03:04 2006 From: christopher.k.hall at gmail.com (Chris Hall) Date: Thu, 10 Aug 2006 13:03:04 -0400 Subject: [Mongrel] mongrel stops responding after period of no use In-Reply-To: <1155224931.5997.16.camel@localhost.localdomain> References: <1155224931.5997.16.camel@localhost.localdomain> Message-ID: thanks all, i will give the mysql timeout one a try first, see if that helps then go from there. Chris. On 8/10/06, Zed Shaw wrote: > On Thu, 2006-08-10 at 07:17 -0400, Chris Hall wrote: > > I just moved from apache2/fcgi to apache2.2/mongrel and everything > > seems to work great except for 2 issues, one being major and one > > minor. > > ActiveRecord::Base.verification_timeout = 14400 > > This is the option to try in environment.rb > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From lists at lastonepicked.com Thu Aug 10 13:25:13 2006 From: lists at lastonepicked.com (HH) Date: Thu, 10 Aug 2006 10:25:13 -0700 Subject: [Mongrel] Telling Apache Not to Send a Sub-Directory to the Cluster Message-ID: Howdy, I am using Apache 2.2 and Mongrel with great success. I have a mod_rewrite question and I am NO expert. I think it's really simple but I haven't nailed it. I was hoping someone here could help. I'm using Apache conf right out of the cluster example from the Mongrel site. I have a directory under my apps 'public' directory called 'sendto'. Files in that directory are accessible but I want to be able to provide a directory listing for when no specific file is requested. Right now, it seems that the requests to http://domain.com/sendto/ are being sent to the cluster. I am looking for a rewrite statement that basically tells Apache not to send that specific URL pattern to the cluster. Can anyone help? Hunter From kigsteronline at mac.com Thu Aug 10 13:28:26 2006 From: kigsteronline at mac.com (kigsteronline at mac.com) Date: Thu, 10 Aug 2006 10:28:26 -0700 Subject: [Mongrel] Getting "Invalid HTTP format, parsing fails." from one client Message-ID: <9C06B0BB-D874-4E89-8499-5F7FE39C0507@mac.com> 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 2006: BAD CLIENT (192.168.2.42): Invalid HTTP format, parsing fails. Wed Aug 09 16:25:31 PDT 2006: BAD CLIENT (192.168.2.42): Invalid HTTP format, parsing fails. Wed Aug 09 16:25:31 PDT 2006: BAD CLIENT (192.168.2.42): Invalid HTTP format, parsing fails. No other computers experience this issue. When I start Webrick, she can access the pages using both Firefox and IE6. Does anyone have any clue as to what may be causing this, and is it possible to actually log the HTTP request details to a log file? I tried running Mongrel with -B (debug) but found not much useful info in the debug files to explain this behavior. Any pointers much appreciated! Thanks, Konstantin ???????????????????????????????????????????? Konstantin Gredeskoul Senior Software Engineer kig at blurb.com Blurb, Inc. 580 California St, Suite 300 San Francisco, CA 94104 415.364.6338 (direct) 415.362.2078 (fax) blurb.com ???????????????????????????????????????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060810/0e0e4df2/attachment-0001.html From mongrel at philip.pjkh.com Thu Aug 10 13:56:28 2006 From: mongrel at philip.pjkh.com (Philip Hallstrom) Date: Thu, 10 Aug 2006 12:56:28 -0500 (CDT) Subject: [Mongrel] Telling Apache Not to Send a Sub-Directory to the Cluster In-Reply-To: References: Message-ID: <20060810125443.U8800@bravo.pjkh.com> > Howdy, > > I am using Apache 2.2 and Mongrel with great success. > > I have a mod_rewrite question and I am NO expert. I think it's really simple > but I haven't nailed it. I was hoping someone here could help. > > I'm using Apache conf right out of the cluster example from the Mongrel > site. > > I have a directory under my apps 'public' directory called 'sendto'. Files > in that directory are accessible but I want to be able to provide a > directory listing for when no specific file is requested. > > Right now, it seems that the requests to http://domain.com/sendto/ are being > sent to the cluster. > > I am looking for a rewrite statement that basically tells Apache not to send > that specific URL pattern to the cluster. Add a rewrite condition to the rule that sends things to the cluster saying that if the url matches this, that's false so bail... I'm not good enough to write out the rule on the fly, but the docs should get you there.... From lists at lastonepicked.com Thu Aug 10 14:02:04 2006 From: lists at lastonepicked.com (HH) Date: Thu, 10 Aug 2006 11:02:04 -0700 Subject: [Mongrel] Telling Apache Not to Send a Sub-Directory to the Cluster In-Reply-To: <20060810125443.U8800@bravo.pjkh.com> Message-ID: Thanks, that's what I'm going for but just like you, not good enough to get there. Been messing with the docs for the past hour and no luck yet. I was hoping a guru could lend a hand. > From: Philip Hallstrom > Reply-To: > Date: Thu, 10 Aug 2006 12:56:28 -0500 (CDT) > To: Mongrel > Subject: Re: [Mongrel] Telling Apache Not to Send a Sub-Directory to the > Cluster > >> Howdy, >> >> I am using Apache 2.2 and Mongrel with great success. >> >> I have a mod_rewrite question and I am NO expert. I think it's really simple >> but I haven't nailed it. I was hoping someone here could help. >> >> I'm using Apache conf right out of the cluster example from the Mongrel >> site. >> >> I have a directory under my apps 'public' directory called 'sendto'. Files >> in that directory are accessible but I want to be able to provide a >> directory listing for when no specific file is requested. >> >> Right now, it seems that the requests to http://domain.com/sendto/ are being >> sent to the cluster. >> >> I am looking for a rewrite statement that basically tells Apache not to send >> that specific URL pattern to the cluster. > > Add a rewrite condition to the rule that sends things to the cluster > saying that if the url matches this, that's false so bail... > > I'm not good enough to write out the rule on the fly, but the docs should > get you there.... From jgeiger at gmail.com Thu Aug 10 14:12:00 2006 From: jgeiger at gmail.com (Joey Geiger) Date: Thu, 10 Aug 2006 13:12:00 -0500 Subject: [Mongrel] Mongrel servers running in a subdirectory behind a proxy Message-ID: <466af3440608101112l7895ec4p617c4fdaab869cb6@mail.gmail.com> 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 behind an apache 1.3 mod_proxy. apache >> proxypass /app http://127.0.0.1:8000 >> pen(8000) >> mongrel_cluster (8001-3) I'm using mongrel_cluster, so I added "prefix: /app" into the cluster configuration, but I'm not sure if it's doing anything, as the routes generated by rails are still /user/index and not /app/user/index As part of the information in previous posts, I found this possible solution, but I wasn't sure if I need to do both at the same time. #make rails think it lives in /app ActionController::AbstractRequest.relative_url_root = "/app" Also the above setting has a bad side effect that if makes the images, stylesheets, javascripts think they are in /app, even when using the external host setting below. # Enable serving of images, stylesheets, and javascripts from an asset server config.action_controller.asset_host = "http://assets.example.com" Thanks for any help you can supply. From christophercyll at gmail.com Thu Aug 10 14:27:01 2006 From: christophercyll at gmail.com (Topher Cyll) Date: Thu, 10 Aug 2006 11:27:01 -0700 Subject: [Mongrel] mongrel and comet "implementation" In-Reply-To: <1155224164.5997.10.camel@localhost.localdomain> References: <2599499e0608092345n49b1071bl73e042623175616@mail.gmail.com> <1155224164.5997.10.camel@localhost.localdomain> Message-ID: <2599499e0608101127p7c0ac4f2xfbf7294e57c13967@mail.gmail.com> Zed, > You don't need the ";". That's only required if you add parameters to > the chunked encoding header. Just give the size (in hex). Good to know! > I've contemplated doing chunked encodings for Mongrel, but I still have > the problem that frameworks do their headers and body out of order, so > it gets ugly (and also most proxies don't grok chunked encoding). Ah, I noticed this didn't seem to work at work (we have a proxy). > That shouldn't happen. Mongrel isn't locking or anything when running, > so you should be able to server multiple requests. I'll take a look at > this further. Hmm, interesting. It would be cool if this could be used more generally. Let me know if you figure it out what's happening! Topher From mongrel at philip.pjkh.com Thu Aug 10 14:38:25 2006 From: mongrel at philip.pjkh.com (Philip Hallstrom) Date: Thu, 10 Aug 2006 13:38:25 -0500 (CDT) Subject: [Mongrel] Telling Apache Not to Send a Sub-Directory to the Cluster In-Reply-To: References: Message-ID: <20060810133807.N9775@bravo.pjkh.com> > Thanks, that's what I'm going for but just like you, not good enough to get > there. > > Been messing with the docs for the past hour and no luck yet. I was hoping a > guru could lend a hand. Turn up the log level for rewrite and watch it... that helps a lot when futzing with those things... > >> From: Philip Hallstrom >> Reply-To: >> Date: Thu, 10 Aug 2006 12:56:28 -0500 (CDT) >> To: Mongrel >> Subject: Re: [Mongrel] Telling Apache Not to Send a Sub-Directory to the >> Cluster >> >>> Howdy, >>> >>> I am using Apache 2.2 and Mongrel with great success. >>> >>> I have a mod_rewrite question and I am NO expert. I think it's really simple >>> but I haven't nailed it. I was hoping someone here could help. >>> >>> I'm using Apache conf right out of the cluster example from the Mongrel >>> site. >>> >>> I have a directory under my apps 'public' directory called 'sendto'. Files >>> in that directory are accessible but I want to be able to provide a >>> directory listing for when no specific file is requested. >>> >>> Right now, it seems that the requests to http://domain.com/sendto/ are being >>> sent to the cluster. >>> >>> I am looking for a rewrite statement that basically tells Apache not to send >>> that specific URL pattern to the cluster. >> >> Add a rewrite condition to the rule that sends things to the cluster >> saying that if the url matches this, that's false so bail... >> >> I'm not good enough to write out the rule on the fly, but the docs should >> get you there.... > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From zedshaw at zedshaw.com Thu Aug 10 15:06:06 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 12:06:06 -0700 Subject: [Mongrel] Mongrel servers running in a subdirectory behind a proxy In-Reply-To: <466af3440608101112l7895ec4p617c4fdaab869cb6@mail.gmail.com> References: <466af3440608101112l7895ec4p617c4fdaab869cb6@mail.gmail.com> Message-ID: <1155236766.6001.1.camel@localhost.localdomain> On Thu, 2006-08-10 at 13:12 -0500, Joey Geiger wrote: > I was able to find some information about this in the list archives, > but it ended with a possible patch being submitted for Mongrel. > You need the pre-release 0.3.13.4 of mongrel which supports the --prefix option: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ With this you can then configure your mongrel servers with the --prefix option: mongrel_rails start -e production --prefix=/app I'll have to contact Bradley about how to get mongrel_cluster to use this though. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 10 15:07:46 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 12:07:46 -0700 Subject: [Mongrel] Getting "Invalid HTTP format, parsing fails." from one client In-Reply-To: <9C06B0BB-D874-4E89-8499-5F7FE39C0507@mac.com> References: <9C06B0BB-D874-4E89-8499-5F7FE39C0507@mac.com> Message-ID: <1155236866.6001.4.camel@localhost.localdomain> On Thu, 2006-08-10 at 10:28 -0700, kigsteronline at mac.com wrote: > 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. If you have McAffee Security Center installed then you need to do two things: 1) Install the 0.3.13.4 pre-release of mongrel: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ 2) Contact McAffee and tell them why are they sending the aaaaaaaaaa: ++++++++ header since that does absolutely nothing at all and is pretty suspicious. Let me know if this works. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Thu Aug 10 15:12:06 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 10 Aug 2006 12:12:06 -0700 Subject: [Mongrel] mongrel and comet "implementation" In-Reply-To: <2599499e0608101127p7c0ac4f2xfbf7294e57c13967@mail.gmail.com> References: <2599499e0608092345n49b1071bl73e042623175616@mail.gmail.com> <1155224164.5997.10.camel@localhost.localdomain> <2599499e0608101127p7c0ac4f2xfbf7294e57c13967@mail.gmail.com> Message-ID: <1155237126.6001.7.camel@localhost.localdomain> On Thu, 2006-08-10 at 11:27 -0700, Topher Cyll wrote: > Zed, > > > That shouldn't happen. Mongrel isn't locking or anything when running, > > so you should be able to server multiple requests. I'll take a look at > > this further. > > Hmm, interesting. It would be cool if this could be used more > generally. Let me know if you figure it out what's happening! This won't happen for a very long time. So, if you want to get this working you'll have to pitch in and figure it out for yourself. Sorry but I've got to get Mongrel working for the normal usage before I jump into weirdness like comet. Keep trying though. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From christophercyll at gmail.com Thu Aug 10 15:50:24 2006 From: christophercyll at gmail.com (Topher Cyll) Date: Thu, 10 Aug 2006 12:50:24 -0700 Subject: [Mongrel] mongrel and comet "implementation" In-Reply-To: <1155237126.6001.7.camel@localhost.localdomain> References: <2599499e0608092345n49b1071bl73e042623175616@mail.gmail.com> <1155224164.5997.10.camel@localhost.localdomain> <2599499e0608101127p7c0ac4f2xfbf7294e57c13967@mail.gmail.com> <1155237126.6001.7.camel@localhost.localdomain> Message-ID: <2599499e0608101250xfb9e719t1c91a696e9bee140@mail.gmail.com> > This won't happen for a very long time. So, if you want to get this > working you'll have to pitch in and figure it out for yourself. Sorry > but I've got to get Mongrel working for the normal usage before I jump > into weirdness like comet. > > Keep trying though. Yeah, no worries. =) I'll poke around when I find some free time. -Toph From bradley at railsmachine.com Thu Aug 10 20:33:07 2006 From: bradley at railsmachine.com (Bradley Taylor) Date: Thu, 10 Aug 2006 20:33:07 -0400 Subject: [Mongrel] Mongrel servers running in a subdirectory behind a proxy In-Reply-To: <1155236766.6001.1.camel@localhost.localdomain> References: <466af3440608101112l7895ec4p617c4fdaab869cb6@mail.gmail.com> <1155236766.6001.1.camel@localhost.localdomain> Message-ID: On Aug 10, 2006, at 3:06 PM, Zed Shaw wrote: > > With this you can then configure your mongrel servers with the -- > prefix > option: > > mongrel_rails start -e production --prefix=/app > > I'll have to contact Bradley about how to get mongrel_cluster to use > this though. A mongrel_cluster release is coming soon (like tomorrow). It has the 'prefix' patch and other nice contributions. Unless, of course, Rails 1.1.7 comes out. -Bradley ------ Rails Optimized Hosting ~ VPS and Dedicated Servers Simplified Deployment ~ Services and Software http://railsmachine.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060810/7870df5f/attachment-0001.html From kigsteronline at mac.com Thu Aug 10 21:09:05 2006 From: kigsteronline at mac.com (kigsteronline at mac.com) Date: Thu, 10 Aug 2006 18:09:05 -0700 Subject: [Mongrel] Getting "Invalid HTTP format, parsing fails." from one client In-Reply-To: <1155236866.6001.4.camel@localhost.localdomain> References: <9C06B0BB-D874-4E89-8499-5F7FE39C0507@mac.com> <1155236866.6001.4.camel@localhost.localdomain> Message-ID: <0FE26229-68B3-4F4E-A400-E1B8A550C898@mac.com> Zed, I thought it had something to do with McAfee. You are right, she is using their Security Center... That thing has gotten so unruly that we are all switching to Norton (another beast). Ironic that anti- virus software often gets more intrusive than the viruses themselves :) Thanks for the heads up. Konstantin On Aug 10, 2006, at 12:07 PM, Zed Shaw wrote: > On Thu, 2006-08-10 at 10:28 -0700, kigsteronline at mac.com wrote: >> 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. > > If you have McAffee Security Center installed then you need to do two > things: > > 1) Install the 0.3.13.4 pre-release of mongrel: gem install mongrel > --source=http://mongrel.rubyforge.org/releases/ > > 2) Contact McAffee and tell them why are they sending the aaaaaaaaaa: > ++++++++ header since that does absolutely nothing at all and is > pretty > suspicious. > > Let me know if this works. > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users Regards, Konstantin __________________________________________ Blog on Tek, Art and Life @ http://tektastic.blogspot.com/ Download hi-res mp3s @ http://www.polygroovers.com/ Or order 2nd down-tempo album "Moods For Take Out" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060810/b5e8225e/attachment.html From wilsonb at gmail.com Fri Aug 11 00:02:27 2006 From: wilsonb at gmail.com (Wilson Bilkovich) Date: Fri, 11 Aug 2006 00:02:27 -0400 Subject: [Mongrel] Getting "Invalid HTTP format, parsing fails." from one client In-Reply-To: <0FE26229-68B3-4F4E-A400-E1B8A550C898@mac.com> References: <9C06B0BB-D874-4E89-8499-5F7FE39C0507@mac.com> <1155236866.6001.4.camel@localhost.localdomain> <0FE26229-68B3-4F4E-A400-E1B8A550C898@mac.com> Message-ID: On 8/10/06, kigsteronline at mac.com wrote: > > Zed, > > I thought it had something to do with McAfee. You are right, she is using > their Security Center... That thing has gotten so unruly that we are all > switching to Norton (another beast). Ironic that anti-virus software often > gets more intrusive than the viruses themselves :) > Danzig wrote this song about McAfee security software in 1988: http://darklyrics.com/lyrics/danzig/danzig.html#7 From christopher.k.hall at gmail.com Fri Aug 11 07:21:06 2006 From: christopher.k.hall at gmail.com (Chris Hall) Date: Fri, 11 Aug 2006 07:21:06 -0400 Subject: [Mongrel] mongrel still fails to write pid file when starting with config file Message-ID: 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 following is generated in the config file: --- :user: mongrel :host: 0.0.0.0 :mime_map: :prefix: :port: "3000" :daemon: true :cwd: /srv/www/railsapps/myapp :includes: - mongrel :environment: production :group: webdev :log_file: log/mongrel.log :timeout: 0 :config_script: :pid_file: log/mongrel.pid :num_processors: 1024 :debug: false :docroot: public i then run mongrel_rails start -C config/mongrel.conf and mongrel start, but the pid file is still not written. the log directory perms are 775 and owned by group webdev. in addition the mogrel.log file is being written. verfied this on 2 separate systems. i went and looked this up in the buglist and found http://rubyforge.org/tracker/?group_id=1306&atid=5145&func=detail&aid=5119 . i saw someone had submitted a diff for 03.13.3, but this fix is not in 0.3.13.4. i patched and now the pid file is written. Chris From pedro at pedrocr.net Fri Aug 11 11:05:11 2006 From: pedro at pedrocr.net (=?ISO-8859-1?Q?Pedro_C=F4rte-Real?=) Date: Fri, 11 Aug 2006 16:05:11 +0100 Subject: [Mongrel] Running some code right before the app is available to users Message-ID: <62e8012c0608110805s51b6ce97h6488a7e30b84b04d@mail.gmail.com> I do some indexing using acts_as_ferret in a rails app. I need to do some preloading of the index's sort fields so that the first request that sorts doesn't take 5 minutes to complete. I tried sticking my preload code in config/environment.rb and that worked but it gets ran in rake migrations, tests, etc, when it's not really needed. Is there anything specific to starting up to serve requests I could check for? Thanks, Pedro. From justin.h.chen at gmail.com Fri Aug 11 13:32:26 2006 From: justin.h.chen at gmail.com (Justin Chen) Date: Fri, 11 Aug 2006 12:32:26 -0500 Subject: [Mongrel] Fwd: Error on Solaris In-Reply-To: <1155225266.5997.18.camel@localhost.localdomain> References: <1155225266.5997.18.camel@localhost.localdomain> Message-ID: When installing the 0.3.13.4 pre-release on Solaris I got the same error as on the Joyent blog: http://joyeur.com/2006/07/21/a-mongrel-endorsement-and-a-manual-fix-for-installing-mongrel-on-solaris-1011 Fix #1 there got it working and so far mongrel has been working. Thanks, Justin On 8/10/06, Zed Shaw wrote: > > On Thu, 2006-08-10 at 17:53 +1000, Carl Woodward wrote: > > Sorry guys, I'm an idiot. Its in C. > > Also, try installing the pre-release as I've (hopefully) fixed things > that cause the Sun C compiler to blow up (because they couldn't read a > spec if it was filled with porn). > > > gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Justin Chen Two-Bit Operation LLC http://www.twobitoperation.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060811/47cb293c/attachment.html From zedshaw at zedshaw.com Fri Aug 11 13:51:06 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 11 Aug 2006 10:51:06 -0700 Subject: [Mongrel] Running some code right before the app is available to users In-Reply-To: <62e8012c0608110805s51b6ce97h6488a7e30b84b04d@mail.gmail.com> References: <62e8012c0608110805s51b6ce97h6488a7e30b84b04d@mail.gmail.com> Message-ID: <1155318666.5980.4.camel@localhost.localdomain> On Fri, 2006-08-11 at 16:05 +0100, Pedro C?rte-Real wrote: > I do some indexing using acts_as_ferret in a rails app. I need to do > some preloading of the index's sort fields so that the first request > that sorts doesn't take 5 minutes to complete. I tried sticking my > preload code in config/environment.rb and that worked but it gets ran > in rake migrations, tests, etc, when it's not really needed. Is there > anything specific to starting up to serve requests I could check for? You could put it in a mongrel.conf and just have Mongrel run it on start-up: mongrel_rails start -S mongrel.conf (Even though it ends in .conf it's actually Ruby code that gets run inside the Configurator.) -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 11 13:59:01 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 11 Aug 2006 10:59:01 -0700 Subject: [Mongrel] Fwd: Error on Solaris In-Reply-To: References: <1155225266.5997.18.camel@localhost.localdomain> Message-ID: <1155319141.5980.10.camel@localhost.localdomain> On Fri, 2006-08-11 at 12:32 -0500, Justin Chen wrote: > When installing the 0.3.13.4 pre-release on Solaris I got the same > error as on the Joyent blog: > http://joyeur.com/2006/07/21/a-mongrel-endorsement-and-a-manual-fix-for-installing-mongrel-on-solaris-1011 > > Fix #1 there got it working and so far mongrel has been working. Yeah, without their C compiler I doubt I could fix it in the source. Looks like it's more than just stray ; characters causing this. Just do what his instructions say so that you're using GCC (but I believe you have to make sure your ruby is compiled with that as well). -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 11 14:26:13 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 11 Aug 2006 11:26:13 -0700 Subject: [Mongrel] mongrel still fails to write pid file when starting with config file In-Reply-To: References: Message-ID: <1155320773.5980.13.camel@localhost.localdomain> On Fri, 2006-08-11 at 07:21 -0400, Chris Hall wrote: > 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 Got it, stupid bug in an if statement. It should all be fixed up, but you need to change "log/mongrel.pid" and "log/mongrel.log" to use absolute paths. Previously mongrel would try to fix these up, but now it doesn't. Change them to be absolute to prevent future surprises. I'll post another pre-release update in 5 minutes. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 11 14:58:56 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 11 Aug 2006 11:58:56 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- PID Files Working Message-ID: <1155322736.5980.22.camel@localhost.localdomain> Hi Folks, An update to tell everyone to try out the pre-release again: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Nothing available for win32 yet, the next pre-release will have a win32 build to check that windows folks are OK. This release fixes the following problems: * PID files weren't being written when configured. Works now and logs messages better. * Small change to the HTTP parser to allow for headers that don't have a space after the ":" character, which is allowed by the RFC. -- Everyone using McAfee Security Center should contact them and tell them their product is a piece of crap. You should also consider not using it since they seem to be modifying people's HTTP requests in bogus ways and telling you that this is a "security" feature. This release is pretty close to becoming official. Everyone needs to test it out and shoot me any final problems. The current outstanding problems I have are: 55.BUG: test tom brice's upload app with keepalive 56.BUG: safari ganks on the deflate filter 57.BUG: look at Ben Moore's bug on ECONNABORTED 59.BUG: content-type not getting set If the folks mentioned could check this release against their problems then that will help quite a bit. Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From anjan.bacchu at Summit.Fiserv.com Fri Aug 11 15:53:06 2006 From: anjan.bacchu at Summit.Fiserv.com (Bacchu, Anjan) Date: Fri, 11 Aug 2006 12:53:06 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- PID Files Wor king Message-ID: 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 Working Hi Folks, An update to tell everyone to try out the pre-release again: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Nothing available for win32 yet, the next pre-release will have a win32 build to check that windows folks are OK. This release fixes the following problems: * PID files weren't being written when configured. Works now and logs messages better. * Small change to the HTTP parser to allow for headers that don't have a space after the ":" character, which is allowed by the RFC. -- Everyone using McAfee Security Center should contact them and tell them their product is a piece of crap. You should also consider not using it since they seem to be modifying people's HTTP requests in bogus ways and telling you that this is a "security" feature. This release is pretty close to becoming official. Everyone needs to test it out and shoot me any final problems. The current outstanding problems I have are: 55.BUG: test tom brice's upload app with keepalive 56.BUG: safari ganks on the deflate filter 57.BUG: look at Ben Moore's bug on ECONNABORTED 59.BUG: content-type not getting set If the folks mentioned could check this release against their problems then that will help quite a bit. Thanks! -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? _______________________________________________ Mongrel-users mailing list Mongrel-users at rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users From tom at onidle.com Fri Aug 11 17:53:59 2006 From: tom at onidle.com (Tom Brice) Date: Fri, 11 Aug 2006 16:53:59 -0500 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- PID Files Working In-Reply-To: <1155322736.5980.22.camel@localhost.localdomain> Message-ID: On 8/11/06 1:58 PM, Zed Shaw wrote: > This release is pretty close to becoming official. Everyone needs to > test it out and shoot me any final problems. The current outstanding > problems I have are: > > 55.BUG: test tom brice's upload app with keepalive Zed, I tested the app I sent you and it appears to be fixed. I'm having a few "lags" here and there but the 4 mongrel's I'm running do not appear to lock or run forever. Have commented out "KeepAlive Off" in my virtual host section and my browser confirms "Keep-Alive timeout=5, max=100". I would like to figure out how to tweak those values but that is a question for the apache folks. My testing is by no means scientific but it seems to be resolved. Thanks, Tom From bradley at railsmachine.com Fri Aug 11 20:12:35 2006 From: bradley at railsmachine.com (Bradley Taylor) Date: Fri, 11 Aug 2006 20:12:35 -0400 Subject: [Mongrel] [ANN] Mongrel Cluster 0.2.1 prerelease with prefix! In-Reply-To: References: Message-ID: <46B5C6E8-AF37-4C26-B3C7-7B4D83219E56@railsmachine.com> Hi all: I have update the mongrel_cluster prerelease to support the new "prefix" option in the Mongrel prerelease and include a rc script for FreeBSD. Thanks for the contributions from Andrew Bennett, Nat Brown, and Neil Wilson. Changes: - 'mongrel_rails cluster::restart' now calls 'mongrel_rails stop' and 'mongrel_rails start'. 'cluster::restart' now accepts the 'force' argument instead of 'soft'. - Added '.conf' as a valid file extension for mongrel_cluster_ctl. - Added check for missing script and directory to the init.d script. (Neil Wilson) - Added rc script for FreeBSD in resources/mongrel_cluster.sh (Andrew Bennett) - Added support for --prefix including Capistrano tasks (Nat Brown) Known issues: - mongrel_rails complains about missing pid or log files when using relative paths despite specifying 'chdir'. To fix, edit your mongrel_cluster conf file to use absolute paths . I will investigate this further this weekend, but I wanted to get the 'prefix' support out. If you don't need to use 'prefix' and you store your configuration outside of 'RAILS_ROOT/config', please wait for the next one. To install: gem install mongrel_cluster --source http:// railsmachine.rubyforge.org/releases/ Please submit bugs, patches, and requests to the RubyForge tracker: http://rubyforge.org/tracker/?group_id=1336 Let me know how it goes. Thanks, Bradley Taylor ------ Rails Optimized Hosting ~ VPS and Dedicated Servers Simplified Deployment ~ Services and Software http://railsmachine.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060811/e71f1a75/attachment.html From kraemer at webit.de Sat Aug 12 05:17:16 2006 From: kraemer at webit.de (Jens Kraemer) Date: Sat, 12 Aug 2006 11:17:16 +0200 Subject: [Mongrel] Telling Apache Not to Send a Sub-Directory to the Cluster In-Reply-To: References: Message-ID: <20060812091716.GC4149@cordoba.webit.de> Hi! On Thu, Aug 10, 2006 at 10:25:13AM -0700, HH wrote: > Howdy, > > I am using Apache 2.2 and Mongrel with great success. > > I have a mod_rewrite question and I am NO expert. I think it's really simple > but I haven't nailed it. I was hoping someone here could help. > > I'm using Apache conf right out of the cluster example from the Mongrel > site. I couldn't find that, so I'm assuming your rewrite rules look like this: RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule .* balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] > I have a directory under my apps 'public' directory called 'sendto'. Files > in that directory are accessible but I want to be able to provide a > directory listing for when no specific file is requested. > > Right now, it seems that the requests to http://domain.com/sendto/ are being > sent to the cluster. > > I am looking for a rewrite statement that basically tells Apache not to send > that specific URL pattern to the cluster. to achiee this, just add another RewriteCond line: RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_URI} !^/sendto RewriteRule .* balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L] this excludes requests pointing to URIs starting with /sendto from being sent via the balancer. Instead these requests will be served by Apache, and directory listings can be allowed with something like Options Indexes hth, Jens -- webit! Gesellschaft f?r neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Kr?mer kraemer at webit.de Schnorrstra?e 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 From luislavena at gmail.com Sat Aug 12 11:14:19 2006 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 12 Aug 2006 12:14:19 -0300 Subject: [Mongrel] Following your Mongrel thread In-Reply-To: References: Message-ID: <71166b3b0608120814n3372b42eod6e34954c078e9a@mail.gmail.com> On 8/11/06, Matthew Bass wrote: > Hello, Luis. I've been following your Mongrel thread here: > http://rubyforge.org/pipermail/mongrel-users/2006-May/000210.html > > I'm also running Win2K and have been trying to get Mongrel running as a > service, without much luck. I tried running daemon_test.rb like you said and > was able to get it to work, however, I had to add the lib directory to the > load path on the Ruby call, like so: > > ruby -I..\lib daemon_test.rb install > > Otherwise, I got an error about not being able to find win32/service. I'm > wondering if this has something to do with my problem running mongrel_rails > start? Every time I try to start the service, I get that message about it > "not starting in a timely manner." No error log or anything. > > I'd appreciate any advice you might have. > > Thanks, > Matt > > Hello Matt, I'm forwarding this to the list to everyone knows about it: win32-service (or win32/service) in its current state: sucks, but sucks badly. Part of the fault is ms side, their complex way to implement services is broken between releases of the NT OS. I maintain a few tools written in C as service for NT 4, later updated to 2000 and now XP (and 2003 server, if worth it). On all the 3-4 OS, it sometimes throw errors that make me look like an idiot. The other "guilty" is Ruby, with their protective green threads and their lack of scalability. Problems raises trying to get back from a C thread to ruby interpreter thread without breaking everything. A few weeks back, a patch was sent to Dan Berger to handle this in a pretty (or better) way... I cannot managed to make rails works good in it. Why? enter Thread-UN-Safety world! If I run a plain mongrel server, make it service and manage it... everything is ok. When you throw in all the fat Rails run... it crash... left threads behind... stop responding... I don't think is Rails fault! (this could be interpreted as a irony). Anyway, after all this mambo-jumbo, I guess will need to look into this. Call next week my "Solve the f*ckin win32-service problem so rails runs nicely on windows" week. Good weekend for everyone. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From luislavena at gmail.com Sat Aug 12 11:28:04 2006 From: luislavena at gmail.com (Luis Lavena) Date: Sat, 12 Aug 2006 12:28:04 -0300 Subject: [Mongrel] Getting "Invalid HTTP format, parsing fails." from one client In-Reply-To: <0FE26229-68B3-4F4E-A400-E1B8A550C898@mac.com> References: <9C06B0BB-D874-4E89-8499-5F7FE39C0507@mac.com> <1155236866.6001.4.camel@localhost.localdomain> <0FE26229-68B3-4F4E-A400-E1B8A550C898@mac.com> Message-ID: <71166b3b0608120828x1ddb305et49e82a8168f65fd1@mail.gmail.com> On 8/10/06, kigsteronline at mac.com wrote: > > Zed, > > I thought it had something to do with McAfee. You are right, she is using > their Security Center... That thing has gotten so unruly that we are all > switching to Norton (another beast). Ironic that anti-virus software often > gets more intrusive than the viruses themselves :) > > Thanks for the heads up. > Konstantin My suggestion is try NOD32 (www.eset.com) instead of Norton :) So far, been working with mongrel, rails, ruby on windows with NOD32 filtering HTTP and everything worked without problems. > > > On Aug 10, 2006, at 12:07 PM, Zed Shaw wrote: > > On Thu, 2006-08-10 at 10:28 -0700, kigsteronline at mac.com wrote: > 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. > > If you have McAffee Security Center installed then you need to do two > things: > > 1) Install the 0.3.13.4 pre-release of mongrel: gem install mongrel > --source=http://mongrel.rubyforge.org/releases/ > > 2) Contact McAffee and tell them why are they sending the aaaaaaaaaa: > ++++++++ header since that does absolutely nothing at all and is pretty > suspicious. > > Let me know if this works. > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > > Regards, > Konstantin > __________________________________________ > Blog on Tek, Art and Life @ http://tektastic.blogspot.com/ > Download hi-res mp3s @ http://www.polygroovers.com/ > Or order 2nd down-tempo album "Moods For Take Out" > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi From carl.lerche at verizon.net Sat Aug 12 12:53:42 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 11:53:42 -0500 (CDT) Subject: [Mongrel] Help mongrel keeps crashing... Message-ID: <22914626.1581911155401622209.JavaMail.root@vms062.mailsrvcs.net> 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 media files? ** Daemonized, any open files are closed. Look at log/mongrel.8130.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8130 ** Starting Rails with production environment ... ** Daemonized, any open files are closed. Look at log/mongrel.8131.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8131 ** Starting Rails with production environment ... ** Daemonized, any open files are closed. Look at log/mongrel.8132.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8132 ** Starting Rails with production environment ... ** Daemonized, any open files are closed. Look at log/mongrel.8133.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8133 (... more initialization stuff. Just the usual ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/40/13/431/media.wmv: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe (... a ton more broken pipe errors ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe (... a ton more broken pipe errors ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ images/header.png: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/31/1013/media.flv: Broken pipe (... a ton more broken pipe errors ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/83/1038/media.wmv: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/83/1038/media.wmv: Broken pipe (... a ton more broken pipe errors ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/83/1038/media.wmv: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe jWl50ivOcGhTQzEh5h5mQystOI0U2oDa4hXZY0VrqCCPd3HX151wmBwBYtPR (... and a bunch more gibberish and broken pipe errors ...) SuiOuNQ+jr9nJly0zLJx6xc1bCzIcW8pbbaQhDRUoqIaQ2NAPYB7B163EMTf b0gNr5K/usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 +acrI8k9prFuuKDrpZQUoUS5qoFQT+zvI0IA7DXqQherSISA0Y4/H 314aHIH59lY31UpcClFCdqgdVJ3akKBASQCe/RsUDBB7s3rcVHZ8vGmJZg6c (... and a bunch more gibberish and broken pipe errors ...) Y7a4lJCZCs6ZkAkpsyORvNrSIYa6OR6cZyFrXeaCFY6R2fEYCu3cXkSQhp8T IGDA5FSffjQye97tMzX2vO7Yt3jEawJ2v7yZNMvdvL0TSPhUUiXI9TNwy1M3 9uNa0JDKHRyop4vlHb/e5GhTrrpctDnxtVFLDzbyPa3/AError sending file /home2/ webapps/nfccms/releases/20060807071308/public/media/01/32/1023/media.flv: Broken pipe Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe (... a ton more broken pipe errors ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/93/1039/image-6.jpg: Broken pipe /home2/webapps/nfccms/current/config/../app/controllers/media_controller.rb: 104: warning: Object#id will be deprecated; use Object#object_id Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe (... a ton more broken pipe errors ...) Error sending file /home2/webapps/nfccms/releases/20060807071308/public/ media/01/32/1023/media.flv: Broken pipe /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb:582:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 582:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 636:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 625:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 956:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel.rb: 955:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:127:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/mongrel/ command.rb:199:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 K0f/TbrFtxG21uH AShA8dvBw7D8DhSyffClG7cO+TN3vDC+wTfs7oIhyX+u8ovpfoIWKPzPWeX+ (... and a bunch more gibberish till the end ...) From zedshaw at zedshaw.com Sat Aug 12 13:34:23 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 10:34:23 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <22914626.1581911155401622209.JavaMail.root@vms062.mailsrvcs.net> References: <22914626.1581911155401622209.JavaMail.root@vms062.mailsrvcs.net> Message-ID: <1155404063.6042.5.camel@localhost.localdomain> On Sat, 2006-08-12 at 11:53 -0500, Carl Lerche wrote: > 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. > Carl, try out the 0.3.13.14 pre-release when you get a chance: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Also remove sendfile: gem uninstall sendfile The broken pipe lines do mean that mongrel is serving static files, which isn't such a good way to set things up. Make sure you configure so that apache or lighttpd are serving the files. The gibberish looks like base64 encodings, which is really bothersome. You better be moved on to 1.1.6 by now. These could very well be someone trying to exploit your server. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From carl.lerche at verizon.net Sat Aug 12 13:49:42 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 12:49:42 -0500 (CDT) Subject: [Mongrel] Help mongrel keeps crashing... Message-ID: <8201328.1629911155404982484.JavaMail.root@vms069.mailsrvcs.net> Zed, Thanks for the suggestions. I will try out the pre-release and let you know how it goes. Also, I am using Apache 2.2.2 with mod_proxy_balancer (I probably should update to 2.2.3). I don't know what you mean by be on 1.1.6. I also don't have the sendfile gem as I know it is not recommended. As for mongrel serving static files, I will have to play with my mod_rewrite configuration as that is what seems to be the problem. I will include it here just in case anybody might have any suggestions for that. Thanks for all the help so far guys! -carl RewriteEngine On # Make sure people go to www.djforums.com, not djforums.com RewriteCond %{HTTP_HOST} ^djforums.com$ [NC] RewriteRule ^(.*)$ http://www.djforums.com.com$1 [R=301,L] # Yes, I've read no-www.com, but my site already has much Google-Fu on # www.blah.com. Feel free to comment this out. # Uncomment for rewrite debugging #RewriteLog logs/myapp_rewrite_log #RewriteLogLevel 9 # Check for maintenance file and redirect all requests RewriteCond %{DOCUMENT_ROOT}/system/maintenance.html -f RewriteCond %{SCRIPT_FILENAME} !maintenance.html RewriteRule ^.*$ /system/maintenance.html [L] # Rewrite index to check for static RewriteRule ^/$ /index.html [QSA] # Rewrite to check for Rails cached page RewriteRule ^([^.]+)$ $1.html [QSA] # Redirect all non-static requests to cluster RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ balancer://djforums%{REQUEST_URI} [P,QSA,L] RewriteCond %{HTTP_REFERER} !^$ RewriteCond %{HTTP_REFERER} !^http://(www.)?djforums.com.*$ [NC] RewriteRule .(gif|jpg|mov|flv|wmv|swf)$ - [F] From carl.lerche at verizon.net Sat Aug 12 14:10:00 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 13:10:00 -0500 (CDT) Subject: [Mongrel] Help mongrel keeps crashing... Message-ID: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> >Carl, try out the 0.3.13.14 pre-release when you get a chance: > >gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Ok, I'm probably doing something dumb, but for some reason mongrel isn't opening a log file (log/mongrel.log) anymore. I tried restarting a number of times (in production and development modes). Not having a log makes it hard to figure out what's going wrong. Any ideas? Thanks, Carl From zedshaw at zedshaw.com Sat Aug 12 14:24:14 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 11:24:14 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <8201328.1629911155404982484.JavaMail.root@vms069.mailsrvcs.net> References: <8201328.1629911155404982484.JavaMail.root@vms069.mailsrvcs.net> Message-ID: <1155407054.6042.11.camel@localhost.localdomain> On Sat, 2006-08-12 at 12:49 -0500, Carl Lerche wrote: > Zed, > > Thanks for the suggestions. I will try out the pre-release and let you know > how it goes. Also, I am using Apache 2.2.2 with mod_proxy_balancer (I > probably should update to 2.2.3). I don't know what you mean by be on 1.1.6. > I also don't have the sendfile gem as I know it is not recommended. "be on 1.1.6" means Rails 1.1.6. You MUST upgrade to this version of rails as there were serious security alerts because of an exploit that could destroy your whole application and probably get you fired AND I WILL NOT TALK TO YOU EVER AGAIN BECAUSE YOU WILL BE EMBARRASSING ME WAY TOO MUCH CARL. Sorry for the dramatics. Do that now. Now. Why are you reading this. Go! :-) -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Sat Aug 12 14:24:44 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 11:24:44 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> Message-ID: <1155407084.6042.12.camel@localhost.localdomain> On Sat, 2006-08-12 at 13:10 -0500, Carl Lerche wrote: > >Carl, try out the 0.3.13.14 pre-release when you get a chance: > > > >gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > Ok, I'm probably doing something dumb, but for some reason mongrel isn't > opening a log file (log/mongrel.log) anymore. I tried restarting a number of > times (in production and development modes). Not having a log makes it hard to > figure out what's going wrong. Any ideas? You'll have to edit your config files so that you set a full path. Zed From carl.lerche at verizon.net Sat Aug 12 15:17:07 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 14:17:07 -0500 (CDT) Subject: [Mongrel] Help mongrel keeps crashing... Message-ID: <18311170.1641351155410227933.JavaMail.root@vms069.mailsrvcs.net> >"be on 1.1.6" means Rails 1.1.6. You MUST upgrade to this version of >rails as there were serious security alerts because of an exploit that >could destroy your whole application and probably get you fired AND I >WILL NOT TALK TO YOU EVER AGAIN BECAUSE YOU WILL BE EMBARRASSING ME WAY >TOO MUCH CARL. Oh no... I'm a bad sys admin :( Anyway, I updated rails to 1.1.6, mongrel to the pre-release, removed the hot link protection from my mod_rewrite config which seems to send static files to apache now. The mongrel log file looks a lot healthier. I'll have to monitor it but I"m supposed to catch an international flight tonight, still haven't packed, still have to run errands AND get to the airport 4 hours early :-/ Better get workin... Thanks for all the help :) -carl From carl.lerche at verizon.net Sat Aug 12 16:10:44 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 13:10:44 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <1155407084.6042.12.camel@localhost.localdomain> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> Message-ID: <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> Alright, more trouble :( 2 mongrel processes have crashed since my last email. Here is the relevant mongrel.log bit: Sat Aug 12 14:32:02 CDT 2006: BAD CLIENT (127.0.0.1): HTTP element QUERY_STRING is longer than the (1024 * 10) allowed length. /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 597:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:597:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:664:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:664:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:651:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel/configurator.rb:258:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel/configurator.rb:257:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ mongrel_rails:128:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel/command.rb:203:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/ active_record/callbacks.rb:347: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i386-freebsd6] /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 597:in `close': Invalid argument (Errno::EINVAL) from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:597:in `process_client' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:664:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:664:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel.rb:651:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel/configurator.rb:258:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel/configurator.rb:257:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ mongrel_rails:128:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ mongrel/command.rb:203:in `run' from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/ mongrel_rails:235 from /usr/local/bin/mongrel_rails:18 /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/ active_record/callbacks.rb:347: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i386-freebsd6] From zedshaw at zedshaw.com Sat Aug 12 17:02:06 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 14:02:06 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> Message-ID: <1155416526.6042.15.camel@localhost.localdomain> What OS are you on Carl? It looks like Ruby sockets on *your* OS can throw yet another fantastic different exception in yet again another unusual situation that I have to cover all over again. I'll pump out a fix in five minutes, but let me know what OS you have (exact type, version, etc) so I can run more tests later. Zed On Sat, 2006-08-12 at 13:10 -0700, Carl Lerche wrote: > Alright, more trouble :( > > 2 mongrel processes have crashed since my last email. Here is the > relevant mongrel.log bit: > > Sat Aug 12 14:32:02 CDT 2006: BAD CLIENT (127.0.0.1): HTTP element > QUERY_STRING is longer than the (1024 * 10) allowed length. > /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: > 597:in `close': Invalid argument (Errno::EINVAL) > from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ > mongrel.rb:597:in `process_client' From zedshaw at zedshaw.com Sat Aug 12 18:01:42 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 15:01:42 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> Message-ID: <1155420102.6042.17.camel@localhost.localdomain> On Sat, 2006-08-12 at 13:10 -0700, Carl Lerche wrote: > Alright, more trouble :( > > 2 mongrel processes have crashed since my last email. Here is the > relevant mongrel.log bit: Alright Carl, should be fixed for good now. Try the pre-release AGAIN and report back to me. Thanks for the testing, you definately are the odd case here. gem install mongrel --source=http://mongrel.rubyforge.org/releases/ -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From carl.lerche at verizon.net Sat Aug 12 18:25:11 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 15:25:11 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <1155416526.6042.15.camel@localhost.localdomain> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> <1155416526.6042.15.camel@localhost.localdomain> Message-ID: <57AED5A8-7EDB-4036-B9FC-F49D91ECB0F9@verizon.net> Hey there, > uname -mrs FreeBSD 6.1-RELEASE i386 So, FreeBSD 6.1. I guess I jumped to 6 too early? Thanks, -carl On Aug 12, 2006, at 2:02 PM, Zed Shaw wrote: > What OS are you on Carl? It looks like Ruby sockets on *your* OS can > throw yet another fantastic different exception in yet again another > unusual situation that I have to cover all over again. > > I'll pump out a fix in five minutes, but let me know what OS you have > (exact type, version, etc) so I can run more tests later. > > Zed > > On Sat, 2006-08-12 at 13:10 -0700, Carl Lerche wrote: >> Alright, more trouble :( >> >> 2 mongrel processes have crashed since my last email. Here is the >> relevant mongrel.log bit: >> >> Sat Aug 12 14:32:02 CDT 2006: BAD CLIENT (127.0.0.1): HTTP element >> QUERY_STRING is longer than the (1024 * 10) allowed length. >> /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: >> 597:in `close': Invalid argument (Errno::EINVAL) >> from /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/ >> mongrel.rb:597:in `process_client' > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From maillist at steelskies.com Sat Aug 12 18:28:34 2006 From: maillist at steelskies.com (Jonathan del Strother) Date: Sat, 12 Aug 2006 23:28:34 +0100 Subject: [Mongrel] Mongrel 0.3.13.4 headers seem a bit broken... Message-ID: <4F4D08F6-3E55-4EBF-A804-E4A6E196A589@steelskies.com> 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 Date: Sat, 12 Aug 2006 22:13:41 GMT Set-Cookie: _session_id=e554ff2d043cb79b961cc033b6718b5e; path=/ Status: 302 Found Cache-Control: no-cache Server: Mongrel 0.3.13.3 Content-Type: text/html location: http://localhost:3000/login On 0.3.13.4, I get the same body back, but it doesn't redirect me. Here's the header : HTTP/1.1 404 Not Found Connection: close Date: Sat, 12 Aug 2006 22:19:33 GMT Content-Length: 93 Hmm. Odd... Similarly, rjs responses don't work for me in 0.3.13.4. I get this header : Connection: close Date: Sat, 12 Aug 2006 22:19:13 GMT Content-Length: 4850 and the browser just sits there. In 0.3.13.3, I get this header : Content-Length: 334 Connection: close Date: Sat, 12 Aug 2006 22:10:50 GMT Set-Cookie: _session_id=8df9b662a48e72c90d96cb9da9792491; path=/ Status: 200 OK Cache-Control: no-cache Server: Mongrel 0.3.13.3 Content-Type: text/javascript which works fine. Did I miss some vital step somewhere? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2114 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060812/f83dc80f/attachment.bin From zedshaw at zedshaw.com Sat Aug 12 18:35:17 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 15:35:17 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> Message-ID: <1155422117.6042.23.camel@localhost.localdomain> On Sat, 2006-08-12 at 13:10 -0700, Carl Lerche wrote: > Alright, more trouble :( > > 2 mongrel processes have crashed since my last email. Here is the > relevant mongrel.log bit: Carl, just to make sure, don't install these pre-releases in production just yet. I'm still working on them, just test them and let me know what happens. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From carl.lerche at verizon.net Sat Aug 12 18:46:22 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 15:46:22 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <1155420102.6042.17.camel@localhost.localdomain> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> <1155420102.6042.17.camel@localhost.localdomain> Message-ID: Zed, thanks for the quick response. I will try out the fix. Also, I didn't see my last email hit the mailing list yet. So, in case it didn't, I'm on FreeBSD 6.1-RELEASE i386 I'll let you know how the fix works. -carl On Aug 12, 2006, at 3:01 PM, Zed Shaw wrote: > On Sat, 2006-08-12 at 13:10 -0700, Carl Lerche wrote: >> Alright, more trouble :( >> >> 2 mongrel processes have crashed since my last email. Here is the >> relevant mongrel.log bit: > > Alright Carl, should be fixed for good now. Try the pre-release AGAIN > and report back to me. Thanks for the testing, you definately are the > odd case here. > > gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From carl.lerche at verizon.net Sat Aug 12 19:03:48 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 16:03:48 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <1155422117.6042.23.camel@localhost.localdomain> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> <1155422117.6042.23.camel@localhost.localdomain> Message-ID: <9E937771-666D-40E9-9211-2E6F8C1FCBA9@verizon.net> Alright, will do. Anyway, I'm having the same problem that Jonathan del Strother just emailed in. The headers sent are 404 and then it just dumps the HTML source as text into the browser. Here are the headers I'm getting: HTTP/1.1 404 Not Found Date: Sat, 12 Aug 2006 23:02:52 GMT Content-Length: 35144 Content-Type: text/plain; charset=ISO-8859-1 -carl > > Carl, just to make sure, don't install these pre-releases in > production > just yet. I'm still working on them, just test them and let me know > what happens. > From zedshaw at zedshaw.com Sat Aug 12 19:29:37 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 16:29:37 -0700 Subject: [Mongrel] Mongrel 0.3.13.4 headers seem a bit broken... In-Reply-To: <4F4D08F6-3E55-4EBF-A804-E4A6E196A589@steelskies.com> References: <4F4D08F6-3E55-4EBF-A804-E4A6E196A589@steelskies.com> Message-ID: <1155425377.6042.28.camel@localhost.localdomain> On Sat, 2006-08-12 at 23:28 +0100, Jonathan del Strother wrote: > 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 : Yep, just caught that and fixed it up. Grab the pre-release again and test for me. Getting closer, but as usual don't run this in production just yet. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Sat Aug 12 19:30:22 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sat, 12 Aug 2006 16:30:22 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> <1155420102.6042.17.camel@localhost.localdomain> Message-ID: <1155425422.6042.30.camel@localhost.localdomain> On Sat, 2006-08-12 at 15:46 -0700, Carl Lerche wrote: > Zed, thanks for the quick response. I will try out the fix. Also, I > didn't see my last email hit the mailing list yet. So, in case it > didn't, I'm on FreeBSD 6.1-RELEASE i386 > > I'll let you know how the fix works. Carl, ok, the redirect problem is fixed, grab the one I just posted (Aug 12, 4:30pm PDT). Let me know if the outcome. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From maillist at steelskies.com Sat Aug 12 21:37:03 2006 From: maillist at steelskies.com (Jonathan del Strother) Date: Sun, 13 Aug 2006 02:37:03 +0100 Subject: [Mongrel] Mongrel 0.3.13.4 headers seem a bit broken... In-Reply-To: <1155425377.6042.28.camel@localhost.localdomain> References: <4F4D08F6-3E55-4EBF-A804-E4A6E196A589@steelskies.com> <1155425377.6042.28.camel@localhost.localdomain> Message-ID: <1B6D39C7-0B12-4180-AD85-81B2772ABB45@steelskies.com> On 13 Aug 2006, at 00:29, Zed Shaw wrote: > On Sat, 2006-08-12 at 23:28 +0100, Jonathan del Strother wrote: >> 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 : > > Yep, just caught that and fixed it up. Grab the pre-release again and > test for me. Nice work, seems to be all fixed now -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2114 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060813/165c4213/attachment.bin From carl.lerche at verizon.net Sun Aug 13 00:49:07 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Sat, 12 Aug 2006 21:49:07 -0700 Subject: [Mongrel] Help mongrel keeps crashing... In-Reply-To: <1155425422.6042.30.camel@localhost.localdomain> References: <5655007.1632801155406200972.JavaMail.root@vms069.mailsrvcs.net> <1155407084.6042.12.camel@localhost.localdomain> <23507832-3AA3-4784-90A8-951075BE946B@verizon.net> <1155420102.6042.17.camel@localhost.localdomain> <1155425422.6042.30.camel@localhost.localdomain> Message-ID: Zed, thanks for the quick fixes. I am running the latest pre-release and will let you know what happens. Thanks, Carl On Aug 12, 2006, at 4:30 PM, Zed Shaw wrote: > On Sat, 2006-08-12 at 15:46 -0700, Carl Lerche wrote: >> Zed, thanks for the quick response. I will try out the fix. Also, I >> didn't see my last email hit the mailing list yet. So, in case it >> didn't, I'm on FreeBSD 6.1-RELEASE i386 >> >> I'll let you know how the fix works. > > Carl, ok, the redirect problem is fixed, grab the one I just posted > (Aug > 12, 4:30pm PDT). Let me know if the outcome. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From zedshaw at zedshaw.com Mon Aug 14 03:02:03 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 00:02:03 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem Message-ID: <1155538923.15237.15.camel@localhost.localdomain> 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/ And this time pick the *right* one for your system. CHANGES * All the outstanding bugs on the rubyforge bug list are now closed off. Reopen any that are not really fixed. * PID files are found when stop/restart and this is now part of the full test suite. * HTTP headers with no spacing at all are now accepted for real I promise and with a test to make sure. * Fixes a *major* problem with how output was processed and Rails locking (I blame the stupid Katana patch, but not really). * FreeBSD 6.1 now throws a brand new Errno exception for closed sockets that nobody else throws. This has caused me to sprinkle "rescue Object" after every socket.close to make sure that--yes--the socket really closes. If anyone wants to try and help changing Ruby's Socket from "Ultimate Errno Randomness Generator" into something sane then let me know because it's seriously pissing me the hell off. LOCKING Previously I was under the delusion that Mongrel was running rails and then sending the response outside of any locking. This wasn't really true for various complex reasons (mainly that I'm a dumbass) but now this is the case. Since most coders cannot get their heads around this to save their lives (myself included), I've done this diagram which seems to help: B-E-F-O-R-E 0.3.13.4 request -> lock -> rails -> response -> unlock -> done A-F-T-E-R 0.3.13.4 request -> lock -> rails -> unlock -> response -> done This also probably fixes people who's Mongrels would lock up sometimes as previously there was a rare chance that if a socket (remember the randomness) got stuck then the process would lock up. Now only one thread locks up (which is still a problem). Please test this release on everything you can and shoot me back results. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From jan.svitok at gmail.com Mon Aug 14 05:33:06 2006 From: jan.svitok at gmail.com (Jan Svitok) Date: Mon, 14 Aug 2006 11:33:06 +0200 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem In-Reply-To: <1155538923.15237.15.camel@localhost.localdomain> References: <1155538923.15237.15.camel@localhost.localdomain> Message-ID: <8d9b3d920608140233y7e395f4am8f1f851223a3b351@mail.gmail.com> On 8/14/06, Zed Shaw wrote: > 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/ > > And this time pick the *right* one for your system. Seems like the gem index (yaml) contains 0.3.12.4-win32 only. Could you update the index please? I'm checking the patch - now I've found that line line shouldn't be there. This is updated patch against current svn (325) (removes the line, and adds --startup-type) I haven't tested it yet today. Jano -------------- next part -------------- A non-text attachment was scrubbed... Name: diff Type: application/octet-stream Size: 2689 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060814/dda77de9/attachment.obj From jan.svitok at gmail.com Mon Aug 14 08:00:10 2006 From: jan.svitok at gmail.com (Jan Svitok) Date: Mon, 14 Aug 2006 14:00:10 +0200 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem In-Reply-To: <8d9b3d920608140233y7e395f4am8f1f851223a3b351@mail.gmail.com> References: <1155538923.15237.15.camel@localhost.localdomain> <8d9b3d920608140233y7e395f4am8f1f851223a3b351@mail.gmail.com> Message-ID: <8d9b3d920608140500h2c40b469u4445f21a4a7a366b@mail.gmail.com> On 8/14/06, Jan Svitok wrote: > On 8/14/06, Zed Shaw wrote: > > 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/ > > > > And this time pick the *right* one for your system. > > Seems like the gem index (yaml) contains 0.3.12.4-win32 only. Could > you update the index please? I've downloaded the gem manually (0.3.13.4-win32), and it doesn't contain compiled extension. Do you cross-compile or do you use oneclick+ some compiler? (latest oneclick 1.8.4-20 is compiled by msvc and it complained about my vc7 compiler -- config.h line 2) J. From jgeiger at gmail.com Mon Aug 14 09:46:55 2006 From: jgeiger at gmail.com (Joey Geiger) Date: Mon, 14 Aug 2006 08:46:55 -0500 Subject: [Mongrel] [ANN] Mongrel Cluster 0.2.1 prerelease with prefix! In-Reply-To: <46B5C6E8-AF37-4C26-B3C7-7B4D83219E56@railsmachine.com> References: <46B5C6E8-AF37-4C26-B3C7-7B4D83219E56@railsmachine.com> Message-ID: <466af3440608140646g46eab985h640e7ca688237d9f@mail.gmail.com> What changes would I need to make to my configuration file to enable the prefix support? Thanks. --- user: user cwd: /web/servers/website.com/rails port: "8001" environment: development group: group address: 127.0.0.1 pid_file: log/mongrel.pid servers: 3 On 8/11/06, Bradley Taylor wrote: > > Hi all: > > I have update the mongrel_cluster prerelease to support the new "prefix" > option in the Mongrel prerelease and include a rc script for FreeBSD. Thanks > for the contributions from Andrew Bennett, Nat Brown, and Neil Wilson. > > Changes: > - 'mongrel_rails cluster::restart' now calls 'mongrel_rails stop' and > 'mongrel_rails start'. 'cluster::restart' now accepts the 'force' argument > instead of 'soft'. > - Added '.conf' as a valid file extension for mongrel_cluster_ctl. > - Added check for missing script and directory to the init.d script. (Neil > Wilson) > - Added rc script for FreeBSD in resources/mongrel_cluster.sh (Andrew > Bennett) > - Added support for --prefix including Capistrano tasks (Nat Brown) > > Known issues: > - mongrel_rails complains about missing pid or log files when using relative > paths despite specifying 'chdir'. To fix, edit your mongrel_cluster conf > file to use absolute paths . I will investigate this further this weekend, > but I wanted to get the 'prefix' support out. If you don't need to use > 'prefix' and you store your configuration outside of 'RAILS_ROOT/config', > please wait for the next one. > > To install: > gem install mongrel_cluster --source > http://railsmachine.rubyforge.org/releases/ > > Please submit bugs, patches, and requests to the RubyForge tracker: > http://rubyforge.org/tracker/?group_id=1336 > Let me know how it goes. > > Thanks, > Bradley Taylor > > ------ > Rails Optimized Hosting ~ VPS and Dedicated Servers > Simplified Deployment ~ Services and Software > http://railsmachine.com > > > > > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From bradley at railsmachine.com Mon Aug 14 11:42:57 2006 From: bradley at railsmachine.com (Bradley Taylor) Date: Mon, 14 Aug 2006 11:42:57 -0400 Subject: [Mongrel] [ANN] Mongrel Cluster 0.2.1- Last Call Message-ID: <531208C8-88B9-4A65-B236-FBEAE5003307@railsmachine.com> Hi all: Here's a pre-release for mongrel_cluster to support current Mongrel 0.3.13.4 pre-release. Changes: - 'mongrel_rails cluster::restart' now calls 'mongrel_rails stop' and 'mongrel_rails start'. 'cluster::restart' now accepts the 'force' argument instead of 'soft'. - Added '.conf' as a valid file extension for mongrel_cluster_ctl. - Added check for missing script and directory to the init.d script. (Neil Wilson) - Added rc script for FreeBSD in resources/mongrel_cluster.sh (Andrew Bennett) - Added support for --prefix including Capistrano tasks (Nat Brown) Thanks for the contributions from Andrew Bennett, Nat Brown, and Neil Wilson. To install: sudo gem install mongrel --source=http://mongrel.rubyforge.org/releases/ sudo gem install mongrel_cluster --source http:// railsmachine.rubyforge.org/releases/ Please submit bugs, patches, and requests to the RubyForge tracker: http://rubyforge.org/tracker/?group_id=1336 Let me know how it goes. Thanks, Bradley Taylor ------ Rails Optimized Hosting ~ VPS and Dedicated Servers Simplified Deployment ~ Services and Software http://railsmachine.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060814/80b70a3e/attachment-0001.html From bradley at railsmachine.com Mon Aug 14 11:57:53 2006 From: bradley at railsmachine.com (Bradley Taylor) Date: Mon, 14 Aug 2006 11:57:53 -0400 Subject: [Mongrel] [ANN] Mongrel Cluster 0.2.1 prerelease with prefix! In-Reply-To: <466af3440608140646g46eab985h640e7ca688237d9f@mail.gmail.com> References: <46B5C6E8-AF37-4C26-B3C7-7B4D83219E56@railsmachine.com> <466af3440608140646g46eab985h640e7ca688237d9f@mail.gmail.com> Message-ID: <1F05CBCD-C7E8-4C17-B6A0-4BF510E6E9BC@railsmachine.com> On Aug 14, 2006, at 9:46 AM, Joey Geiger wrote: > What changes would I need to make to my configuration file to enable > the prefix support? > > Thanks. > > --- > user: user > cwd: /web/servers/website.com/rails > port: "8001" > environment: development > group: group > address: 127.0.0.1 > pid_file: log/mongrel.pid > servers: 3 > Add "prefix:" with the same value you that would pass to mongrel_rails on the command line. You could also rerun mongrel_rails cluster::configure and regenerate it. Thanks, Bradley ------ Rails Optimized Hosting ~ VPS and Dedicated Servers Simplified Deployment ~ Services and Software http://railsmachine.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060814/caf9b6b0/attachment.html From jgeiger at gmail.com Mon Aug 14 12:21:30 2006 From: jgeiger at gmail.com (Joey Geiger) Date: Mon, 14 Aug 2006 11:21:30 -0500 Subject: [Mongrel] [ANN] Mongrel Cluster 0.2.1- Last Call In-Reply-To: <531208C8-88B9-4A65-B236-FBEAE5003307@railsmachine.com> References: <531208C8-88B9-4A65-B236-FBEAE5003307@railsmachine.com> Message-ID: <466af3440608140921p2c7a76f4j81520cd191232efc@mail.gmail.com> I'm not sure if this is a bug, or a working as intended, but when I configure my application to server images/js/css from an external server like this: # Enable serving of images, stylesheets, and javascripts from an asset server config.action_controller.asset_host = "http://dev.website.com" The files as created by the rails commands: <%= stylesheet_link_tag 'main', 'mozilla-pc' %> <%= javascript_include_tag :defaults %> are then sent to the browser as: with the extra /app thrown in there. I would hope that if I'm using an external server, there is a way to disable having the prefix thrown into the urls. Otherwise so far it's working as expected for me. Thanks. From zedshaw at zedshaw.com Mon Aug 14 13:43:33 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 10:43:33 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem In-Reply-To: <8d9b3d920608140233y7e395f4am8f1f851223a3b351@mail.gmail.com> References: <1155538923.15237.15.camel@localhost.localdomain> <8d9b3d920608140233y7e395f4am8f1f851223a3b351@mail.gmail.com> Message-ID: <1155577413.6099.1.camel@localhost.localdomain> On Mon, 2006-08-14 at 11:33 +0200, Jan Svitok wrote: > On 8/14/06, Zed Shaw wrote: > Seems like the gem index (yaml) contains 0.3.12.4-win32 only. Could > you update the index please? > > >From my checks it's there: ~> gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Attempting local installation of 'mongrel' Local gem file not found: mongrel*.gem Attempting remote installation of 'mongrel' Select which gem to install for your platform (i486-linux) 1. mongrel 0.3.13.4 (ruby) 2. mongrel 0.3.12.4 (mswin32) 3. Cancel installation Maybe windows doesn't like it for some reason? I'll reload tonight and double check. > I'm checking the patch - now I've found that line line shouldn't be there. > This is updated patch against current svn (325) (removes the line, and > adds --startup-type) > I haven't tested it yet today. I'll try working this in today. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Mon Aug 14 13:45:11 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 10:45:11 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 -- PIDs Work, Win32 Gem In-Reply-To: <8d9b3d920608140500h2c40b469u4445f21a4a7a366b@mail.gmail.com> References: <1155538923.15237.15.camel@localhost.localdomain> <8d9b3d920608140233y7e395f4am8f1f851223a3b351@mail.gmail.com> <8d9b3d920608140500h2c40b469u4445f21a4a7a366b@mail.gmail.com> Message-ID: <1155577511.6099.4.camel@localhost.localdomain> On Mon, 2006-08-14 at 14:00 +0200, Jan Svitok wrote: > On 8/14/06, Jan Svitok wrote: > I've downloaded the gem manually (0.3.13.4-win32), and it doesn't > contain compiled extension. Do you cross-compile or do you use > oneclick+ some compiler? (latest oneclick 1.8.4-20 is compiled by msvc > and it complained about my vc7 compiler -- config.h line 2) Oh, I see what's wrong now. I uploaded 0.3.12.4 on accident somehow. I'll fix it up and try the win32 release again. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Mon Aug 14 13:47:10 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 10:47:10 -0700 Subject: [Mongrel] [ANN] Mongrel Cluster 0.2.1- Last Call In-Reply-To: <466af3440608140921p2c7a76f4j81520cd191232efc@mail.gmail.com> References: <531208C8-88B9-4A65-B236-FBEAE5003307@railsmachine.com> <466af3440608140921p2c7a76f4j81520cd191232efc@mail.gmail.com> Message-ID: <1155577630.6099.7.camel@localhost.localdomain> On Mon, 2006-08-14 at 11:21 -0500, Joey Geiger wrote: > I'm not sure if this is a bug, or a working as intended, but when I > configure my application to server images/js/css from an external > server like this: > with the extra /app thrown in there. I would hope that if I'm using an > external server, there is a way to disable having the prefix thrown > into the urls. Otherwise so far it's working as expected for me. That's a Rails thing, not a Mongrel thing. Basically you said mount at /app, so that's what it's doing. Most likely it goes through generating URLs such that /app is always included. I'd suggest just changing your asset host so you can stay on the rails. :-) -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Mon Aug 14 17:20:10 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 14:20:10 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 -- All Praise Win32 Message-ID: <1155590410.6248.17.camel@localhost.localdomain> Hey Win32 folks, I messed up the win32 gem for my last Pre-Release announce. Please grab it again with: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And make sure your apps work with it. Nothing else has changed, but there will be another release for win32 tomorrow. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From carl.lerche at verizon.net Mon Aug 14 17:25:26 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Mon, 14 Aug 2006 14:25:26 -0700 Subject: [Mongrel] More mongrel pre-release crashes Message-ID: Alright, here are some more outputs of the log for the latest pre- release of mongrel. I'm just copying the relevant stuff: ERROR reading http body: Socket closed or read failure Mon Aug 14 00:00:02 CDT 2006: ERROR: undefined method `rewind' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 221:in `initialize' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 555:in `process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 664:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 664:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 651:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ configurator.rb:267:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ configurator.rb:266:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails: 127:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ command.rb:203:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:233 /usr/local/bin/mongrel_rails:18 Mon Aug 14 10:39:55 CDT 2006: ERROR: failed to allocate memory /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 536:in `readpartial' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 536:in `process_client' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 664:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 664:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: 651:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ configurator.rb:267:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ configurator.rb:266:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails: 127:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel/ command.rb:203:in `run' /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:233 /usr/local/bin/mongrel_rails:18 [FATAL] failed to allocate memory Also, what does it mean when I see a bunch of gibberish in the log file like as follows? You mentioned base64 stuff, how is it sent to the log file? I tried to decode a line and I get the following: '"GIF89aM\0009\000\367\000\000\000\000\000\377\377\377\037\037 \203_d \304\227\235\246{\204\216kr\256\211\221\255\233\240\225nz\233u"' Thanks, -carl R0lGODlhTQA5APcAAAAAAP///x8fIINfZMSXnaZ7hI5rcq6Jka2boJVuept1 gUs2PqGCjm5QXF5BTp9zjoNtgY9/jol5iSMgIx8dH/nv+SAfINnX2R4YH3dl ehgTGZqJnaKRpWdaaisjLS4lMVRGWSsgMBsVHh8dIMnFy1tSYXpxgWtjcjky QKWerEdESnh1e1hWWk1GVh4YJl9VbX5yjn16gSUfLikjMjMuO42DnB0bICQi JywqL768wTUtQiwkO05EYEQ8VV1ZZRsaHbWvwTw6QEFAQ2dgeC8sNoeBlVhR a2xmfM/L2j4zXZeNtZybnx4ZLxgWH0dBWiknMH54kXRvhZOOo/f1/jo2SSAe KCYkLkRBUFRRYB0cIXh0hx8eI3x4izU0OWVkaa2ssWJfcGxqdTYyS1JOZnVw kbWt3U1KXCEgJuXj8B8dLCMhMCknNp2ZttvW+V5ca0lITy8sRWBcgUlGYi4s PGtnhyQjK4KAknJxeVhVdE9OWDAuThwbKSQjNGpnlyAfLD08S1BPX6Siv9LQ 8jo5VCopPKSi23FwjH9+ns/O+8vK8B8fSUBAahcXIyAgL4aGwxoaJDAwQCAg Kbu76YaGpx0dJI+PrJWVsx8fJampxXBwgG9vfn9/jiYmKiAgIzAwMx8fIRoa G46Okx0dHiUlJoeHif39//v7/Pj4+eDg4VxelJGSyE9QbMTF6bW21z0/XnZ5 tM/R/97g/7m6y0dKcHBzn1pcetPW/q+y0sTJ/Ly/2iUqUFNaiJae1sTG1O7w /1BWfauwy9jg/+Hn/szR49Le/9nb4fj5/O7v8tPU12ZwhiAlL7W2uNzl9O/1 /2JugOfw/uHv//Lz9OXm5/D6/8zOz/v+/+/+//T//xwdHfX29uvs7BwfHSU9 KRoxHTJKNRAoEj5XQAcgB/3+/YuOiXJzcPDy5uDjzOvu2cHDtC0uJd7ivvj6 6v7/9v7/8R4eHCAgH///+15eXf///v39/Pr6+aCbi9fTyoaBeSQcGuXe3R4a Gv7+/iAgIB8fHx4eHv///yH5BAEAAP8ALAAAAABNADkAAAj/ALsJ7PYtnEGD 3bhx88ZtYEKFDAkenEixosWL4b518waO4cKOAgsedEbS2ZUqVahoydGrUiYu dooAuQWkppQYJYI88eOnioWfQIP+HGHhk9Cg/DopPbMlzZwW1AIwqzXLUqAM IBbo2GEkkJSSzlZFATJMlhRDmGpEqRFIFpBKR67MqZOmyqdIPQUI6NdPr1+9 fM/IONP3794zjfxcGsUpyBssX4pZ0qUIzpwdOnoYMUKHzCRnyUhWilXpFy1L wNDkahWohiEoTpgwUbxl76dPffkW/qu7zgfCfy1QEDXCzwwP+oQskWbsmHNZ k7Qc6dDBSI8kcWbFqYUHz6pDwHbR/8KkypIlQ0aoqFEJKI3i3IAp6C6sG7C/ G11u+BMg6gcoUJ08QQQRVXgSTz1f2ANPAPsEEIA8F6zgAwhYkKFEGYkkUkst yRzSiyCs3DJJMnLAwcceaexBwyY+UMKXYQJQYFh9uvnDiQoeaKDBBF28wYIP LAx4BzLyBFBOOew4GMApqCzjwxeoVDBFG2WoosokmISISShu/AEJH2mk0cgZ /PjjyT1eYLMbjGz+9cMoIBChggkpfFHDCSCEoAIJ8hQpDzzyZHNBNKaIkw0y OVwgjSw1xNGHKoVgYgkUchCS4h57NKJpI528008695DjTj/8tNkmBiJoIAIK JXCQAwkRyP8lww0e5NCgkg5eQA098zgIzzFhvKEDHEnQUkghgECSKSBXpBGJ From john at fivesquaresoftware.com Mon Aug 14 17:33:16 2006 From: john at fivesquaresoftware.com (John Clayton) Date: Mon, 14 Aug 2006 14:33:16 -0700 Subject: [Mongrel] Mongrel loading wrong database environment (& a couple other bugs?) Message-ID: Hi There, I've got a mongrel cluster running on redhat 9 proxied behind an Apache 2.2 installation. I have run into a real stumbling block in that, while the rails app runs in production mode (you get a production.log file, for example, and I see this in the mongrel log: ** Starting Rails with production environment ... ), it always loads the development database configuration no matter what. I can re- config the file, move things around, with no effect. Has anyone else noticed this? I'm starting up mongrel using the mongrel_cluster_ctl script from /et/ init.d/mongrel_cluster as suggested in the docs. You can see my config file below. I've also noticed a couple other issues. 1. When specifying a pid file that's not in the default, you can start up mongrel fine and it writes the pid(s, this is clustered) to the correct location, say /tmp/mongrel.*.pid, but the stop command always tries to find the pid in /path/to/docroot/log/tmp/ mongrel.*.pid, basically appending the absolute path to the default location. This is handy if you want to move symlinks around and still have the ctl script find the pids. 2. the -r (--root) option and the :docroot yml pair don't seem to have any effect whatsoever. Thanks for any help you can offer, John Clayton My mongrel versions: mongrel (0.3.13.3) A small fast HTTP library and server that runs Rails, Camping, and Nitro apps. mongrel_cluster (0.2.0) Mongrel plugin that provides commands and Capistrano tasks for managing multiple Mongrel processes. My config file: --- user: mongrel cwd: /var/www/example.com/app/current/ port: "8000" environment: production debug: false group: instrument address: 127.0.0.1 pid_file: log/mongrel.pid servers: 3 From lists at lastonepicked.com Mon Aug 14 20:11:24 2006 From: lists at lastonepicked.com (HH) Date: Mon, 14 Aug 2006 17:11:24 -0700 Subject: [Mongrel] 0.3.13.4 w/ File Upload Progress? Message-ID: So, do these new shiny 0.3.13.4 releases have the previously mentioned upload progress stuff baked in and ready to use? H From zedshaw at zedshaw.com Mon Aug 14 20:13:59 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 17:13:59 -0700 Subject: [Mongrel] More mongrel pre-release crashes In-Reply-To: References: Message-ID: <1155600839.6158.8.camel@localhost.localdomain> On Mon, 2006-08-14 at 14:25 -0700, Carl Lerche wrote: > Alright, here are some more outputs of the log for the latest pre- > release of mongrel. I'm just copying the relevant stuff: > Carl, what the hell are you doing to my software. :-) Nah, this is good, but I'm really curious what your app is, it seems to really stretch boundaries. > ERROR reading http body: Socket closed or read failure > Mon Aug 14 00:00:02 CDT 2006: ERROR: undefined method `rewind' for > nil:NilClass Ah, right before this should have been a socket read failure message. Can you send that on to me. I've fixed this and will do another pre-release. Also, does this crash the server? It shouldn't. > > Mon Aug 14 10:39:55 CDT 2006: ERROR: failed to allocate memory > /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/lib/mongrel.rb: > 536:in `readpartial' Ok, you're on your own here. You've basically run out of ram so--kaboom! If you have rails actions that are loading tons of data, consider forcing that data =nil and call GC.start. Before and after filters are good for this. > Also, what does it mean when I see a bunch of gibberish in the log > file like as follows? You mentioned base64 stuff, how is it sent to > the log file? I tried to decode a line and I get the following: > '"GIF89aM\0009\000\367\000\000\000\000\000\377\377\377\037\037 \203_d > \304\227\235\246{\204\216kr\256\211\221\255\233\240\225nz\233u"' > Looks like it's sending an image, but I've no idea why it'd put that int here since I don't have the full log. It could mean that your configuration isn't setup properly since Mongrel seems to be serving files. I'd like to find out why you get this message, so if you can send me a zip of your logs and maybe a detailed description of what your app does then I can try to find out what causes those. Send it to me off list so that you can keep it a secret (if you need to). -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Mon Aug 14 20:18:27 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 17:18:27 -0700 Subject: [Mongrel] Mongrel loading wrong database environment (& a couple other bugs?) In-Reply-To: References: Message-ID: <1155601107.6158.12.camel@localhost.localdomain> On Mon, 2006-08-14 at 14:33 -0700, John Clayton wrote: > Hi There, > > I've got a mongrel cluster running on redhat 9 proxied behind an > Apache 2.2 installation. I have run into a real stumbling block in > that, while the rails app runs in production mode (you get a > production.log file, for example, and I see this in the mongrel log: > ** Starting Rails with production environment ... ), it always loads > the development database configuration no matter what. I can re- > config the file, move things around, with no effect. Has anyone else > noticed this? Not sure what Mongrel would do to cause this, and since many other people are running in production with Mongrel you should double check your database.yml config and your database config. Best thing to do is remove *everything* from database.yml except your production setup, and remove all databases except your production database. But, uh don't do this on real production, do it some test environment. If you do this then you'll quickly find out why it's wrong and can go fix your configuration. > 1. When specifying a pid file that's not in the default, you can > start up mongrel fine and it writes the pid(s, this is clustered) to > the correct location, say /tmp/mongrel.*.pid, but the stop command > always tries to find the pid in /path/to/docroot/log/tmp/ > mongrel.*.pid, basically appending the absolute path to the default > location. > This is fixed in the 0.3.13.4 pre-release. If you have a chance, double confirm it by installing the pre-release on your development or staging system: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > This is handy if you want to move symlinks around and still have the > ctl script find the pids. > > 2. the -r (--root) option and the :docroot yml pair don't seem to > have any effect whatsoever. > Can you describe this a bit better? Also tell me if you see this stil with the pre-release. Oh, one more thing, also make sure that your setup runs in production *without* mongrel_cluster and with webrick. If it works in plain mongrel then it might be a mongrel_cluster bug. If it works with webrick then it might be a mongrel bug. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From tgw529 at gmail.com Mon Aug 14 20:48:43 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Mon, 14 Aug 2006 20:48:43 -0400 Subject: [Mongrel] Start up error Message-ID: <1d6e22490608141748v165e003ck122c0832b04a5231@mail.gmail.com> I am a complete newbie and am having trouble getting mongrel started up. I cannot find any info about this error. If you can help at all, I would be very grateful. Here is the error I get when I try and start my rails app with mongrel. I have reomved and reinstalled Rails, Ruby, Daemons, and Mongrel based on some other articles I found on this list. PLEASE HELP! tim at rome:/www/app.tickspot.com$ sudo mongrel_rails start -e developement -p 80 ** Starting Mongrel listening at 0.0.0.0:80 ** Starting Rails with developement environment ... /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:168:in `read': No such file or directory - /www/app.tickspot.com/config/../config/environments/developement.rb (Errno::ENOENT) from /usr/lib/ruby/gems/1.8/gems/rails- 1.1.6/lib/initializer.rb:168:in `load_environment' from /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/core_ext/kernel/reporting.rb:11:in `silence_warnings' from /usr/lib/ruby/gems/1.8/gems/rails- 1.1.6/lib/initializer.rb:165:in `load_environment' from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:82:in `process' from /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:42:in `run' from /www/app.tickspot.com/config/environment.rb:13 from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:21:in `require' from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.2/lib/mongrel/rails.rb:156:in`rails' from /usr/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.2/bin/mongrel_rails:104:in `cloaker_' from /usr/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.2/lib/mongrel.rb:845:in `listener' from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.2/bin/mongrel_rails:91:in `cloaker_' from /usr/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.2/lib/mongrel.rb:763:in `initialize' from /usr/lib/ruby/gems/1.8/gems/mongrel-0.3.13.2/bin/mongrel_rails:78:in`run' from /usr/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.2/lib/mongrel/command.rb:211:in `run' from /usr/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.2/bin/mongrel_rails:227 from /usr/bin/mongrel_rails:18 -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060814/1d8d029a/attachment.html From francois.beausoleil at gmail.com Mon Aug 14 21:02:50 2006 From: francois.beausoleil at gmail.com (Francois Beausoleil) Date: Mon, 14 Aug 2006 21:02:50 -0400 Subject: [Mongrel] Start up error In-Reply-To: <1d6e22490608141748v165e003ck122c0832b04a5231@mail.gmail.com> References: <1d6e22490608141748v165e003ck122c0832b04a5231@mail.gmail.com> Message-ID: <41d5fadf0608141802n4cc4a9c0m24301d5d23387a84@mail.gmail.com> Hello Timothy, 2006/8/14, Timothy Wright : > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:168:in > `read': No such file or directory - > /www/app.tickspot.com/config/../config/environments/developement.rb > (Errno::ENOENT) Message says it all: No such file or directory Make sure that file exists, and if not, you'll need to create it. Hope that helps ! -- Fran?ois Beausoleil http://blog.teksol.info/ From tgw529 at gmail.com Mon Aug 14 21:04:45 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Mon, 14 Aug 2006 21:04:45 -0400 Subject: [Mongrel] Start up error In-Reply-To: <41d5fadf0608141802n4cc4a9c0m24301d5d23387a84@mail.gmail.com> References: <1d6e22490608141748v165e003ck122c0832b04a5231@mail.gmail.com> <41d5fadf0608141802n4cc4a9c0m24301d5d23387a84@mail.gmail.com> Message-ID: <1d6e22490608141804l7088bcd9yb07e2d92378f3f59@mail.gmail.com> Just got. It mispelled development On 8/14/06, Francois Beausoleil wrote: > > Hello Timothy, > > 2006/8/14, Timothy Wright : > > /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:168:in > > `read': No such file or directory - > > /www/app.tickspot.com/config/../config/environments/developement.rb > > (Errno::ENOENT) > > Message says it all: > > No such file or directory > > Make sure that file exists, and if not, you'll need to create it. > > Hope that helps ! > -- > Fran?ois Beausoleil > http://blog.teksol.info/ > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060814/9c56251d/attachment.html From zedshaw at zedshaw.com Mon Aug 14 21:18:10 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 14 Aug 2006 18:18:10 -0700 Subject: [Mongrel] 0.3.13.4 w/ File Upload Progress? In-Reply-To: References: Message-ID: <1155604690.6158.14.camel@localhost.localdomain> On Mon, 2006-08-14 at 17:11 -0700, HH wrote: > So, do these new shiny 0.3.13.4 releases have the previously mentioned > upload progress stuff baked in and ready to use? No, not yet. I've gotta pull that together and come up with the packaging and docs. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zackchandler at gmail.com Tue Aug 15 18:55:50 2006 From: zackchandler at gmail.com (Zack Chandler) Date: Tue, 15 Aug 2006 15:55:50 -0700 Subject: [Mongrel] mongrel_cluster not starting on reboot Message-ID: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> Hi, I'm in the process of moving my blog over from lighttpd -> apache 2.2 + mongrel. Everything works fine as long as I don't reboot :) On reboot apache comes up but mongrel_cluster doesn't start up the pooches... I have added the mongrel_cluster call to my startup scripts like so: www:/etc/init.d# update-rc.d mongrel_cluster defaults Adding system startup for /etc/init.d/mongrel_cluster ... /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster www:/etc/init.d# Specs: mongrel 0.3.13.3 mongrel_cluster 0.2.0 on debian sarge (rimu). Any ideas? -- Zack Chandler http://depixelate.com From jason at joyent.com Tue Aug 15 19:23:35 2006 From: jason at joyent.com (Jason A. Hoffman) Date: Tue, 15 Aug 2006 16:23:35 -0700 Subject: [Mongrel] mongrel_cluster not starting on reboot In-Reply-To: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> References: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> Message-ID: On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: > Hi, > > I'm in the process of moving my blog over from lighttpd -> apache 2.2 > + mongrel. Everything works fine as long as I don't reboot :) > > On reboot apache comes up but mongrel_cluster doesn't start up the > pooches... > > I have added the mongrel_cluster call to my startup scripts like so: > > www:/etc/init.d# update-rc.d mongrel_cluster defaults > Adding system startup for /etc/init.d/mongrel_cluster ... > /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > www:/etc/init.d# > > Specs: > mongrel 0.3.13.3 > mongrel_cluster 0.2.0 on > debian sarge (rimu). > > Any ideas? What happens when you run that startup script on it's own? Often the problem with these (like cronjobs on reboot) is that you need full paths to everything. On reboot root will do things like use the sh shell to get things going and it doesn't know where to look. - J From zackchandler at gmail.com Tue Aug 15 20:26:09 2006 From: zackchandler at gmail.com (Zack Chandler) Date: Tue, 15 Aug 2006 17:26:09 -0700 Subject: [Mongrel] mongrel_cluster not starting on reboot In-Reply-To: References: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> Message-ID: <33841ac70608151726n292c51fpc38b35dec6f2ff6e@mail.gmail.com> On 8/15/06, Jason A. Hoffman wrote: > On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: > > Hi, > > > > I'm in the process of moving my blog over from lighttpd -> apache 2.2 > > + mongrel. Everything works fine as long as I don't reboot :) > > > > On reboot apache comes up but mongrel_cluster doesn't start up the > > pooches... > > > > I have added the mongrel_cluster call to my startup scripts like so: > > > > www:/etc/init.d# update-rc.d mongrel_cluster defaults > > Adding system startup for /etc/init.d/mongrel_cluster ... > > /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > > www:/etc/init.d# > > > > Specs: > > mongrel 0.3.13.3 > > mongrel_cluster 0.2.0 on > > debian sarge (rimu). > > > > Any ideas? > > What happens when you run that startup script on it's own? > > Often the problem with these (like cronjobs on reboot) is that you > need full paths to everything. On reboot root will do things like use > the sh shell to get things going and it doesn't know where to look. > > - J > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > Jason, >sudo /etc/init.d/mongrel_cluster start works fine from the command line. Any other ideas? -- Zack Chandler http://depixelate.com From jason at joyent.com Tue Aug 15 20:31:48 2006 From: jason at joyent.com (Jason A. Hoffman) Date: Tue, 15 Aug 2006 17:31:48 -0700 Subject: [Mongrel] mongrel_cluster not starting on reboot In-Reply-To: <33841ac70608151726n292c51fpc38b35dec6f2ff6e@mail.gmail.com> References: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> <33841ac70608151726n292c51fpc38b35dec6f2ff6e@mail.gmail.com> Message-ID: > Jason, > >> sudo /etc/init.d/mongrel_cluster start > works fine from the command line. > > Any other ideas? What are the permissions on the file (ls -aol /etc/init.d/ mongrel_cluster) and the contents? - J From jason at joyent.com Tue Aug 15 20:46:30 2006 From: jason at joyent.com (Jason A. Hoffman) Date: Tue, 15 Aug 2006 17:46:30 -0700 Subject: [Mongrel] mongrel_cluster not starting on reboot In-Reply-To: <33841ac70608151726n292c51fpc38b35dec6f2ff6e@mail.gmail.com> References: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> <33841ac70608151726n292c51fpc38b35dec6f2ff6e@mail.gmail.com> Message-ID: <9271BB62-DAF8-4EC5-9BF1-98BCC19E2D9C@joyent.com> On Aug 15, 2006, at 5:26 PM, Zack Chandler wrote: > On 8/15/06, Jason A. Hoffman wrote: >> On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: >>> Hi, >>> >>> I'm in the process of moving my blog over from lighttpd -> apache >>> 2.2 >>> + mongrel. Everything works fine as long as I don't reboot :) >>> >>> On reboot apache comes up but mongrel_cluster doesn't start up the >>> pooches... >>> >>> I have added the mongrel_cluster call to my startup scripts like >>> so: >>> >>> www:/etc/init.d# update-rc.d mongrel_cluster defaults >>> Adding system startup for /etc/init.d/mongrel_cluster ... >>> /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster >>> www:/etc/init.d# You know what, looking at this the rc6.d (from what I recall, I'm a solaris/BSD person) is that run level 6 is the System reboot runtime for debian, and when something is a "K" it disables the service and keeps it stopped. 2,3,4,5 are probably all multiuser and they're "S", that's why it works from the command line once it's up. Maybe rename all the K20mongrel_cluster ones to S20mongrel_cluster. - Jason From steven at lumos.us Tue Aug 15 21:09:25 2006 From: steven at lumos.us (Steven Lumos) Date: Tue, 15 Aug 2006 18:09:25 -0700 Subject: [Mongrel] Fwd: Error on Solaris References: <1155225266.5997.18.camel@localhost.localdomain> Message-ID: <86fyfx8p16.fsf@bitty.lumos.us> Zed Shaw writes: > On Thu, 2006-08-10 at 17:53 +1000, Carl Woodward wrote: >> Sorry guys, I'm an idiot. Its in C. > > Also, try installing the pre-release as I've (hopefully) fixed things > that cause the Sun C compiler to blow up (because they couldn't read a > spec if it was filled with porn). > > > gem install mongrel --source=http://mongrel.rubyforge.org/releases/ Sun C does not blow up, it emits some warnings. The warnings aren't errors, they are warnings. That's what the word "warning" at the beginning of those lines means. Empty declarations really are illegal in C99. They really are syntax errors. I wonder where you differ from Sun on the spec. I'd like to see your derivation of ';' from the grammar in Annex A.2.2. If anyone is inordinately bothered by the warnings, they can get rid of them by adding -xc99=%none to their compiler flags. Then an empty decl will be converted to 'int;' like C89 and GCC do. Better to fix the bug (as has already been done) however. Granted, using the word "error" in the body of a warning is confusing to people who miss the word "warning" immediately preceding it. That's why I used phrases like "Mostly just FYI", and "I get some warnings" in my bug report. The single remaining warning is also a warning. GCC will also emit this warning, but they hide this feature behind -Wunreachable-code. Try it (3.4.3 here) and you will learn why they hide it. It flags over 100 lines. I removed the crazy #line directives (1,106,24,110,26,114?) from the generated C file (0.3.13.3) and compiled to find that the warning is on line 297. That line really is unreachable. The warning really should be there. Having unreachable lines isn't exactly a crime for a parser generator. If anyone is inordinately bothered by the warning they can add -erroff=E_STATEMENT_NOT_REACHED to their compiler flags. Mongrel runs great when compiled with Sun C! So does Ruby. Maybe I should have noted in my bug report that I was using it with great success, would love to buy you a beverage, etc. GCC is periodically broken in horrible ways on SPARC. They even managed to break printf("%.2lf", x). I haven't caught up on whether they ever succeeded in correctly implementing the standard calling convention. Steve From tgw529 at gmail.com Tue Aug 15 22:34:45 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Tue, 15 Aug 2006 22:34:45 -0400 Subject: [Mongrel] mongrel lighttpd and ssl Message-ID: <1d6e22490608151934i16a7cc50u3c955c3ac66d80c@mail.gmail.com> I am wanting to one run instance of lighttpd, many many instances of mongrel. I also need ssl but only for one of my sites. I understand that Mongrel does not play with SSL so I am forced to use Lighttpd. I think that lighttpd only handles ssl or non-ssl on any given instance. Is there a way for me to accomplish my goal of one lighttpd with multiple mongrels and the occasional ssl connection? -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060815/d52dd420/attachment.html From zackchandler at gmail.com Tue Aug 15 23:22:58 2006 From: zackchandler at gmail.com (Zack Chandler) Date: Tue, 15 Aug 2006 20:22:58 -0700 Subject: [Mongrel] mongrel_cluster not starting on reboot In-Reply-To: <9271BB62-DAF8-4EC5-9BF1-98BCC19E2D9C@joyent.com> References: <33841ac70608151555g248359d8o3414dc2358b3ef42@mail.gmail.com> <33841ac70608151726n292c51fpc38b35dec6f2ff6e@mail.gmail.com> <9271BB62-DAF8-4EC5-9BF1-98BCC19E2D9C@joyent.com> Message-ID: <33841ac70608152022y29a07bces397a4287121e4c6d@mail.gmail.com> On 8/15/06, Jason A. Hoffman wrote: > On Aug 15, 2006, at 5:26 PM, Zack Chandler wrote: > > On 8/15/06, Jason A. Hoffman wrote: > >> On Aug 15, 2006, at 3:55 PM, Zack Chandler wrote: > >>> Hi, > >>> > >>> I'm in the process of moving my blog over from lighttpd -> apache > >>> 2.2 > >>> + mongrel. Everything works fine as long as I don't reboot :) > >>> > >>> On reboot apache comes up but mongrel_cluster doesn't start up the > >>> pooches... > >>> > >>> I have added the mongrel_cluster call to my startup scripts like > >>> so: > >>> > >>> www:/etc/init.d# update-rc.d mongrel_cluster defaults > >>> Adding system startup for /etc/init.d/mongrel_cluster ... > >>> /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster > >>> www:/etc/init.d# > > You know what, looking at this the rc6.d (from what I recall, I'm a > solaris/BSD person) is that run level 6 is the System reboot runtime > for debian, and when something is a "K" it disables the service and > keeps it stopped. > > 2,3,4,5 are probably all multiuser and they're "S", that's why it > works from the command line once it's up. Maybe rename all the > K20mongrel_cluster ones to S20mongrel_cluster. > > - Jason > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > Jason, I found out Rimuhosting supports console-over-ssh. That is sweet! Once I logged in I noticed this line: command not found: mongrel_cluster_ctl I guess /usr/local/bin is not in the boot PATH. I symlinked the following ln -s /usr/local/bin/mongrel_cluster_ctl mongrel_cluster_ctl ln -s /usr/local/bin/mongrel_rails mongrel_rails and it worked like a charm. Thanks! -- Zack Chandler http://depixelate.com From emho.verger at gmail.com Wed Aug 16 00:06:12 2006 From: emho.verger at gmail.com (Emho Verger) Date: Wed, 16 Aug 2006 12:06:12 +0800 Subject: [Mongrel] New subscriber, new question Message-ID: Hi all, I?m new to the list. I've working with mongrel for the last week and have some quetion about mongrel cluster: Is this (being executed from the application folder): # mongrel_rails start -d -p 3001 -e production # mongrel_rails start -d -p 3002 -e production # mongrel_rails start -d -p 3003 -e production the same as: # mongrel_rails cluster::configure -e production -p 3001 -N 3 -c /var/www/apps/testapp # mongrel_rails cluster::start Im not familiar with clusters, and since the load balance is being done by the Apache proxy balancer, I wonder what is the difference of executing that set of commands and the cluster::start. thanks to all, Emho From neil at aldur.co.uk Wed Aug 16 00:25:21 2006 From: neil at aldur.co.uk (Neil Wilson) Date: Wed, 16 Aug 2006 05:25:21 +0100 Subject: [Mongrel] Debian Apache 2.2 package available on experimental Message-ID: Finally! See http://people.debian.org/~terpstra/message/20060815.194742.e85b8143.en.html For all those Debianites wanting to try mod_proxy_balancer with Mongrel -- Neil Wilson (neil at aldur.co.uk) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/6fcee72b/attachment.html From scott at sigkill.org Wed Aug 16 01:06:27 2006 From: scott at sigkill.org (Scott Laird) Date: Tue, 15 Aug 2006 22:06:27 -0700 Subject: [Mongrel] Debian Apache 2.2 package available on experimental In-Reply-To: References: Message-ID: <14b7e5ef0608152206y6d4d00bcndc31772b1e146002@mail.gmail.com> Wow! I was starting to think they'd abandoned Apache. Scott On 8/15/06, Neil Wilson wrote: > Finally! > > See > http://people.debian.org/~terpstra/message/20060815.194742.e85b8143.en.html > > For all those Debianites wanting to try mod_proxy_balancer with Mongrel > > -- > Neil Wilson (neil at aldur.co.uk) > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From tgw529 at gmail.com Wed Aug 16 08:53:31 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Wed, 16 Aug 2006 08:53:31 -0400 Subject: [Mongrel] Mongrel Lighttpd and SSL Message-ID: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> I am wanting to one run instance of lighttpd, many many instances of mongrel. I also need ssl but only for one of my sites. I understand that Mongrel does not play with SSL so I am forced to use Lighttpd. I think that lighttpd only handles ssl or non-ssl on any given instance. Is there a way for me to accomplish my goal of one lighttpd with multiple mongrels and the occasional ssl connection? -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/76c00966/attachment-0001.html From jamesludlow at gmail.com Wed Aug 16 09:21:01 2006 From: jamesludlow at gmail.com (James Ludlow) Date: Wed, 16 Aug 2006 08:21:01 -0500 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> Message-ID: On 8/16/06, Timothy Wright wrote: > > I am wanting to one run instance of lighttpd, many many instances of > mongrel. I also need ssl but only for one of my sites. I understand that > Mongrel does not play with SSL so I am forced to use Lighttpd. I think that > lighttpd only handles ssl or non-ssl on any given instance. Is there a way > for me to accomplish my goal of one lighttpd with multiple mongrels and the > occasional ssl connection? I know that this doesn't answer your question at all, but have you considered pound -> mongrel_cluster -> tons-o-mongrels ? -- James From tgw529 at gmail.com Wed Aug 16 09:24:37 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Wed, 16 Aug 2006 09:24:37 -0400 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> Message-ID: <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> I am doing admin work for a guy and he really wants to keep things with just lighty and mongrel. I have thought about it and if this does not work I will suggest it. On 8/16/06, James Ludlow wrote: > > On 8/16/06, Timothy Wright wrote: > > > > I am wanting to one run instance of lighttpd, many many instances of > > mongrel. I also need ssl but only for one of my sites. I understand that > > Mongrel does not play with SSL so I am forced to use Lighttpd. I think > that > > lighttpd only handles ssl or non-ssl on any given instance. Is there a > way > > for me to accomplish my goal of one lighttpd with multiple mongrels and > the > > occasional ssl connection? > > I know that this doesn't answer your question at all, but have you > considered pound -> mongrel_cluster -> tons-o-mongrels ? > > > -- James > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/a094a379/attachment.html From zackchandler at gmail.com Wed Aug 16 10:57:59 2006 From: zackchandler at gmail.com (Zack Chandler) Date: Wed, 16 Aug 2006 07:57:59 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> Message-ID: <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> On 8/16/06, Timothy Wright wrote: > I am doing admin work for a guy and he really wants to keep things with just > lighty and mongrel. I have thought about it and if this does not work I will > suggest it. > > > > On 8/16/06, James Ludlow wrote: > > On 8/16/06, Timothy Wright wrote: > > > > > > I am wanting to one run instance of lighttpd, many many instances of > > > mongrel. I also need ssl but only for one of my sites. I understand that > > > Mongrel does not play with SSL so I am forced to use Lighttpd. I think > that > > > lighttpd only handles ssl or non-ssl on any given instance. Is there a > way > > > for me to accomplish my goal of one lighttpd with multiple mongrels and > the > > > occasional ssl connection? > > > > I know that this doesn't answer your question at all, but have you > > considered pound -> mongrel_cluster -> tons-o-mongrels ? > > > > > > -- James > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > -- > Grace and Peace, > Timothy G. Wright > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > If you just want it lighty + mongrel then you probably need to use mod_proxy_core. It's brand new so you'll be on the bleeding edge. http://blog.lighttpd.net/articles/2006/07/15/the-new-mod_proxy_core -- Zack Chandler http://depixelate.com From bryan at galisys.com Wed Aug 16 11:10:48 2006 From: bryan at galisys.com (Bryan Thompson) Date: Wed, 16 Aug 2006 10:10:48 -0500 Subject: [Mongrel] (no subject) Message-ID: <8619B931-FEA1-47B7-9B75-23CDC83A9FA5@galisys.com> Hi everybody, We are developing several applications on a single server and I'm looking for a way to use mongrel with each of them. Right now, http://testapp.com/ is being served on that machine through apache and mongrel. Here's what a part of my apache config looks like: BalancerMember http://127.0.0.1:8000 BalancerMember http://127.0.0.1:8001 BalancerMember http://127.0.0.1:8002 ServerName testapp.com ServerAlias testapp.com ProxyPass / balancer://testappcluster/ ProxyPassReverse / balancer://testappcluster/ It works great, but I want to move this app to http://testapp.com/foo and have another app at http://testapp.com/bar. Any tips? I was able to get my apps served separately with subdomains, however, I would prefer to keep them all on the same domain and just use /foo and /bar. Thanks! Bryan Thompson -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/813dac7d/attachment.html From ezmobius at gmail.com Wed Aug 16 11:30:11 2006 From: ezmobius at gmail.com (Ezra Zygmuntowicz) Date: Wed, 16 Aug 2006 08:30:11 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> Message-ID: <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> On Aug 16, 2006, at 7:57 AM, Zack Chandler wrote: > On 8/16/06, Timothy Wright wrote: >> I am doing admin work for a guy and he really wants to keep things >> with just >> lighty and mongrel. I have thought about it and if this does not >> work I will >> suggest it. >> >> >> >> On 8/16/06, James Ludlow wrote: >>> On 8/16/06, Timothy Wright wrote: >>>> >>>> I am wanting to one run instance of lighttpd, many many >>>> instances of >>>> mongrel. I also need ssl but only for one of my sites. I >>>> understand that >>>> Mongrel does not play with SSL so I am forced to use Lighttpd. I >>>> think >> that >>>> lighttpd only handles ssl or non-ssl on any given instance. Is >>>> there a >> way >>>> for me to accomplish my goal of one lighttpd with multiple >>>> mongrels and >> the >>>> occasional ssl connection? >>> >>> I know that this doesn't answer your question at all, but have you >>> considered pound -> mongrel_cluster -> tons-o-mongrels ? >>> >>> >>> -- James >>> _______________________________________________ >>> Mongrel-users mailing list >>> Mongrel-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/mongrel-users >>> >> >> >> >> -- >> Grace and Peace, >> Timothy G. Wright >> _______________________________________________ >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users >> >> > > If you just want it lighty + mongrel then you probably need to use > mod_proxy_core. It's brand new so you'll be on the bleeding edge. > > http://blog.lighttpd.net/articles/2006/07/15/the-new-mod_proxy_core > > -- > Zack Chandler > http://depixelate.com I have been playing with the pre releases of lighty with the new mod_proxy_core and mongrel_cluster and its working very nice. I haven't run into any issues with it yet and it solves most all of the issues that lighty's previous mod_proxy had. -Ezra From tgw529 at gmail.com Wed Aug 16 11:35:25 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Wed, 16 Aug 2006 11:35:25 -0400 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> Message-ID: <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> Ezra, Would you mind sharing your lighttpd.conf file with me? I would like to see how you have it set up. Thanks. Tim On 8/16/06, Ezra Zygmuntowicz wrote: > > > On Aug 16, 2006, at 7:57 AM, Zack Chandler wrote: > > > On 8/16/06, Timothy Wright wrote: > >> I am doing admin work for a guy and he really wants to keep things > >> with just > >> lighty and mongrel. I have thought about it and if this does not > >> work I will > >> suggest it. > >> > >> > >> > >> On 8/16/06, James Ludlow wrote: > >>> On 8/16/06, Timothy Wright wrote: > >>>> > >>>> I am wanting to one run instance of lighttpd, many many > >>>> instances of > >>>> mongrel. I also need ssl but only for one of my sites. I > >>>> understand that > >>>> Mongrel does not play with SSL so I am forced to use Lighttpd. I > >>>> think > >> that > >>>> lighttpd only handles ssl or non-ssl on any given instance. Is > >>>> there a > >> way > >>>> for me to accomplish my goal of one lighttpd with multiple > >>>> mongrels and > >> the > >>>> occasional ssl connection? > >>> > >>> I know that this doesn't answer your question at all, but have you > >>> considered pound -> mongrel_cluster -> tons-o-mongrels ? > >>> > >>> > >>> -- James > >>> _______________________________________________ > >>> Mongrel-users mailing list > >>> Mongrel-users at rubyforge.org > >>> http://rubyforge.org/mailman/listinfo/mongrel-users > >>> > >> > >> > >> > >> -- > >> Grace and Peace, > >> Timothy G. Wright > >> _______________________________________________ > >> Mongrel-users mailing list > >> Mongrel-users at rubyforge.org > >> http://rubyforge.org/mailman/listinfo/mongrel-users > >> > >> > > > > If you just want it lighty + mongrel then you probably need to use > > mod_proxy_core. It's brand new so you'll be on the bleeding edge. > > > > http://blog.lighttpd.net/articles/2006/07/15/the-new-mod_proxy_core > > > > -- > > Zack Chandler > > http://depixelate.com > > > I have been playing with the pre releases of lighty with the new > mod_proxy_core and mongrel_cluster and its working very nice. I > haven't run into any issues with it yet and it solves most all of the > issues that lighty's previous mod_proxy had. > > -Ezra > > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/45bda0ff/attachment-0001.html From jan.svitok at gmail.com Wed Aug 16 11:47:23 2006 From: jan.svitok at gmail.com (Jan Svitok) Date: Wed, 16 Aug 2006 17:47:23 +0200 Subject: [Mongrel] (no subject) In-Reply-To: <8619B931-FEA1-47B7-9B75-23CDC83A9FA5@galisys.com> References: <8619B931-FEA1-47B7-9B75-23CDC83A9FA5@galisys.com> Message-ID: <8d9b3d920608160847j2453a269s6611367e7a0a89d1@mail.gmail.com> On 8/16/06, Bryan Thompson wrote: > > Hi everybody, > > We are developing several applications on a single server and I'm looking > for a way to use mongrel with each of them. Right now, http://testapp.com/ > is being served on that machine through apache and mongrel. Here's what a > part of my apache config looks like: > > > > > BalancerMember http://127.0.0.1:8000 > BalancerMember http://127.0.0.1:8001 > BalancerMember http://127.0.0.1:8002 > > > > ServerName testapp.com > ServerAlias testapp.com > ProxyPass / balancer://testappcluster/ > ProxyPassReverse / balancer://testappcluster/ > > It works great, but I want to move this app to http://testapp.com/foo and > have another app at http://testapp.com/bar. > > Any tips? I was able to get my apps served separately with subdomains, > however, I would prefer to keep them all on the same domain and just use > /foo and /bar. > > Thanks! > > Bryan Thompson Hi, It's not possible to run more apps within one mongrel (for details see former thread "[Mongrel] Mongrel and multi apps"). For subdirectories, start your mongrel with --prefix /foo (or you can put it in the mongrel config file) From ezmobius at gmail.com Wed Aug 16 12:05:13 2006 From: ezmobius at gmail.com (Ezra Zygmuntowicz) Date: Wed, 16 Aug 2006 09:05:13 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> Message-ID: <02A7BCE2-A52E-4908-9AA7-AF9C60519A0D@gmail.com> On Aug 16, 2006, at 8:35 AM, Timothy Wright wrote: > Ezra, Would you mind sharing your lighttpd.conf file with me? I > would like to see how you have it set up. > Thanks. > Tim > > Sure. Its really simple. THis conf file sends all requests to mongrel though including static. I'm working on the rewrite rules for letting lighty serve the static content and I will post that once I'm finished. But this config works great and is dead simple. server.port = 80 server.bind = "0.0.0.0" server.document-root = "/var/www" # These modules need to be loaded for just plain old proxy. server.modules = ( "mod_rewrite", "mod_redirect", "mod_access", "mod_proxy_core") $HTTP["host"] = "\.foo\.com" { proxy-core.balancer = "round-robin" proxy-core.protocol = "http" proxy-core.backends = ( "127.0.0.1:3000", "127.0.0.1:3001", "127.0.0.1:3002") } I left out the mime-type assign list, I'm sure you have that somewhere. Cheers- -Ezra From bryan at galisys.com Wed Aug 16 12:08:25 2006 From: bryan at galisys.com (Bryan Thompson) Date: Wed, 16 Aug 2006 11:08:25 -0500 Subject: [Mongrel] (no subject) In-Reply-To: <8d9b3d920608160847j2453a269s6611367e7a0a89d1@mail.gmail.com> References: <8619B931-FEA1-47B7-9B75-23CDC83A9FA5@galisys.com> <8d9b3d920608160847j2453a269s6611367e7a0a89d1@mail.gmail.com> Message-ID: I can run more than one cluster at a time, so shouldn't I be able to have apache separate app /foo into traffic to balancer://foocluster and /foo to balancer://barcluster? I have gotten the following to work with apache2, however, it isn't exactly what I want: Root: http://testapp.com/ -- shows static html apache 'it worked' page. App one: http://foo.testapp.com/ -- uses balancer://foocluster App two: http://bar.testapp.com/ -- uses balancer://barcluster So, it should be possbible to use: Root: http://testapp.com/ -- show static html apache 'it worked' page. App one: http://testapp.com/foo -- use balancer://foocluster App two: http://testapp.com/bar -- use balancer://barcluster Bryan > It's not possible to run more apps within one mongrel (for details see > former thread "[Mongrel] Mongrel and multi apps"). > > For subdirectories, start your mongrel with --prefix /foo (or you can > put it in the mongrel config file) From tgw529 at gmail.com Wed Aug 16 12:09:30 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Wed, 16 Aug 2006 12:09:30 -0400 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <02A7BCE2-A52E-4908-9AA7-AF9C60519A0D@gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> <02A7BCE2-A52E-4908-9AA7-AF9C60519A0D@gmail.com> Message-ID: <1d6e22490608160909s394092desadc36b5edfa1833b@mail.gmail.com> Thanks a ton I will get working on that and see what happens. Tim On 8/16/06, Ezra Zygmuntowicz wrote: > > > On Aug 16, 2006, at 8:35 AM, Timothy Wright wrote: > > > Ezra, Would you mind sharing your lighttpd.conf file with me? I > > would like to see how you have it set up. > > Thanks. > > Tim > > > > > > Sure. Its really simple. THis conf file sends all requests to > mongrel though including static. I'm working on the rewrite rules for > letting lighty serve the static content and I will post that once I'm > finished. But this config works great and is dead simple. > > server.port = 80 > server.bind = "0.0.0.0" > server.document-root = "/var/www" > > # These modules need to be loaded for just plain old proxy. > server.modules = ( "mod_rewrite", "mod_redirect", "mod_access", > "mod_proxy_core") > > > $HTTP["host"] = "\.foo\.com" { > proxy-core.balancer = "round-robin" > proxy-core.protocol = "http" > proxy-core.backends = ( "127.0.0.1:3000", "127.0.0.1:3001", > "127.0.0.1:3002") > } > > > > I left out the mime-type assign list, I'm sure you have that > somewhere. > > Cheers- > -Ezra > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/da0aa976/attachment.html From jan.svitok at gmail.com Wed Aug 16 12:52:29 2006 From: jan.svitok at gmail.com (Jan Svitok) Date: Wed, 16 Aug 2006 18:52:29 +0200 Subject: [Mongrel] (no subject) In-Reply-To: References: <8619B931-FEA1-47B7-9B75-23CDC83A9FA5@galisys.com> <8d9b3d920608160847j2453a269s6611367e7a0a89d1@mail.gmail.com> Message-ID: <8d9b3d920608160952i70d4ddf4ob3f81d5f98718bb2@mail.gmail.com> On 8/16/06, Bryan Thompson wrote: > I can run more than one cluster at a time, so shouldn't I be able to > have apache separate app /foo into traffic to balancer://foocluster > and /foo to balancer://barcluster? > > I have gotten the following to work with apache2, however, it isn't > exactly what I want: > > Root: http://testapp.com/ -- shows static html apache 'it worked' page. > App one: http://foo.testapp.com/ -- uses balancer://foocluster > App two: http://bar.testapp.com/ -- uses balancer://barcluster > > So, it should be possbible to use: > > Root: http://testapp.com/ -- show static html apache 'it worked' page. > App one: http://testapp.com/foo -- use balancer://foocluster > App two: http://testapp.com/bar -- use balancer://barcluster right. From lists at chrisdo.org Wed Aug 16 16:51:40 2006 From: lists at chrisdo.org (Christof Dorner) Date: Wed, 16 Aug 2006 22:51:40 +0200 Subject: [Mongrel] New subscriber, new question In-Reply-To: References: Message-ID: <04D4EE3A-6D25-4670-B436-2078E2CF949E@chrisdo.org> Yes, I think this is the same, but it's easier to handle this with mongrel_cluster. Am 16.08.2006 um 06:06 schrieb Emho Verger: > Hi all, > > I?m new to the list. I've working with mongrel for the last week and > have some quetion about mongrel cluster: > > Is this (being executed from the application folder): > # mongrel_rails start -d -p 3001 -e production > # mongrel_rails start -d -p 3002 -e production > # mongrel_rails start -d -p 3003 -e production > > the same as: > > # mongrel_rails cluster::configure -e production -p 3001 -N 3 -c > /var/www/apps/testapp > # mongrel_rails cluster::start > > Im not familiar with clusters, and since the load balance is being > done by the Apache proxy balancer, I wonder what is the difference of > executing that set of commands and the cluster::start. > > thanks to all, > > Emho > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users From carl.lerche at verizon.net Wed Aug 16 18:09:48 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Wed, 16 Aug 2006 18:09:48 -0400 Subject: [Mongrel] Memory leak with the pre-release? Message-ID: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> Hello, I'm just wondering if there could possibly be a memory leak with the latest pre-release? When I run it, the processes keep increasing in memory size and easily pass 200MB and eventually crash due to a lack of memory. Is anybody else having this problem? Thanks, -carl PS, Zed, I sent you two emails directly to your address with logs and other stuff. Let me know if you didn't get them. From joenoon at gmail.com Wed Aug 16 18:00:28 2006 From: joenoon at gmail.com (Joe Noon) Date: Wed, 16 Aug 2006 15:00:28 -0700 Subject: [Mongrel] New subscriber, new question In-Reply-To: <04D4EE3A-6D25-4670-B436-2078E2CF949E@chrisdo.org> References: <04D4EE3A-6D25-4670-B436-2078E2CF949E@chrisdo.org> Message-ID: <619B8CDD-B14D-47F9-8342-A909BB79B180@gmail.com> On Aug 16, 2006, at 1:51 PM, Christof Dorner wrote: > Yes, I think this is the same, but it's easier to handle this with > mongrel_cluster. > > Am 16.08.2006 um 06:06 schrieb Emho Verger: > >> Hi all, >> >> I?m new to the list. I've working with mongrel for the last week and >> have some quetion about mongrel cluster: >> >> Is this (being executed from the application folder): >> # mongrel_rails start -d -p 3001 -e production >> # mongrel_rails start -d -p 3002 -e production >> # mongrel_rails start -d -p 3003 -e production >> >> the same as: >> >> # mongrel_rails cluster::configure -e production -p 3001 -N 3 -c >> /var/www/apps/testapp >> # mongrel_rails cluster::start I run each port separately, close to as you have described. I do it this way so I can run each as a daemontools service. I then have a separate daemontools service script that periodically checks each mongrel for functionality and terms/kills it if needed. Its a nice setup and allows me to not worry about anything being down for more than a minute or so. Probably overkill for general needs though. From ezmobius at gmail.com Wed Aug 16 19:06:52 2006 From: ezmobius at gmail.com (Ezra Zygmuntowicz) Date: Wed, 16 Aug 2006 16:06:52 -0700 Subject: [Mongrel] Memory leak with the pre-release? In-Reply-To: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> References: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> Message-ID: <8FC0D7C4-A565-420A-AD05-4C2CFA3A007D@gmail.com> On Aug 16, 2006, at 3:09 PM, Carl Lerche wrote: > Hello, > > I'm just wondering if there could possibly be a memory leak with the > latest pre-release? When I run it, the processes keep increasing in > memory size and easily pass 200MB and eventually crash due to a lack > of memory. Is anybody else having this problem? > > Thanks, > -carl > > PS, Zed, I sent you two emails directly to your address with logs and > other stuff. Let me know if you didn't get them. > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > Hey Carl- I have been seeing memory leaks with the new version of rails out right now as well as edge. I don't think its mongrel related. But to be sure, can you test your app with webrick and see if you still get the leak? My bet is you do still get it. I haven'tbeen able to pinpoint it but it is very annoying. My app runs fine in production biut in dev mode with mongrel or webrick it keeps eating memory until it fails to allocate with a fatal error and kills the processes. Do let me know if anyone figures out why the hell dev mode is leaking again. I though this was fixed a while ago but its happening again. I think it may have something to do with the new reloading code in dev mode but i haven't been able to pinpoint it. Cheers- -Ezra From zedshaw at zedshaw.com Wed Aug 16 19:09:21 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 16 Aug 2006 16:09:21 -0700 Subject: [Mongrel] Memory leak with the pre-release? In-Reply-To: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> References: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> Message-ID: <1155769761.6122.2.camel@localhost.localdomain> On Wed, 2006-08-16 at 18:09 -0400, Carl Lerche wrote: > Hello, > > I'm just wondering if there could possibly be a memory leak with the > latest pre-release? When I run it, the processes keep increasing in > memory size and easily pass 200MB and eventually crash due to a lack > of memory. Is anybody else having this problem? > > Thanks, > -carl > > PS, Zed, I sent you two emails directly to your address with logs and > other stuff. Let me know if you didn't get them. Yes I got them carl, I'm looking them over when I get the chance. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Wed Aug 16 19:53:26 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 16 Aug 2006 16:53:26 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed Message-ID: <1155772406.6122.11.camel@localhost.localdomain> 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 apply a few more patches from Jan Svitok. This will happen tonight. * The parser is fixed up to allow at least 10k QUERY_STRINGS. * There is a new debugging feature. You can now send any Mongrel process a USR1 signal and it'll start dumping the full text and parameters of any request it considers "bad". More on this below. * Tests were enhanced to test for the empty query string. * The mongrel_cluster work from Bradley Taylor is now part of Mongrel and will be maintained together so it'll get released at the same time as mongrel. * Timeout errors now include the reason mongrel timed out the thread in the exception description. That's all for now. Please grab this release with: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And verify your application still works. USR1 BAD CLIENT DEBUGGING As mentioned above, if you're seeing BAD CLIENT messages or parsing errors from Mongrel then you can send your mongrel process a USR1 signal (unix only) and Mongrel will start dumping the full text and parameters of what it received before aborting the client. When you hit a parsing error, really make sure the client is correct, then if you're positive it's right, send me the snippet from your log (not all of your log) and I'll look at it. When you're done, then simply hit the processes with another USR1 to toggle it off. The downside is I'm not sure of the security implications of this change, but there's only a performance hit if the client is bad so it's not that bad to leave it on. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From carl.lerche at verizon.net Wed Aug 16 20:10:18 2006 From: carl.lerche at verizon.net (Carl Lerche) Date: Wed, 16 Aug 2006 20:10:18 -0400 Subject: [Mongrel] Memory leak with the pre-release? In-Reply-To: <8FC0D7C4-A565-420A-AD05-4C2CFA3A007D@gmail.com> References: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> <8FC0D7C4-A565-420A-AD05-4C2CFA3A007D@gmail.com> Message-ID: On Aug 16, 2006, at 7:06 PM, Ezra Zygmuntowicz wrote: > > Hey Carl- > > I have been seeing memory leaks with the new version of rails out > right now as well as edge. I don't think its mongrel related. But to > be sure, can you test your app with webrick and see if you still get > the leak? My bet is you do still get it. I haven'tbeen able to > pinpoint it but it is very annoying. My app runs fine in production > biut in dev mode with mongrel or webrick it keeps eating memory until > it fails to allocate with a fatal error and kills the processes. > > Do let me know if anyone figures out why the hell dev mode is > leaking again. I though this was fixed a while ago but its happening > again. I think it may have something to do with the new reloading > code in dev mode but i haven't been able to pinpoint it. I'm running it in production mode right now and I get the memory leaks. I also haven't noticed a problem with memory leaks before I started using the pre-release. Maybe it's related to rails 1.1.6? I just don't know. -carl From zedshaw at zedshaw.com Wed Aug 16 20:14:34 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 16 Aug 2006 17:14:34 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed In-Reply-To: <1155772406.6122.11.camel@localhost.localdomain> References: <1155772406.6122.11.camel@localhost.localdomain> Message-ID: <1155773674.6122.13.camel@localhost.localdomain> On Wed, 2006-08-16 at 16:53 -0700, Zed Shaw wrote: > 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. Correction, NOW the win32 gems are up. I really gotta either get vmware or wine going for cross builds so I can automate this. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Wed Aug 16 20:16:12 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Wed, 16 Aug 2006 17:16:12 -0700 Subject: [Mongrel] Memory leak with the pre-release? In-Reply-To: References: <809B3B7D-4F2D-47E7-83F1-79A9C995EF90@verizon.net> <8FC0D7C4-A565-420A-AD05-4C2CFA3A007D@gmail.com> Message-ID: <1155773772.6122.15.camel@localhost.localdomain> On Wed, 2006-08-16 at 20:10 -0400, Carl Lerche wrote: > On Aug 16, 2006, at 7:06 PM, Ezra Zygmuntowicz wrote: > > > > Hey Carl- > > > > I have been seeing memory leaks with the new version of rails out > > right now as well as edge. I don't think its mongrel related. But to > > be sure, can you test your app with webrick and see if you still get > > the leak? My bet is you do still get it. I haven'tbeen able to > > pinpoint it but it is very annoying. My app runs fine in production > > biut in dev mode with mongrel or webrick it keeps eating memory until > > it fails to allocate with a fatal error and kills the processes. > > > > Do let me know if anyone figures out why the hell dev mode is > > leaking again. I though this was fixed a while ago but its happening > > again. I think it may have something to do with the new reloading > > code in dev mode but i haven't been able to pinpoint it. > > I'm running it in production mode right now and I get the memory > leaks. I also haven't noticed a problem with memory leaks before I > started using the pre-release. Maybe it's related to rails 1.1.6? I > just don't know. Just a quick thought, but why don't you put: GC.start Into an after filter on your application controller (the base controller you have for all your other ones). Simply forcing the GC this way might fix it magically. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From tgw529 at gmail.com Wed Aug 16 21:36:27 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Wed, 16 Aug 2006 21:36:27 -0400 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608160909s394092desadc36b5edfa1833b@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> <02A7BCE2-A52E-4908-9AA7-AF9C60519A0D@gmail.com> <1d6e22490608160909s394092desadc36b5edfa1833b@mail.gmail.com> Message-ID: <1d6e22490608161836v7ac82cfaiaa16e62fdac88376@mail.gmail.com> Ezra, In my effort to move to the bleeding edge, I am unable to install lighttpd. Here is the error that I get. Any thoughts? I am new at this so if it si an obvious one, I am sorry. Tim tim at rome:~/lighttpd-merge-1.4.x$ sudo ./autogen.sh ./autogen.sh: running `libtoolize --copy --force' You should update your `aclocal.m4' by running aclocal. ./autogen.sh: running `aclocal' ./autogen.sh: running `autoheader' ./autogen.sh: running `automake --add-missing --copy' src/Makefile.am:77: Libtool library used but `LIBTOOL' is undefined src/Makefile.am:77: src/Makefile.am:77: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' src/Makefile.am:77: to `configure.in' and run `aclocal' and `autoconf' again. tim at rome:~/lighttpd-merge-1.4.x$ ./configure -bash: ./configure: No such file or directory On 8/16/06, Timothy Wright wrote: > > Thanks a ton > I will get working on that and see what happens. > Tim > > On 8/16/06, Ezra Zygmuntowicz wrote: > > > > > On Aug 16, 2006, at 8:35 AM, Timothy Wright wrote: > > > > > Ezra, Would you mind sharing your lighttpd.conf file with me? I > > > would like to see how you have it set up. > > > Thanks. > > > Tim > > > > > > > > > > Sure. Its really simple. THis conf file sends all requests to > > mongrel though including static. I'm working on the rewrite rules for > > letting lighty serve the static content and I will post that once I'm > > finished. But this config works great and is dead simple. > > > > server.port = 80 > > server.bind = " 0.0.0.0" > > server.document-root = "/var/www" > > > > # These modules need to be loaded for just plain old proxy. > > server.modules = ( "mod_rewrite", "mod_redirect", "mod_access", > > "mod_proxy_core") > > > > > > $HTTP["host"] = "\.foo\.com" { > > proxy-core.balancer = "round-robin" > > proxy-core.protocol = "http" > > proxy-core.backends = ( " 127.0.0.1:3000", "127.0.0.1:3001", > > "127.0.0.1:3002") > > } > > > > > > > > I left out the mime-type assign list, I'm sure you have that > > somewhere. > > > > Cheers- > > -Ezra > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > -- > > Grace and Peace, > Timothy G. Wright > -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060816/3bfc8a26/attachment.html From emho.verger at gmail.com Wed Aug 16 23:21:05 2006 From: emho.verger at gmail.com (Emho Verger) Date: Thu, 17 Aug 2006 11:21:05 +0800 Subject: [Mongrel] New subscriber, new question In-Reply-To: References: Message-ID: Hi, I'd just like to share a weird problem and solution that was slowing down the browsing of the company website ... I had declared something like this (where www1.thewebname.com and www2.thewebname.com were accessible, and the IP was declared in the public DNS's): BalancerMember http://www1.thewebname.com:8000 BalancerMember http://www1.thewebname.com:8001 BalancerMember http://www1.thewebname.com:8002 BalancerMember http://www2.thewebname.com:8000 BalancerMember http://www2.thewebname.com:8001 BalancerMember http://www2.thewebname.com:8002 However, things were very very very slow ... Then, I decided to try out changing the names for the IP's themselves ... and things fly now ... fast as I was expecting with mongrel :) It took me sometime to realice of that and I still think it is kind of weird (it was unacceptable slow before) hope it helps someone, regards, Emho From ezmobius at gmail.com Wed Aug 16 23:31:12 2006 From: ezmobius at gmail.com (Ezra Zygmuntowicz) Date: Wed, 16 Aug 2006 20:31:12 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608161836v7ac82cfaiaa16e62fdac88376@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> <02A7BCE2-A52E-4908-9AA7-AF9C60519A0D@gmail.com> <1d6e22490608160909s394092desadc36b5edfa1833b@mail.gmail.com> <1d6e22490608161836v7ac82cfaiaa16e62fdac88376@mail.gmail.com> Message-ID: On Aug 16, 2006, at 6:36 PM, Timothy Wright wrote: > Ezra, > In my effort to move to the bleeding edge, I am unable to install > lighttpd. Here is the error that I get. Any thoughts? I am new at > this so if it si an obvious one, I am sorry. > Tim > > tim at rome:~/lighttpd-merge-1.4.x$ sudo ./autogen.sh > ./autogen.sh: running `libtoolize --copy --force' > You should update your `aclocal.m4' by running aclocal. > ./autogen.sh: running `aclocal' > ./autogen.sh: running `autoheader' > ./autogen.sh: running `automake --add-missing --copy' > src/Makefile.am:77: Libtool library used but `LIBTOOL' is undefined > src/Makefile.am:77: > src/Makefile.am:77: The usual way to define `LIBTOOL' is to add > `AC_PROG_LIBTOOL' > src/Makefile.am:77: to `configure.in' and run `aclocal' and > `autoconf' again. > tim at rome:~/lighttpd-merge-1.4.x$ ./configure > -bash: ./configure: No such file or directory > Did you check it out of svn? I had problems compiling from svn as well. So I used the prerelease here: http://www.lighttpd.net/download/lighttpd-1.4.12-20060724-0947.tar.gz then its just a ./configure && make && sudo make install -Ezra From mail at flydown.org Thu Aug 17 04:12:18 2006 From: mail at flydown.org (Michele) Date: Thu, 17 Aug 2006 10:12:18 +0200 Subject: [Mongrel] Apache Proxy Error + Mongrel dying Message-ID: 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 cluster and then it starts working well again, but after a while, I get the same error again. I know of the Apache bug and put this in my httpd.conf: #Fix for Apache bug 39499 SetEnv force-proxy-request-1.0 1 SetEnv proxy-nokeepalive 1 It seemed to work at first, but now I'm getting the errors again. Would using 0.3.14 fix this? is it ready for production? Thanks for your help, - Michele Finotto From mrueckert at suse.de Thu Aug 17 05:18:18 2006 From: mrueckert at suse.de (Marcus Rueckert) Date: Thu, 17 Aug 2006 11:18:18 +0200 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> Message-ID: <20060817091818.GN6949@suse.de> On 2006-08-16 08:30:11 -0700, Ezra Zygmuntowicz wrote: > I have been playing with the pre releases of lighty with the new > mod_proxy_core and mongrel_cluster and its working very nice. I > haven't run into any issues with it yet and it solves most all of the > issues that lighty's previous mod_proxy had. As a lighttpd developer i would like to mention: DONT USE THE CURRENT SVN STATE. especially not in production environments. If you do it anyway, dont expect support. Thanks in advance darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org From jgeiger at gmail.com Thu Aug 17 09:11:35 2006 From: jgeiger at gmail.com (Joey Geiger) Date: Thu, 17 Aug 2006 08:11:35 -0500 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed In-Reply-To: <1155773674.6122.13.camel@localhost.localdomain> References: <1155772406.6122.11.camel@localhost.localdomain> <1155773674.6122.13.camel@localhost.localdomain> Message-ID: <466af3440608170611h698caa2bwe784d830df7768bf@mail.gmail.com> Are you including the mongrel_cluster code in the mongrel gem, or just releasing them at the same time? On 8/16/06, Zed Shaw wrote: > On Wed, 2006-08-16 at 16:53 -0700, Zed Shaw wrote: > > 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. > > Correction, NOW the win32 gems are up. > > I really gotta either get vmware or wine going for cross builds so I can > automate this. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From spig at spig.net Thu Aug 17 09:54:18 2006 From: spig at spig.net (Steve Spigarelli) Date: Thu, 17 Aug 2006 07:54:18 -0600 Subject: [Mongrel] mongrel lighttpd and ssl In-Reply-To: <1d6e22490608151934i16a7cc50u3c955c3ac66d80c@mail.gmail.com> References: <1d6e22490608151934i16a7cc50u3c955c3ac66d80c@mail.gmail.com> Message-ID: <76d9cfcf0608170654g332bf281mfceda84638bc58a3@mail.gmail.com> I'm not sure where you got the impression that you can only do ssl or non-ssl. Just add an ssl section to lightty's conf for ssl. The SSL documentation at http://trac.lighttpd.net/trac/wiki/Docs%3ASSL only says that you have to use IP-based virtual hosting if you want to use one instance of lightty. With no mention of mongrel in this post, I feel bad even posting a response here. It's probably much more of a lightty question than a mongrel one. I hope my answers help in some way.. BTW, my configuration looks very similar to what is posted on the lightty ssl documentation I referenced above. I have my other hosts in the same file for standard port 80 traffic. Steve Spigarelli On 8/15/06, Timothy Wright wrote: > I am wanting to one run instance of lighttpd, many many instances of > mongrel. I also need ssl but only for one of my sites. I understand that > Mongrel does not play with SSL so I am forced to use Lighttpd. I think that > lighttpd only handles ssl or non-ssl on any given instance. Is there a way > for me to accomplish my goal of one lighttpd with multiple mongrels and the > occasional ssl connection? > > -- > Grace and Peace, > Timothy G. Wright > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From bradley at railsmachine.com Thu Aug 17 10:12:18 2006 From: bradley at railsmachine.com (Bradley Taylor) Date: Thu, 17 Aug 2006 10:12:18 -0400 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed In-Reply-To: <466af3440608170611h698caa2bwe784d830df7768bf@mail.gmail.com> References: <1155772406.6122.11.camel@localhost.localdomain> <1155773674.6122.13.camel@localhost.localdomain> <466af3440608170611h698caa2bwe784d830df7768bf@mail.gmail.com> Message-ID: Hi Joey: On Aug 17, 2006, at 9:11 AM, Joey Geiger wrote: > Are you including the mongrel_cluster code in the mongrel gem, or just > releasing them at the same time? > Its still a different gem, but now the source/gem lives in the Mongrel project (instead of railsmachine) and will get built with the Mongrel build. Thanks, Bradley ------ Rails Optimized Hosting ~ VPS and Dedicated Servers Simplified Deployment ~ Services and Software http://railsmachine.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/c469c556/attachment.html From zedshaw at zedshaw.com Thu Aug 17 15:00:06 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 17 Aug 2006 12:00:06 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <20060817091818.GN6949@suse.de> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <20060817091818.GN6949@suse.de> Message-ID: <1155841206.5778.1.camel@localhost.localdomain> On Thu, 2006-08-17 at 11:18 +0200, Marcus Rueckert wrote: > On 2006-08-16 08:30:11 -0700, Ezra Zygmuntowicz wrote: > > I have been playing with the pre releases of lighty with the new > > mod_proxy_core and mongrel_cluster and its working very nice. I > > haven't run into any issues with it yet and it solves most all of the > > issues that lighty's previous mod_proxy had. > > As a lighttpd developer i would like to mention: > > DONT USE THE CURRENT SVN STATE. Marcus, why is that? Is it in flux or did you guys find something? -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From snacktime at gmail.com Thu Aug 17 15:14:08 2006 From: snacktime at gmail.com (snacktime) Date: Thu, 17 Aug 2006 12:14:08 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> Message-ID: <1f060c4c0608171214n51519070o3016958cc5429377@mail.gmail.com> Here is an example of doing ssl and non ssl in the same instance. Note the use of $SERVER["socket"] and HTTP["host"]. You can use both of those for one virtual host like I did below. The host setting sets the options that are common to both ssl and non ssl, and the socket settings are port specific. Lots of different combinations are possible. var.base = "/tmp/" server.document-root = var.base server.modules = ( "mod_rewrite", "mod_accesslog", "mod_fastcgi", "mod_compress", "mod_expire" ) compress.filetype = ( "text/plain", "text/html", "text/css", "text/javascript" ) expire.url = ( "/favicon.ico" => "access 3 days", "/javascripts/" => "access 3 days" ) var.app1 = "/usr/local/www/seca/web/" $HTTP["host"] == "test.domain.com" { fastcgi.server = ( ".fcgi" => ( "localhost" => ( "min-procs" => 1, "max-procs" => 1, "socket" => var.app1 + "tmp/sockets/fcgi.socket", "bin-path" => var.app1 + "public/dispatch.fcgi", "bin-environment" => ( "RAILS_ENV" => "development" ) ) ) ) } $SERVER["socket"] == "72.25.136.58:80" { server.name = "test.domain.com" server.error-handler-404 = "/dispatch.fcgi" accesslog.filename = var.app1 + "log/lighttpd.access.log" compress.cache-dir = var.app1 + "tmp/cache" } $SERVER["socket"] == "72.25.136.58:443" { ssl.ca-file = var.app1 + "ssl/ca.pem" server.name = "test.domain.com" server.error-handler-404 = "/dispatch.fcgi" server.document-root = var.app1 + "public/" server.errorlog = var.app1 + "log/lighttpd.error.log" accesslog.filename = var.app1 + "log/lighttpd.access.log" compress.cache-dir = var.app1 + "tmp/cache" } var.app2 = "/usr/local/cart/jdonline/web/" $SERVER["socket"] == "72.25.136.54:80" { server.name = "domain2.com" server.error-handler-404 = "/dispatch.fcgi" server.document-root = var.app2 + "public/" server.errorlog = var.app2 + "log/lighttpd.error.log" accesslog.filename = var.app2 + "log/lighttpd.access.log" compress.cache-dir = var.app2 + "tmp/cache" fastcgi.server = ( ".fcgi" => ( "localhost" => ( "min-procs" => 1, "max-procs" => 1, "socket" => var.app2 + "tmp/sockets/fcgi.socket", "bin-path" => var.app2 + "public/dispatch.fcgi", "bin-environment" => ( "RAILS_ENV" => "development" ) ) ) ) } From snacktime at gmail.com Thu Aug 17 15:22:19 2006 From: snacktime at gmail.com (snacktime) Date: Thu, 17 Aug 2006 12:22:19 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1f060c4c0608171214n51519070o3016958cc5429377@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> <1f060c4c0608171214n51519070o3016958cc5429377@mail.gmail.com> Message-ID: <1f060c4c0608171222i2e7087es1646fffd2db474a5@mail.gmail.com> Not sure why they didn't paste correctly, but the following two lines were supposed to be in the section for port 443. ssl.engine = "enable" ssl.pemfile = var.app1 + "ssl/ra.pem" From mrueckert at suse.de Thu Aug 17 15:33:51 2006 From: mrueckert at suse.de (Marcus Rueckert) Date: Thu, 17 Aug 2006 21:33:51 +0200 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1155841206.5778.1.camel@localhost.localdomain> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <20060817091818.GN6949@suse.de> <1155841206.5778.1.camel@localhost.localdomain> Message-ID: <20060817193350.GY6949@suse.de> On 2006-08-17 12:00:06 -0700, Zed Shaw wrote: > > As a lighttpd developer i would like to mention: > > > > DONT USE THE CURRENT SVN STATE. > > Marcus, why is that? Is it in flux or did you guys find something? it is no in the shape for that so far. mod_proxy_core and some real core changes need some fine tuning first. just watch the lighty blog :) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org From kigsteronline at mac.com Thu Aug 17 21:34:24 2006 From: kigsteronline at mac.com (kigsteronline at mac.com) Date: Thu, 17 Aug 2006 18:34:24 -0700 Subject: [Mongrel] error starting mongrel: undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) In-Reply-To: <86fyfx8p16.fsf@bitty.lumos.us> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> Message-ID: <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> $ mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ mongrel.rb:666:in `register': undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:850:in `uri' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:1018:in `debug' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:1016:in `debug' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:108:in `cloaker_' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:832:in `listener' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:96:in `cloaker_' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel.rb:750:in `initialize' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:83:in `run' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/lib/mongrel/command.rb:199:in `run' from /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/ mongrel-0.3.13.3/bin/mongrel_rails:235 from /usr/local/ruby/bin/mongrel_rails:18 What am I missing? I installed it using "sudo gem install mongrel --include-dependencies" Thanks! Konstantin From kigsteronline at mac.com Thu Aug 17 21:45:16 2006 From: kigsteronline at mac.com (kigsteronline at mac.com) Date: Thu, 17 Aug 2006 18:45:16 -0700 Subject: [Mongrel] Avoiding sudo when starting/stopping mongrel_cluster In-Reply-To: <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> Message-ID: <3C76966F-984C-4337-95A7-DCCA29F787DA@mac.com> Hello! I apologize for newbie questions, but I am setting up capistrano and mongrel_cluster for the first time on Linux RS2. During "cap cold_deploy" from a development machine to a production box, I see the following: ** transaction: commit * executing task restart * executing task restart_mongrel_cluster * executing task stop_mongrel_cluster * executing "sudo mongrel_rails cluster::stop -C /data/apps/blurby/ current/config/mongrel_cluster.yml" I am running remote user as special application user, not root. Since mongrel cluster does not need privileged port, I would prefer if I didn't need to use SUDO to start/stop the cluster. Is there a way to remove "sudo" from the above command and run cluster as application user? Thanks for any input, Konstantin From nicksieger at gmail.com Thu Aug 17 21:49:48 2006 From: nicksieger at gmail.com (Nick Sieger) Date: Thu, 17 Aug 2006 20:49:48 -0500 Subject: [Mongrel] Avoiding sudo when starting/stopping mongrel_cluster In-Reply-To: <3C76966F-984C-4337-95A7-DCCA29F787DA@mac.com> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> <3C76966F-984C-4337-95A7-DCCA29F787DA@mac.com> Message-ID: On 8/17/06, kigsteronline at mac.com wrote: > > Is there a way to remove "sudo" from the above command and run > cluster as application user? "set :use_sudo, false" in your cap recipes file. Cheers, /Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/47f6dc00/attachment.html From nicksieger at gmail.com Thu Aug 17 21:52:17 2006 From: nicksieger at gmail.com (Nick Sieger) Date: Thu, 17 Aug 2006 20:52:17 -0500 Subject: [Mongrel] error starting mongrel: undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) In-Reply-To: <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> Message-ID: On 8/17/06, kigsteronline at mac.com wrote: > > $ mongrel_rails start > ** Starting Mongrel listening at 0.0.0.0:3000 > /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ > mongrel.rb:666:in `register': undefined method `resolve' for > nil:Mongrel::URIClassifier (NoMethodError) > > What am I missing? > > I installed it using "sudo gem install mongrel --include-dependencies" Go back and install again and watch for errors. The most likely culprit is that the /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel- 0.3.13.3/ext/http11/http11.so didn't get moved to /usr/local/ruby-1.8.4 /lib/ruby/gems/1.8/gems /mongrel-0.3.13.3/lib/http11.so during the installation process. HTH, /Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/61ce1e50/attachment.html From spig at spig.net Thu Aug 17 22:02:41 2006 From: spig at spig.net (Steve Spigarelli) Date: Thu, 17 Aug 2006 20:02:41 -0600 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. Message-ID: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> I'm not sure what's happening so I'll try and explain what I know. I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT (xx.xx.xx.xx): Invalid HTTP format, parsing fails." I'm running mongrel 0.3.13.4 from gem source, and running on a Macbook Pro. I am running rails in development mode and if I switch to running webrick, all requests come through as normal and return valid responses. So, the only problem I have is using a windows machine to access portions of the site. So far, I can consistently reproduce the problem in Firefox 1.0.7. I also can reproduce this in IE. One windows machine is a Parallels VM with a base, Win XP system. The other had Zonealarm firewall, but I have disabled that due to the thread that mentioned Mcafee security center. So, what are some ideas and is it possible that I am missing something critical that I have overlooked? Thanks for any help, Steve Spigarelli From _ at whats-your.name Thu Aug 17 22:08:36 2006 From: _ at whats-your.name (carmen) Date: Fri, 18 Aug 2006 02:08:36 +0000 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. In-Reply-To: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> References: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> Message-ID: <20060818020836.GE27460@replic.net> On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote: > I'm not sure what's happening so I'll try and explain what I know. > > > I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT > (xx.xx.xx.xx): Invalid HTTP format, parsing fails." it would be helpful to know what HTTP request is being sent. on windows this util can tell you: http://www.analogx.com/files/pmoni.exe or you could make mongrel spit the request to stderr.. From tgw529 at gmail.com Thu Aug 17 22:10:18 2006 From: tgw529 at gmail.com (Timothy Wright) Date: Thu, 17 Aug 2006 22:10:18 -0400 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1f060c4c0608171214n51519070o3016958cc5429377@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> <1f060c4c0608171214n51519070o3016958cc5429377@mail.gmail.com> Message-ID: <1d6e22490608171910wf64351ax99feda74ad8d0504@mail.gmail.com> Snacktime, I am sorry to say that I am bit confused by what you are saying. I am new at this so I am sorry. Please clairfy as much as possible. Is that what your file looks like or do I need to add in alot of my own info. The Var.appexpression is an include of some sort? Sorry for the lack of understanding on my part. Tim On 8/17/06, snacktime wrote: > > Here is an example of doing ssl and non ssl in the same instance. > Note the use of $SERVER["socket"] and HTTP["host"]. You can use both > of those for one virtual host like I did below. The host setting sets > the options that are common to both ssl and non ssl, and the socket > settings are port specific. Lots of different combinations are > possible. > > > > var.base = "/tmp/" > server.document-root = var.base > server.modules = ( "mod_rewrite", "mod_accesslog", > "mod_fastcgi", "mod_compress", "mod_expire" ) > > > compress.filetype = ( "text/plain", "text/html", "text/css", > "text/javascript" ) > > expire.url = ( "/favicon.ico" => "access 3 days", > "/javascripts/" => "access 3 days" ) > > var.app1 = "/usr/local/www/seca/web/" > $HTTP["host"] == "test.domain.com" { > fastcgi.server = ( ".fcgi" => ( "localhost" => ( > "min-procs" => 1, > "max-procs" => 1, > "socket" => var.app1 + "tmp/sockets/fcgi.socket", > "bin-path" => var.app1 + "public/dispatch.fcgi", > "bin-environment" => ( "RAILS_ENV" => "development" ) > ) ) ) > } > > $SERVER["socket"] == "72.25.136.58:80" { > server.name = "test.domain.com" > server.error-handler-404 = "/dispatch.fcgi" > accesslog.filename = var.app1 + "log/lighttpd.access.log" > compress.cache-dir = var.app1 + "tmp/cache" > } > $SERVER["socket"] == "72.25.136.58:443" { > ssl.ca-file = var.app1 + "ssl/ca.pem" > server.name = "test.domain.com" > server.error-handler-404 = "/dispatch.fcgi" > server.document-root = var.app1 + "public/" > server.errorlog = var.app1 + "log/lighttpd.error.log" > accesslog.filename = var.app1 + "log/lighttpd.access.log" > compress.cache-dir = var.app1 + "tmp/cache" > } > > var.app2 = "/usr/local/cart/jdonline/web/" > $SERVER["socket"] == "72.25.136.54:80" { > server.name = "domain2.com" > server.error-handler-404 = "/dispatch.fcgi" > server.document-root = var.app2 + "public/" > server.errorlog = var.app2 + "log/lighttpd.error.log" > accesslog.filename = var.app2 + "log/lighttpd.access.log" > compress.cache-dir = var.app2 + "tmp/cache" > fastcgi.server = ( ".fcgi" => ( "localhost" => ( > "min-procs" => 1, > "max-procs" => 1, > "socket" => var.app2 + "tmp/sockets/fcgi.socket", > "bin-path" => var.app2 + "public/dispatch.fcgi", > "bin-environment" => ( "RAILS_ENV" => "development" ) > ) ) ) > } > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -- Grace and Peace, Timothy G. Wright -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060817/f7a910af/attachment.html From spig at spig.net Thu Aug 17 22:16:48 2006 From: spig at spig.net (Steve Spigarelli) Date: Thu, 17 Aug 2006 20:16:48 -0600 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. In-Reply-To: <20060818020836.GE27460@replic.net> References: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> <20060818020836.GE27460@replic.net> Message-ID: <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> Is there an easy configuration to do that, or should I modify the gem source? On 8/17/06, carmen <_ at whats-your.name> wrote: > On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote: > > I'm not sure what's happening so I'll try and explain what I know. > > > > > > I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT > > (xx.xx.xx.xx): Invalid HTTP format, parsing fails." > > it would be helpful to know what HTTP request is being sent. on windows this util can tell you: http://www.analogx.com/files/pmoni.exe > > or you could make mongrel spit the request to stderr.. > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > From spig at spig.net Thu Aug 17 23:00:00 2006 From: spig at spig.net (Steve Spigarelli) Date: Thu, 17 Aug 2006 21:00:00 -0600 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. In-Reply-To: <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> References: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> <20060818020836.GE27460@replic.net> <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> Message-ID: <76d9cfcf0608172000k3b1da594ld6176bcefbd618dd@mail.gmail.com> Looks like the request is coming in as: delete /member/main/delete_favorite/12 HTTP/1.1\r\n ... standard headers and content.. Any ideas? I am sending "delete" as the method instead of get or post but I might be doing something that really isn't supported or that I just don't understand quite yet.. I think I'll see what other ways I can find to do this. I was trying to get a little more restian and I thought Rails converted the delete method to a "post" but I guess I'll have to work on this a little more. Thanks for the help, Steve On 8/17/06, Steve Spigarelli wrote: > Is there an easy configuration to do that, or should I modify the gem source? > > > On 8/17/06, carmen <_ at whats-your.name> wrote: > > On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote: > > > I'm not sure what's happening so I'll try and explain what I know. > > > > > > > > > I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT > > > (xx.xx.xx.xx): Invalid HTTP format, parsing fails." > > > > it would be helpful to know what HTTP request is being sent. on windows this util can tell you: http://www.analogx.com/files/pmoni.exe > > > > or you could make mongrel spit the request to stderr.. > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > From spig at spig.net Thu Aug 17 23:32:00 2006 From: spig at spig.net (Steve Spigarelli) Date: Thu, 17 Aug 2006 21:32:00 -0600 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. In-Reply-To: <76d9cfcf0608172000k3b1da594ld6176bcefbd618dd@mail.gmail.com> References: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> <20060818020836.GE27460@replic.net> <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> <76d9cfcf0608172000k3b1da594ld6176bcefbd618dd@mail.gmail.com> Message-ID: <76d9cfcf0608172032w24c9645dk9d29afce1edf06e2@mail.gmail.com> >From windows boxes I was having problems with link_to and the :method => 'delete'. In my controller I was then checking for request.delete?. I have changed this back to :method => 'post' and request.post? and things are working again across all platforms. I'm not sure where the problem is but I assume that mongrel is not aware of how to handle the 'delete' method as webrick was able to handle the request. Am I missing something? Am I out of date with something that I need to get the latest source code on? Steve On 8/17/06, Steve Spigarelli wrote: > Looks like the request is coming in as: > > delete /member/main/delete_favorite/12 HTTP/1.1\r\n ... standard > headers and content.. > > > Any ideas? I am sending "delete" as the method instead of get or post > but I might be doing something that really isn't supported or that I > just don't understand quite yet.. I think I'll see what other ways I > can find to do this. I was trying to get a little more restian and I > thought Rails converted the delete method to a "post" but I guess I'll > have to work on this a little more. > > Thanks for the help, > > Steve > > On 8/17/06, Steve Spigarelli wrote: > > Is there an easy configuration to do that, or should I modify the gem source? > > > > > > On 8/17/06, carmen <_ at whats-your.name> wrote: > > > On Thu Aug 17, 2006 at 08:02:41PM -0600, Steve Spigarelli wrote: > > > > I'm not sure what's happening so I'll try and explain what I know. > > > > > > > > > > > > I am getting the error "Thu Aug 17 20:01:57 MDT 2006: BAD CLIENT > > > > (xx.xx.xx.xx): Invalid HTTP format, parsing fails." > > > > > > it would be helpful to know what HTTP request is being sent. on windows this util can tell you: http://www.analogx.com/files/pmoni.exe > > > > > > or you could make mongrel spit the request to stderr.. > > > _______________________________________________ > > > Mongrel-users mailing list > > > Mongrel-users at rubyforge.org > > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > From _ at whats-your.name Thu Aug 17 23:39:04 2006 From: _ at whats-your.name (carmen) Date: Fri, 18 Aug 2006 03:39:04 +0000 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. In-Reply-To: <76d9cfcf0608172032w24c9645dk9d29afce1edf06e2@mail.gmail.com> References: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> <20060818020836.GE27460@replic.net> <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> <76d9cfcf0608172000k3b1da594ld6176bcefbd618dd@mail.gmail.com> <76d9cfcf0608172032w24c9645dk9d29afce1edf06e2@mail.gmail.com> Message-ID: <20060818033904.GF27460@replic.net> > Am I missing something? Am I out of date with something that I need > to get the latest source code on? probably not. Mongrel is significantly more RFC congruous than webrick. you might want to check out ActiveResource in rails 1.2 to see how methods are mapped to GET, PUT, DELETE, and POST.. From zedshaw at zedshaw.com Fri Aug 18 00:03:47 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Thu, 17 Aug 2006 21:03:47 -0700 Subject: [Mongrel] BAD CLIENT, Invalid HTTP Format - Firefox, IE, etc.. In-Reply-To: <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> References: <76d9cfcf0608171902i23d5d73bocece49ce988b4e9@mail.gmail.com> <20060818020836.GE27460@replic.net> <76d9cfcf0608171916i2e2f40c6rda2dc6686b285fe9@mail.gmail.com> Message-ID: <1155873827.6112.2.camel@localhost.localdomain> On Thu, 2006-08-17 at 20:16 -0600, Steve Spigarelli wrote: > Is there an easy configuration to do that, or should I modify the gem source? > Hey Steve, What you can do is run your app under mongrel, then hit all your mongrel processes with the USR1 signal: killall -USR1 mongrel_rails After you do this, your log/mongrel.log should say it's gonna start logging clients, and then when you get a BAD CLIENT it'll spit out the full data it received and the params it had before it booted the client. Run that and then shoot me the logs (off list!). -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From snacktime at gmail.com Fri Aug 18 01:11:32 2006 From: snacktime at gmail.com (snacktime) Date: Thu, 17 Aug 2006 22:11:32 -0700 Subject: [Mongrel] Mongrel Lighttpd and SSL In-Reply-To: <1d6e22490608171910wf64351ax99feda74ad8d0504@mail.gmail.com> References: <1d6e22490608160553j3be0b017p23493d4bff33f718@mail.gmail.com> <1d6e22490608160624q7f74865et40286a4eaaf30375@mail.gmail.com> <33841ac70608160757n63fa4991n510d7a6a9efaeb1c@mail.gmail.com> <748A8EBD-2652-45CE-9C43-2D0BDB164FBB@brainspl.at> <1d6e22490608160835g2c90ef13ne3771b536944f4d6@mail.gmail.com> <1f060c4c0608171214n51519070o3016958cc5429377@mail.gmail.com> <1d6e22490608171910wf64351ax99feda74ad8d0504@mail.gmail.com> Message-ID: <1f060c4c0608172211w2767062dh3c13e2441decb319@mail.gmail.com> On 8/17/06, Timothy Wright wrote: > Snacktime, > I am sorry to say that I am bit confused by what you are saying. I am new at > this so I am sorry. Please clairfy as much as possible. Is that what your > file looks like or do I need to add in alot of my own info. The Var.app > expression is an include of some sort? Sorry for the lack of understanding > on my part. The Var.app is just a variable to store base paths in, etc.. $HTTP["host"] matches hostnames. $SERVER["socket"] matches an ip address/port combination. I set things that are common to the whole hostname using the host, and use the socket to set the per port configs. One thing that might have thrown you is that for the host config I used the hostname, while the socket sections used the ip address. The config I posted is complete, there are no includes. Chris From maillist at steelskies.com Fri Aug 18 05:50:18 2006 From: maillist at steelskies.com (Jonathan del Strother) Date: Fri, 18 Aug 2006 10:50:18 +0100 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed In-Reply-To: <1155772406.6122.11.camel@localhost.localdomain> References: <1155772406.6122.11.camel@localhost.localdomain> Message-ID: I'm quite often losing mysql connections during requests, when using mongrel. Doesn't happen with lighty. This is on OS X 10.4.6, mysql 4.1.16, and a recent rails. Is there any other useful information I can supply? On 17 Aug 2006, at 00:53, Zed Shaw wrote: > 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 apply a few > more patches from Jan Svitok. This will happen tonight. > * The parser is fixed up to allow at least 10k QUERY_STRINGS. > * There is a new debugging feature. You can now send any Mongrel > process a USR1 signal and it'll start dumping the full text and > parameters of any request it considers "bad". More on this below. > * Tests were enhanced to test for the empty query string. > * The mongrel_cluster work from Bradley Taylor is now part of Mongrel > and will be maintained together so it'll get released at the same time > as mongrel. > * Timeout errors now include the reason mongrel timed out the > thread in > the exception description. > > That's all for now. Please grab this release with: > > gem install mongrel --source=http://mongrel.rubyforge.org/releases/ > > And verify your application still works. > > > USR1 BAD CLIENT DEBUGGING > > As mentioned above, if you're seeing BAD CLIENT messages or parsing > errors from Mongrel then you can send your mongrel process a USR1 > signal > (unix only) and Mongrel will start dumping the full text and > parameters > of what it received before aborting the client. > > When you hit a parsing error, really make sure the client is correct, > then if you're positive it's right, send me the snippet from your log > (not all of your log) and I'll look at it. > > When you're done, then simply hit the processes with another USR1 to > toggle it off. > > The downside is I'm not sure of the security implications of this > change, but there's only a performance hit if the client is bad so > it's > not that bad to leave it on. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2114 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/7d40d830/attachment.bin From mail at flydown.org Fri Aug 18 08:59:13 2006 From: mail at flydown.org (Michele) Date: Fri, 18 Aug 2006 14:59:13 +0200 Subject: [Mongrel] Apache Proxy Error + Mongrel dying In-Reply-To: References: Message-ID: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> If I run Mongrel 0.3.13.4 in debug mode, I get this error before the process dies: "Illegal instruction: 4 (core dumped)". What could it be? Is there a way which instruction is causing the error? Thanks, - Michele On Aug 17, 2006, at 10:12 , Michele wrote: > 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 cluster and then it starts working well > again, but after a while, I get the same error again. > > I know of the Apache bug and put this in my httpd.conf: > #Fix for Apache bug 39499 > SetEnv force-proxy-request-1.0 1 > SetEnv proxy-nokeepalive 1 > > It seemed to work at first, but now I'm getting the errors again. > > Would using 0.3.14 fix this? is it ready for production? > > Thanks for your help, > - Michele Finotto > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From bassnode at gmail.com Fri Aug 18 10:09:07 2006 From: bassnode at gmail.com (Ed Hickey) Date: Fri, 18 Aug 2006 09:09:07 -0500 Subject: [Mongrel] error starting mongrel: undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) In-Reply-To: References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> Message-ID: <733f56120608180709t4404a932r6eb0ae4898f191f2@mail.gmail.com> i believe i had this problem and it was because i didn't install gcc. make sure you have the gcc package installed, uninstall mogrel, install mongrel and try again. ed On 8/17/06, Nick Sieger wrote: > > On 8/17/06, kigsteronline at mac.com wrote: > > > $ mongrel_rails start > ** Starting Mongrel listening at 0.0.0.0:3000 > /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ > mongrel.rb:666:in `register': undefined method `resolve' for > nil:Mongrel::URIClassifier (NoMethodError) > > What am I missing? > > I installed it using "sudo gem install mongrel --include-dependencies" > > Go back and install again and watch for errors. The most likely culprit > is that the /usr/local/ruby- 1.8.4/lib/ruby/gems/1.8/gems/mongrel- > 0.3.13.3/ext/http11/http11.so didn't get moved to /usr/local/ruby-1.8.4 > /lib/ruby/gems/1.8/gems > /mongrel- 0.3.13.3/lib/http11.so during the installation process. > > HTH, > /Nick > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/5f8b25da/attachment.html From gusxedge at gmail.com Fri Aug 18 10:12:04 2006 From: gusxedge at gmail.com (Guillaume Carbonneau) Date: Fri, 18 Aug 2006 10:12:04 -0400 Subject: [Mongrel] Mongrel setting with Mysql error Message-ID: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> 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 searching google, ruby and rails mailing list but didn't find anything. I'd appreciate if you guys could point me to the right direction. Like what steps I have to do to make mysql interact with Mongrel/Ruby. Thanks Guillaume Carbonneau -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/90d6401e/attachment.html From mongrel at philip.pjkh.com Fri Aug 18 11:43:30 2006 From: mongrel at philip.pjkh.com (Philip Hallstrom) Date: Fri, 18 Aug 2006 10:43:30 -0500 (CDT) Subject: [Mongrel] Mongrel setting with Mysql error In-Reply-To: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> References: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> Message-ID: <20060818104230.O1536@bravo.pjkh.com> > 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 > searching google, ruby and rails mailing list but didn't find anything. > I'd appreciate if you guys could point me to the right direction. Like what > steps I have to do to make mysql interact with Mongrel/Ruby. Can you use mysql from straight ruby? If you do "gem list" do you see the following: mysql (2.7) MySQL/Ruby provides the same functions for Ruby programs that the MySQL C API provides for C programs. If not, you should... I could be wrong, but I think that message means you don't have the ruby/mysql part hooked up. "gem install mysql" should get it for you From me at seebq.com Fri Aug 18 13:43:31 2006 From: me at seebq.com (Charles Brian Quinn) Date: Fri, 18 Aug 2006 13:43:31 -0400 Subject: [Mongrel] New automated Capistrano setup for Apache2.1+ and mongrel_cluster Message-ID: <3a2de0cd0608181043j4f5d6701x52af72309a48c033@mail.gmail.com> 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 part: (0..mongrel_servers-1).each { |server| apache2_rails_conf += " BalancerMember http://127.0.0.1:#{mongrel_start_port + server}\n" } It's on our newest Slingshot Hosting image, but you can download it here: http://www.slingshothosting.com/files/apache2_2_mongrel_deploy.rb Deployment just got a whole lot easier. And, is about to get even easier: http://cleanair.highgroove.com/articles/2006/08/18/heartbeat-sneak-preview -- Charles Brian Quinn self-promotion: www.seebq.com highgroove studios: www.highgroove.com slingshot hosting: www.slingshothosting.com -- Charles Brian Quinn self-promotion: www.seebq.com highgroove studios: www.highgroove.com slingshot hosting: www.slingshothosting.com From snacktime at gmail.com Fri Aug 18 13:55:01 2006 From: snacktime at gmail.com (snacktime) Date: Fri, 18 Aug 2006 10:55:01 -0700 Subject: [Mongrel] error starting mongrel: undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) In-Reply-To: <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> Message-ID: <1f060c4c0608181055x26c51cc5k95a046007995a46b@mail.gmail.com> There is something wrong with that version of mongrel. I had this exact same issue. Downgrade it work fine, upgrade to pre release it work fine. stay at 0.3.13.3 I get that error. clean out everything try again same result. That was on freebsd 6.1. Tried it on two different 6.1 servers same result. From kigsteronline at mac.com Fri Aug 18 13:54:28 2006 From: kigsteronline at mac.com (kigsteronline at mac.com) Date: Fri, 18 Aug 2006 10:54:28 -0700 Subject: [Mongrel] error starting mongrel: undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) In-Reply-To: <733f56120608180709t4404a932r6eb0ae4898f191f2@mail.gmail.com> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> <733f56120608180709t4404a932r6eb0ae4898f191f2@mail.gmail.com> Message-ID: <4308BB46-89CB-427E-A0D1-987BC94F4707@mac.com> This was some weird permissions problem... I've rebuilt everything from scratch and made sure that /usr/local/ruby was readable by all users, and now it's all working. Thanks for the help! K On Aug 18, 2006, at 7:09 AM, Ed Hickey wrote: > i believe i had this problem and it was because i didn't install > gcc. make sure you have the gcc package installed, uninstall > mogrel, install mongrel and try again. > > ed > > On 8/17/06, Nick Sieger wrote: > On 8/17/06, kigsteronline at mac.com < kigsteronline at mac.com> wrote: > $ mongrel_rails start > ** Starting Mongrel listening at 0.0.0.0:3000 > /usr/local/ruby-1.8.4/lib/ruby/gems/1.8/gems/mongrel-0.3.13.3/lib/ > mongrel.rb:666:in `register': undefined method `resolve' for > nil:Mongrel::URIClassifier (NoMethodError) > > What am I missing? > > I installed it using "sudo gem install mongrel --include-dependencies" > > Go back and install again and watch for errors. T he most likely > culprit is that the /usr/local/ruby- 1.8.4/lib/ruby/gems/1.8/gems/ > mongrel-0.3.13.3/ext/http11/http11.so didn't get moved to /usr/ > local/ruby- 1.8.4/lib/ruby/gems/1.8/gems > /mongrel- 0.3.13.3/lib/http11.so during the installation process. > > HTH, > /Nick > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/cf412578/attachment.html From tdreyno at gmail.com Fri Aug 18 14:42:45 2006 From: tdreyno at gmail.com (Thomas Reynolds) Date: Fri, 18 Aug 2006 11:42:45 -0700 Subject: [Mongrel] New automated Capistrano setup for Apache2.1+ and mongrel_cluster In-Reply-To: <3a2de0cd0608181043j4f5d6701x52af72309a48c033@mail.gmail.com> References: <3a2de0cd0608181043j4f5d6701x52af72309a48c033@mail.gmail.com> Message-ID: <1ccc71a80608181142h292748abj8bdef821e0a8b37c@mail.gmail.com> Oh my fucking god, you have made my life so much better. Tweaking .conf files was starting to drive me mad. -Thomas Reynolds On 8/18/06, Charles Brian Quinn wrote: > > 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 part: > > (0..mongrel_servers-1).each { |server| > apache2_rails_conf += " BalancerMember > http://127.0.0.1:#{mongrel_start_port + server}\n" > } > > It's on our newest Slingshot Hosting image, but you can download it here: > > http://www.slingshothosting.com/files/apache2_2_mongrel_deploy.rb > > Deployment just got a whole lot easier. > > And, is about to get even easier: > > http://cleanair.highgroove.com/articles/2006/08/18/heartbeat-sneak-preview > > -- > Charles Brian Quinn > self-promotion: www.seebq.com > highgroove studios: www.highgroove.com > slingshot hosting: www.slingshothosting.com > > > -- > Charles Brian Quinn > self-promotion: www.seebq.com > highgroove studios: www.highgroove.com > slingshot hosting: www.slingshothosting.com > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/100b1ef5/attachment.html From jacob at jacobatzen.dk Fri Aug 18 15:01:29 2006 From: jacob at jacobatzen.dk (Jacob Atzen) Date: Fri, 18 Aug 2006 21:01:29 +0200 Subject: [Mongrel] Apache Proxy Error + Mongrel dying In-Reply-To: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> References: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> Message-ID: <20060818190128.GA13275@nezbo.dhcp.aub.dk> On Fri, Aug 18, 2006 at 02:59:13PM +0200, Michele wrote: > If I run Mongrel 0.3.13.4 in debug mode, I get this error before the > process dies: "Illegal instruction: 4 (core dumped)". > > What could it be? Is there a way which instruction is causing the error? > > Thanks, > - Michele > > On Aug 17, 2006, at 10:12 , Michele wrote: > > > 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 cluster and then it starts working well > > again, but after a while, I get the same error again. > > > > I know of the Apache bug and put this in my httpd.conf: > > #Fix for Apache bug 39499 > > SetEnv force-proxy-request-1.0 1 > > SetEnv proxy-nokeepalive 1 > > > > It seemed to work at first, but now I'm getting the errors again. > > > > Would using 0.3.14 fix this? is it ready for production? Hello list, I'm seeing something like the same problem. Mongrels who suddenly stop responding. I'm running an Apache mod_proxy with Mongrel backends setup. And from time to time I'll get the following in the Apache error log file: [Fri Aug 18 20:28:53 2006] [error] [client xxx.xxx.xxx.xxx] proxy: error reading status line from remote server 127.0.0.1 Fri Aug 18 20:28:53 2006] [error] [client xxx.xxx.xxx.xxx] proxy: Error reading from remote server returned by ... Additionally I'm experiencing Mongrels locking up hard. The only thing to do to them is a kill -9. I'm also seeing Mongrels disappearing without a trace in mongrel.log. The problem seems to increase when the load is high, and I have a feeling that increasing the number of mongrels somewhat increases the time interval between lockups. Right now I'm running 20 mongrels and haven't seen the problem for a while. It should be noted that the application is not severely loaded. The Rails production log seems to indicate something like 10 reqs/sec and the requests processing time goes from 1 r/s and up to ~1000 r/s with the majority running way above 10 r/s. I haven't seen any core dumps even with debug turned on for Mongrel. I'm on FreeBSD 6.1, Apache 2.2.3, Mongrel 0.3.13.4 (as I had another issue and was advised to upgrade by Zed Shaw) and Rails 1.1.6 and deploying with Mongrel_cluster and Capistrano. Unfortunately I will not be able to provide further info for the next 2 weeks, but I do hope somebody will be able to figure out what is going on with what little info is given. -- Thanks, - Jacob Atzen From zedshaw at zedshaw.com Fri Aug 18 15:50:40 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 12:50:40 -0700 Subject: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed In-Reply-To: References: <1155772406.6122.11.camel@localhost.localdomain> Message-ID: <1155930640.6117.10.camel@localhost.localdomain> On Fri, 2006-08-18 at 10:50 +0100, Jonathan del Strother wrote: > I'm quite often losing mysql connections during requests, when using > mongrel. Doesn't happen with lighty. > This is on OS X 10.4.6, mysql 4.1.16, and a recent rails. Is there > any other useful information I can supply? Do you mean FastCGI and lighty? Because "lighty" doesn't run rails. If so, then I'll need more information than this. For example: 1) When does this happen? 2) Where's your mysql database? 3) Do you have enough ram? 4) Have you done a packet trace to see what might cause it? These are very informative, although it sucks to have to resort to this. 5) What's the exception you get? 6) Are you opening a bunch of files? 7) Do you have lots of cache() statements in your templates? Those open lots of files. 8) Are you using the default rails pure ruby driver or the compiled driver? If you can get me more info I might be able to figure it out. Otherwise most folks seem to have upgraded to the latest driver and not had this problem. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 18 15:53:08 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 12:53:08 -0700 Subject: [Mongrel] Apache Proxy Error + Mongrel dying In-Reply-To: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> References: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> Message-ID: <1155930788.6117.14.camel@localhost.localdomain> On Fri, 2006-08-18 at 14:59 +0200, Michele wrote: > If I run Mongrel 0.3.13.4 in debug mode, I get this error before the > process dies: "Illegal instruction: 4 (core dumped)". > > What could it be? Is there a way which instruction is causing the error? What operating system and version? How'd you build your ruby? After how long does this happen? Does it tell you line number of where it happens? Is the line number consistent? Try running it under gdb, then when it dies type: backtrace and send me the output. That or run the program under strace and give me the last bit of the output before it died. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 18 15:54:30 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 12:54:30 -0700 Subject: [Mongrel] error starting mongrel: undefined method `resolve' for nil:Mongrel::URIClassifier (NoMethodError) In-Reply-To: <733f56120608180709t4404a932r6eb0ae4898f191f2@mail.gmail.com> References: <1155225266.5997.18.camel@localhost.localdomain> <86fyfx8p16.fsf@bitty.lumos.us> <7141A7E5-03E8-4977-99BD-5C4A3D271EB0@mac.com> <733f56120608180709t4404a932r6eb0ae4898f191f2@mail.gmail.com> Message-ID: <1155930870.6117.15.camel@localhost.localdomain> On Fri, 2006-08-18 at 09:09 -0500, Ed Hickey wrote: > i believe i had this problem and it was because i didn't install gcc. > make sure you have the gcc package installed, uninstall mogrel, > install mongrel and try again. Yep, the ever present "gems installs even if nothing builds" problem. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 18 15:56:20 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 12:56:20 -0700 Subject: [Mongrel] Mongrel setting with Mysql error In-Reply-To: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> References: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> Message-ID: <1155930980.6117.18.camel@localhost.localdomain> On Fri, 2006-08-18 at 10:12 -0400, Guillaume Carbonneau wrote: > 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 > searching google, ruby and rails mailing list but didn't find > anything. > I'd appreciate if you guys could point me to the right direction. Like > what steps I have to do to make mysql interact with Mongrel/Ruby. > Haven't seen this from people who use win32, so I'm thinking your setup is wrong somehow. Have you tried installing the win32 mysql gem? gem install mysql I believe that'll intall it but you have to pick win32. If you've already done this then maybe remove it and see if you get the error. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 18 15:59:48 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 12:59:48 -0700 Subject: [Mongrel] New automated Capistrano setup for Apache2.1+ and mongrel_cluster In-Reply-To: <3a2de0cd0608181043j4f5d6701x52af72309a48c033@mail.gmail.com> References: <3a2de0cd0608181043j4f5d6701x52af72309a48c033@mail.gmail.com> Message-ID: <1155931188.6117.21.camel@localhost.localdomain> On Fri, 2006-08-18 at 13:43 -0400, Charles Brian Quinn wrote: > 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!). Cool, did you make sure it runs with the latest pre-release? That's coming down as the official release very soon, as soon as I route out or rule out a bug. The main change for your stuff is that it's better to specify the log and pid file paths as absolute paths just to make sure they get set right. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Fri Aug 18 16:06:04 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 13:06:04 -0700 Subject: [Mongrel] Apache Proxy Error + Mongrel dying In-Reply-To: <20060818190128.GA13275@nezbo.dhcp.aub.dk> References: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> <20060818190128.GA13275@nezbo.dhcp.aub.dk> Message-ID: <1155931564.6117.26.camel@localhost.localdomain> On Fri, 2006-08-18 at 21:01 +0200, Jacob Atzen wrote: > On Fri, Aug 18, 2006 at 02:59:13PM +0200, Michele wrote: > Hello list, > > I'm seeing something like the same problem. Mongrels who suddenly stop > responding. I'm running an Apache mod_proxy with Mongrel backends setup. > And from time to time I'll get the following in the Apache error log > file: > Make sure you are running the latest pre-release: gem install mongrel --source=http://mongrel.rubyforge.org/releases/ And then if you still have the same error report *anything* you have in the mongrel.log, there should be some exceptions at least. > I'm on FreeBSD 6.1, Apache 2.2.3, Mongrel 0.3.13.4 (as I had another > issue and was advised to upgrade by Zed Shaw) and Rails 1.1.6 and > deploying with Mongrel_cluster and Capistrano. FreeBSD 6.1 seems to be the common factor for everyone having these problems. I'm guessing that FBSD 6.1 changed something subtle about how sockets work and now Mongrel is paying the penalty. Until I get one of these machines to play one I won't have a chance to fix this though (or even figure out if I'm right or not). -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From gusxedge at gmail.com Fri Aug 18 20:56:59 2006 From: gusxedge at gmail.com (Guillaume Carbonneau) Date: Fri, 18 Aug 2006 20:56:59 -0400 Subject: [Mongrel] Mongrel setting with Mysql error In-Reply-To: <1155930980.6117.18.camel@localhost.localdomain> References: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> <1155930980.6117.18.camel@localhost.localdomain> Message-ID: <3f4ebe010608181756i45d34f27v1482f80ba9c9b77f@mail.gmail.com> On 8/18/06, Zed Shaw wrote: > > On Fri, 2006-08-18 at 10:12 -0400, Guillaume Carbonneau wrote: > > 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 > > searching google, ruby and rails mailing list but didn't find > > anything. > > I'd appreciate if you guys could point me to the right direction. Like > > what steps I have to do to make mysql interact with Mongrel/Ruby. > > > > Haven't seen this from people who use win32, so I'm thinking your setup is > wrong somehow. > > Have you tried installing the win32 mysql gem? > > gem install mysql > > I believe that'll intall it but you have to pick win32. If you've > already done this then maybe remove it and see if you get the error. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users I updated my gems I tried removing / reinstalling the mysql gem and i'm still getting the error. I always pick the mswin32 btw... I noticed a pattern when I start the mongrel server.. 1st request generates this error : uninitialized constant Mysql 2nd and further errors : uninitialized constant ActiveRecord::Mysql Still getting errors. I tried with dead simple apps and it generates the same errors Thanks for your answers so far... Guillaume Carbonneau -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060818/9e438a9b/attachment.html From zedshaw at zedshaw.com Sat Aug 19 00:49:48 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Fri, 18 Aug 2006 21:49:48 -0700 Subject: [Mongrel] [ANN] Experiment in Online Mongrel Chat Support Message-ID: <1155962988.6175.5.camel@localhost.localdomain> Hi Folks, I was playing with Lingr today (http://www.lingr.com) and kind of like it, so I thought I'd setup a little room and see how it works for answering Mongrel questions. http://www.lingr.com/room/3yXhqKbfPy8 I'll be hanging there for a while and we'll see how it works out. If it works well, and doesn't turn into a nastier-than-IRC situation then I may turn it into a permanent thing. And no, lingr isn't paying me to use them, I'm not endorsing them, and they don't use Mongrel, they use FastCGI with comet: http://blog.lingr.com/2006/08/lingr_under_the.html So no whining or yelling out nasty words like "whore". That's not nice. ;-) -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From me at seebq.com Sat Aug 19 00:51:08 2006 From: me at seebq.com (Charles Brian Quinn) Date: Sat, 19 Aug 2006 00:51:08 -0400 Subject: [Mongrel] New automated Capistrano setup for Apache2.1+ and mongrel_cluster In-Reply-To: <1155931188.6117.21.camel@localhost.localdomain> References: <3a2de0cd0608181043j4f5d6701x52af72309a48c033@mail.gmail.com> <1155931188.6117.21.camel@localhost.localdomain> Message-ID: <3a2de0cd0608182151r71687278oe16fde8125f4fe46@mail.gmail.com> On 8/18/06, Zed Shaw wrote: > Cool, did you make sure it runs with the latest pre-release? That's > coming down as the official release very soon, as soon as I route out or > rule out a bug. The main change for your stuff is that it's better to > specify the log and pid file paths as absolute paths just to make sure > they get set right. I just updated my script, and made it work with the new mongrel pre-release. It has options to specify the prefix as a capistrano setting. It's totally improved and tried and tested to be able to run multiple mongrel_clusters on multiple vhosts simultaneously (and takes care of all ports). Some things to note that I forgot to mention last time: You'll need to have a line in your apache2 that says: Include /etc/rails/*.conf to pickup all the conf files for the multiple mongrel_clusters you're running You'll also want to have the line: NameVirtualHost *:80 to be able to serve up all your different named virtualhost servers for each app. Also one more thing, I put the amazingly feature-barren proxy-balancer manager on mongrel_start_port + 81, which ends up being 8081, so another cluster on 8100 would put it on port 8181. Just FYI. It could be configurable one day too, though. Newest version is here again: http://www.slingshothosting.com/files/apache2_2_mongrel_deploy.rb p.s. Zed I sent you some Apache2 best practices documents for the mongrel site. Did you receive them? Should I post the webgen files on rubyforge, or just submit a patch to current mongrel svn? p.p.s. a crazy mongrel: http://www.flickr.com/photos/cassi007/211404555/ -- Charles Brian Quinn self-promotion: www.seebq.com highgroove studios: www.highgroove.com slingshot hosting: www.slingshothosting.com From jan.svitok at gmail.com Sat Aug 19 02:38:30 2006 From: jan.svitok at gmail.com (Jan Svitok) Date: Sat, 19 Aug 2006 08:38:30 +0200 Subject: [Mongrel] Mongrel setting with Mysql error In-Reply-To: <3f4ebe010608181756i45d34f27v1482f80ba9c9b77f@mail.gmail.com> References: <3f4ebe010608180712u4e4d2d3er9d33b6924020b15f@mail.gmail.com> <1155930980.6117.18.camel@localhost.localdomain> <3f4ebe010608181756i45d34f27v1482f80ba9c9b77f@mail.gmail.com> Message-ID: <8d9b3d920608182338v1ee3eec9ya9f34f9ee4df8efc@mail.gmail.com> On 8/19/06, Guillaume Carbonneau wrote: > > > > On 8/18/06, Zed Shaw wrote: > > On Fri, 2006-08-18 at 10:12 -0400, Guillaume Carbonneau wrote: > > > 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 > > > searching google, ruby and rails mailing list but didn't find > > > anything. > > > I'd appreciate if you guys could point me to the right direction. Like > > > what steps I have to do to make mysql interact with Mongrel/Ruby. > > > > > > > Haven't seen this from people who use win32, so I'm thinking your setup is > wrong somehow. > > > > Have you tried installing the win32 mysql gem? > > > > gem install mysql > > > > I believe that'll intall it but you have to pick win32. If you've > > already done this then maybe remove it and see if you get the error. > > > > > > -- > > Zed A. Shaw > > http://www.zedshaw.com/ > > http://mongrel.rubyforge.org/ > > http://www.railsmachine.com/ -- Need Mongrel support? > > > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users at rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > I updated my gems > I tried removing / reinstalling the mysql gem and i'm still getting the > error. > I always pick the mswin32 btw... > > I noticed a pattern when I start the mongrel server.. > 1st request generates this error : uninitialized constant Mysql > 2nd and further errors : uninitialized constant ActiveRecord::Mysql > Still getting errors. I tried with dead simple apps and it generates the > same errors > > Thanks for your answers so far... > > Guillaume Carbonneau 1. in c:\ruby\lib\gems\gems\activerecord-x.x.x\lib\activerecord\connection_adapters\ (or similar) you should have mysql_adapter.rb. try a little test: just create instance of it, even without any configuration: require 'activerecord/adapters/mysql_adapter' ActiveRecord::ConnectionAdapters::MysqlAdapter.new() to see if it complains about the constant. 2. in c:\ruby\lib\gems\gems\activerecord-x.x.x\lib\activerecord\vendor\ you should have file mysql.rb - the pure rb mysql driver that is used if the binary one is not used. 3. change your ruby association temporarily to "c:\ruby\bin\ruby.exe" -dw "%1" %* to see all the exceptions and warnings. J. From jay.turpin at gmail.com Sat Aug 19 10:18:03 2006 From: jay.turpin at gmail.com (Jay Turpin) Date: Sat, 19 Aug 2006 07:18:03 -0700 Subject: [Mongrel] IIS and response timeout Message-ID: <4eda9d210608190718y207f3be8o70e00bbf41293eff@mail.gmail.com> I apologize if this has been covered before, I checked the archives and didn't see anything over the last few months. I am running IIS6 with IsapiRewriter and a single mongrel service for each Rails application. One of my apps does a long query to the database to produce a CSV file. After the request has gone beyond 30 seconds, the user get a 500 Internal Server Error. I've looked around for ways to adjust the response timeout, either in IIS or mongrel, but haven't found anything yet. Any ideas? -- -- Jay Turpin "One test is worth a thousand expert opinions." - Bill Nye (The Science Guy) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060819/92bcc485/attachment.html From will at hotgazpacho.com Sat Aug 19 10:37:37 2006 From: will at hotgazpacho.com (Will Green) Date: Sat, 19 Aug 2006 10:37:37 -0400 Subject: [Mongrel] IIS and response timeout In-Reply-To: <4eda9d210608190718y207f3be8o70e00bbf41293eff@mail.gmail.com> References: <4eda9d210608190718y207f3be8o70e00bbf41293eff@mail.gmail.com> Message-ID: <44E72231.9030507@hotgazpacho.com> For long running tasks, you should look into Ezra's BackgrounDRb: http://brainspl.at/articles/2006/07/02/backgroundrb-updated == Will Jay Turpin wrote: > I apologize if this has been covered before, I checked the archives > and didn't see anything over the last few months. > > I am running IIS6 with IsapiRewriter and a single mongrel service for > each Rails application. One of my apps does a long query to the > database to produce a CSV file. After the request has gone beyond 30 > seconds, the user get a 500 Internal Server Error. > > I've looked around for ways to adjust the response timeout, either in > IIS or mongrel, but haven't found anything yet. Any ideas? > > -- > -- Jay Turpin > "One test is worth a thousand expert opinions." - Bill Nye (The > Science Guy) > >------------------------------------------------------------------------ > >_______________________________________________ >Mongrel-users mailing list >Mongrel-users at rubyforge.org >http://rubyforge.org/mailman/listinfo/mongrel-users > From mail at flydown.org Sat Aug 19 15:29:53 2006 From: mail at flydown.org (Michele) Date: Sat, 19 Aug 2006 21:29:53 +0200 Subject: [Mongrel] Apache Proxy Error + Mongrel dying In-Reply-To: <1155930788.6117.14.camel@localhost.localdomain> References: <65FCC3F2-0058-414B-BEEA-CB6148741005@flydown.org> <1155930788.6117.14.camel@localhost.localdomain> Message-ID: Zed, I got it: there was a piece of code trying to redirect_to(nil) every now and then. What I don't understand is I got a normal Rails error while in development (Stack level too deep), but Mongrel crashed in production, thus not writing the error to the log. - Michele On Aug 18, 2006, at 21:53 , Zed Shaw wrote: > On Fri, 2006-08-18 at 14:59 +0200, Michele wrote: >> If I run Mongrel 0.3.13.4 in debug mode, I get this error before the >> process dies: "Illegal instruction: 4 (core dumped)". >> >> What could it be? Is there a way which instruction is causing the >> error? > > What operating system and version? How'd you build your ruby? After > how > long does this happen? Does it tell you line number of where it > happens? Is the line number consistent? > > Try running it under gdb, then when it dies type: backtrace and > send me > the output. That or run the program under strace and give me the last > bit of the output before it died. > > > -- > Zed A. Shaw > http://www.zedshaw.com/ > http://mongrel.rubyforge.org/ > http://www.railsmachine.com/ -- Need Mongrel support? > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From scarydog at mac.com Sun Aug 20 03:25:06 2006 From: scarydog at mac.com (Nathan Donaldson) Date: Sun, 20 Aug 2006 19:25:06 +1200 Subject: [Mongrel] Problem with: service mongrel_cluster start Message-ID: <57AB69ED-924B-4652-80E8-658EB33D38E2@mac.com> Hi all, I am having trouble transitioning from fastcgi to Mongrel. I have it all working apart from one small part, I can't get the service to start on boot. I have followed the instructions and if I call the script directly: i.e. "/etc/init.d/mongrel_cluster start" it works fine, but if I call it using "service mongrel_cluster start" it fails with the following error: Starting all mongrel_clusters... /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21: command not found: mongrel_rails cluster::start -c sonar_radiant.yml mongrel_rails cluster::start returned an error. I can see what is happening, it is calling mongrel_rails cluster::start -c config_file_without the directory. It should say: mongrel_rails cluster::start -c /etc/mongrel_cluster/sonar_radiant.yml Anyone know what I can do to fix this? Regards Nathan From lapomme00 at gmail.com Sun Aug 20 03:53:30 2006 From: lapomme00 at gmail.com (Brett Walker) Date: Sun, 20 Aug 2006 15:53:30 +0800 Subject: [Mongrel] Version number in log file... Message-ID: I have one small suggestion, after just upgrading to the 0.13.4 pre-release. What about putting the version number in the log? This way it's easy to verify what version we're running. Maybe Starting Mongrel (v0.13.4) listening at 127.0.0.1:8000 or something. Cheers, Brett From snacktime at gmail.com Sun Aug 20 05:50:27 2006 From: snacktime at gmail.com (snacktime) Date: Sun, 20 Aug 2006 02:50:27 -0700 Subject: [Mongrel] http parser Message-ID: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.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 wouldn't be all that much work I don't think. Took me about an hour to create a working http server with Eventmachine, your parser, and subclassing HttpRequest to get rid of the socket reading. I'll spend some more time on it tommorrow and see how it progresses. Chris From ezmobius at gmail.com Sun Aug 20 15:26:01 2006 From: ezmobius at gmail.com (Ezra Zygmuntowicz) Date: Sun, 20 Aug 2006 12:26:01 -0700 Subject: [Mongrel] http parser In-Reply-To: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> Message-ID: On Aug 20, 2006, at 2:50 AM, snacktime wrote: > 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 wouldn't be all that much work I > don't think. Took me about an hour to create a working http server > with Eventmachine, your parser, and subclassing HttpRequest to get rid > of the socket reading. I'll spend some more time on it tommorrow and > see how it progresses. > > Chris > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > Hey Chris- I would love to see your code for this. I have been working with eventmachine on some similar stuff. -Ezra From zedshaw at zedshaw.com Sun Aug 20 16:08:27 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sun, 20 Aug 2006 13:08:27 -0700 Subject: [Mongrel] http parser In-Reply-To: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> Message-ID: <1156104507.6252.16.camel@localhost.localdomain> On Sun, 2006-08-20 at 02:50 -0700, snacktime wrote: > 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 wouldn't be all that much work I > don't think. Took me about an hour to create a working http server > with Eventmachine, your parser, and subclassing HttpRequest to get rid > of the socket reading. I'll spend some more time on it tommorrow and > see how it progresses. The EventMachine stuff doesn't really buy you much since they use Ruby's select still to process connections. That means you're still stuck with 1024 max files and still stuck with Ruby's threads. All they do is then move IO processing out to a *large* amount of convoluted C++ code. I'm sure you'll love security auditing that. :-) They are also working on their Mongrel competitor, but being in true open source NIH form couldn't be bothered to borrow the parser I wrote and decided to write their own by hand (it's like I don't even say anything). For whatever reason I've always thought those guys were a little on the shady side. Not sure why, they just seem desperate for cash or something. I'd say play around with it and if you get something interesting working then that's cool, but in the end adding even more compiled code that I'd have to distribute that's then tied to a group of developers who're obviously trying to make bank off my work isn't going to go over well. FYI, I'm also working on a different approach that moves all of the HTTP processing into an ultra fast ucontext/poll based IO system. I'm hoping it'll work with any language too (Python baby). But don't let this discourage you, Mongrel is open source so people can try these things out. You never know, it could end up being the bee's knees on a platform like win32. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From snacktime at gmail.com Sun Aug 20 16:38:42 2006 From: snacktime at gmail.com (snacktime) Date: Sun, 20 Aug 2006 13:38:42 -0700 Subject: [Mongrel] http parser In-Reply-To: References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> Message-ID: <1f060c4c0608201338j56962604xeb2d8ff7910e0860@mail.gmail.com> Here is a quick and dirty example of how to use the parser. Notice that the server isn't sending a valid reply to the client, and the handler doesn't exist, I added that just as an example for others of how you might use the Eventmachine thread pool to run the handler. But you should get the general idea. Zed correct me if I am wrong, but nparsed returns the length of the headers that were parsed, so if the parser finishes nparsed is the header length. Then I just add the content length to that and keep reading until we get all the content. I also subclassed HttpRequest since in mongrel that's where the rest of the body is read, but in eventmachine it's not. To use EM in mongrel you would need to find the best way to only run one handler at a time. An array of connections in process_request together with a state variable might work. New requests get pushed onto a list, and process_request takes the first request in the list, sets the state to busy, then when it's done sets the state to idle and checks the array for more request to process before finishing. Need to think that one through a bit more. require 'rubygems' require 'mongrel' require 'eventmachine' class Mongrel::HttpRequest attr_reader :body, :params # You don't really call this. It's made for you. # Main thing it does is hook up the params, and store any remaining # body data into the HttpRequest.body attribute. # # TODO: Implement tempfile removal when the request is done. def initialize(params, initial_body) @params = params end class Server < EventMachine::Connection def initialize *args super @linebuffer = "" end def post_init @parser = Mongrel::HttpParser.new @params = {} @nparsed = 0 @request = nil @request_len = nil #start_tls end def unbind puts "Connection Closed\r\n" end def process_request(request) # Run the handler in a thread. Not implemented just put here to show how to use # EventMachine.defer to run the handler in EventMachine's thread pool. start = proc {run_handler} stop = proc {|r| send_data r close_connection } EventMachine.defer(start,stop) end def receive_data data @linebuffer << data @nparsed = @parser.execute(@params, @linebuffer, @nparsed) p "nparsed=#{@nparsed}" if @parser.finished? if @request_len.nil? @request = Mongrel::HttpRequest.new(@params, at linebuffer) @request_len = @nparsed + @request.params[Mongrel::Const::CONTENT_LENGTH].to_i if @linebuffer.length >= @request_len process_request(@request) end elsif @linebuffer.length >= @request_len process_request(@request) end end end end EventMachine::run { EventMachine::start_server "127.0.0.1", 80, Server } From snacktime at gmail.com Sun Aug 20 16:50:03 2006 From: snacktime at gmail.com (snacktime) Date: Sun, 20 Aug 2006 13:50:03 -0700 Subject: [Mongrel] http parser In-Reply-To: <1156104507.6252.16.camel@localhost.localdomain> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> Message-ID: <1f060c4c0608201350g44c3d886geb70eac8602bd58a@mail.gmail.com> On 8/20/06, Zed Shaw wrote: > On Sun, 2006-08-20 at 02:50 -0700, snacktime wrote: > > 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 wouldn't be all that much work I > > don't think. Took me about an hour to create a working http server > > with Eventmachine, your parser, and subclassing HttpRequest to get rid > > of the socket reading. I'll spend some more time on it tommorrow and > > see how it progresses. > > The EventMachine stuff doesn't really buy you much since they use Ruby's > select still to process connections. I didn't realize that. I thought they used a native select. If that's the case then EM would actually perform worse, since you are always grabbing threads from a pool to run blocking operations and then jumping back into the event loop. I do like how you did your parser though, it would be easy to drop that into pretty much any ruby project that needs an http parser. Chris From garbagecat10 at gmail.com Sun Aug 20 17:04:41 2006 From: garbagecat10 at gmail.com (Francis Cianfrocca) Date: Sun, 20 Aug 2006 17:04:41 -0400 Subject: [Mongrel] http parser In-Reply-To: <1156104507.6252.16.camel@localhost.localdomain> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> Message-ID: <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> On 8/20/06, Zed Shaw wrote: > The EventMachine stuff doesn't really buy you much since they use Ruby's > select still to process connections. That means you're still stuck with > 1024 max files and still stuck with Ruby's threads. All they do is then > move IO processing out to a *large* amount of convoluted C++ code. I'm > sure you'll love security auditing that. :-) > > They are also working on their Mongrel competitor, but being in true > open source NIH form couldn't be bothered to borrow the parser I wrote > and decided to write their own by hand (it's like I don't even say > anything). For whatever reason I've always thought those guys were a > little on the shady side. Not sure why, they just seem desperate for > cash or something. > > I'd say play around with it and if you get something interesting working > then that's cool, but in the end adding even more compiled code that I'd > have to distribute that's then tied to a group of developers who're > obviously trying to make bank off my work isn't going to go over well. > > FYI, I'm also working on a different approach that moves all of the HTTP > processing into an ultra fast ucontext/poll based IO system. I'm hoping > it'll work with any language too (Python baby). > > But don't let this discourage you, Mongrel is open source so people can > try these things out. You never know, it could end up being the bee's > knees on a platform like win32. It's hard to know how to answer this, given that I've felt the Ruby community has generally been about looking for good answers to technical problems, and not about making unsupported statements that have a strong odor of suspicion and insecurity about them. EventMachine is not and has never been fundamentally about HTTP. It started out as a general framework for writing fast, event-driven programs without having to use threads, and it wasn't designed only for working with Ruby. It is stuck with a limit of the number of descriptors when used with Ruby because we hook Ruby's select implementation in order to interoperate with Ruby threads, which EM does with no problems whatsoever. I wrote the EM I/O engine in C++ for two primary reasons: first because this code base builds on more than ten years of experience with extremely high-speed network servers on a range of different platforms. And second, because when I wrote it (last April), Ruby didn't have proper nonblocking I/O. The Ruby-core guys generously added proper nonblocking support at the end of May, and at this point EM has a nearly-complete pure Ruby implementation, that has an identical API and will be used transparently on platforms where the extension fails to compile. I just checked EM's C++ code, and it's only 4200 lines. That's not a *large* amount of code. It's a *small* amount of code. If you think it's "convoluted," then I have to say you probably haven't tried to read it. (It's also possible that you're not that strong a C++ programmer.) I've been through some hard-core source-code audits in my time, and I'm confident this code would pass without an abnormal amount of effort. And at any rate, it's wide open on Rubyforge SCM, so anyone and everyone is invited to take a crack at finding the security holes in it. We'll gratefully accept any patch correcting security flaws. Working on a Mongrel competitor: I'm not particularly interested in competing against Mongrel for a couple of reasons. Most importantly, I'm not entirely sure what Mongrel's goal in life is. It seems nice to have a better-performing Webrick, but you've also said that you expect Mongrel to be deployed in conjunction with Apache or Lighty, so I'm left assuming the primary value-added is that people can save the trouble of configuring FastCGI or such stuff. Also, it seems nice to be able to cluster Rails instances intelligently. And you have said to me yourself that adding faster I/O to Rails is of limited value because there are so many performance problems in Rails itself. And none of those are problems I'm interested in solving any differently than you have. I'm not quite sure what you think anything I'm working on is that might be competitive to Mongrel. I know that Mongrel has an HTTP parser in it, and we have one too, but that's not a whole lot of overlap. I've read your statements on parsing HTTP, and I'm not terribly convinced by your approach, which seems to be all about implementing a very complex RFC as completely and strictly as possible. I've been writing practical high-speed HTTP parsers for almost ten years now, and I know a lot about which parts of the standard(s) really matter and which matter less, and also about which parts should be treated in a relaxed way. You and I are trying to solve different problems, and for my problem-domain, your chosen approach isn't too interesting. You're trying to write a well-behaved proxying layer between Rails and standard web servers. I'm trying to write a general framework for event-driven applications that can easily incoroporate a range of different protocols. Speed and ease of development matter a lot more to me than strict conformance with RFC 2616. >>>For whatever reason I've always thought those guys were a little on the shady side. Not sure why, they just seem desperate for cash or something.<<< This borders on libel. I challenge you to produce the evidence on the basis of which you make these statements. I've been a senior technology executive and investor for quite a long time. I don't contribute to open-source projects in order to make a living. Are you willing to make the same statement in regard to yourself? >>>but in the end adding even more compiled code that I'd have to distribute that's then tied to a group of developers who're obviously trying to make bank off my work isn't going to go over well.<<< To my knowledge, no one in my group is trying to induce you to add anything, compiled or otherwise, to your code base. Your statement sounds like more than just protesting too much: it sounds insecure. I can't speak for your motivations, but the rest of us just want to work with the best possible technology, and investigate new ideas to see if they lead to interesting places. Zed, you're an important guy in the community and you've written some impressive technology. But you're showing a personal side that is quite disappointing. From garbagecat10 at gmail.com Sun Aug 20 17:21:12 2006 From: garbagecat10 at gmail.com (Francis Cianfrocca) Date: Sun, 20 Aug 2006 17:21:12 -0400 Subject: [Mongrel] http parser In-Reply-To: <1f060c4c0608201350g44c3d886geb70eac8602bd58a@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <1f060c4c0608201350g44c3d886geb70eac8602bd58a@mail.gmail.com> Message-ID: <3a94cf510608201421n56f540acjc0ba08b2f9281d9a@mail.gmail.com> On 8/20/06, snacktime wrote: > > > I didn't realize that. I thought they used a native select. If > that's the case then EM would actually perform worse, since you are > always grabbing threads from a pool to run blocking operations and > then jumping back into the event loop. I do like how you did your > parser though, it would be easy to drop that into pretty much any ruby > project that needs an http parser. Read the code, Chris. We use a native select loop built in the normal (native) way, using fully nonblocking I/O. There are no threads anywhere inside of EventMachine (except for the thread pool accessed by #defer which you and I have already corresponded about). When EM is built for a Ruby environment, it hooks Ruby's thread scheduler to give Ruby a chance to run its threads. It's not any slower. You've already seen that EM can make 1000 TCP client connections in well under a second. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060820/a0f61357/attachment.html From zedshaw at zedshaw.com Sun Aug 20 18:32:11 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sun, 20 Aug 2006 15:32:11 -0700 Subject: [Mongrel] http parser In-Reply-To: <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> Message-ID: <1156113131.7991.50.camel@localhost.localdomain> On Sun, 2006-08-20 at 17:04 -0400, Francis Cianfrocca wrote: > On 8/20/06, Zed Shaw wrote: While a public forum might not be the place to air my thoughts, since you replied here, I'll comment here. Feel free to contact me off list so we can possibly patch this up. Let's skip all the technical stuff for now, and focus on this one area: > >>>For whatever reason I've always thought those guys were a > little on the shady side. Not sure why, they just seem desperate for > cash or something.<<< > This borders on libel. I challenge you to produce the evidence on the > basis of which you make these statements. I've been a senior > technology executive and investor for quite a long time. I don't > contribute to open-source projects in order to make a living. Are you > willing to make the same statement in regard to yourself? > > >>>but in the end adding even more compiled code that I'd > have to distribute that's then tied to a group of developers who're > obviously trying to make bank off my work isn't going to go over well.<<< > To my knowledge, no one in my group is trying to induce you to add > anything, compiled or otherwise, to your code base. Your statement > sounds like more than just protesting too much: it sounds insecure. I > can't speak for your motivations, but the rest of us just want to work > with the best possible technology, and investigate new ideas to see if > they lead to interesting places. You know what man, you're right, that was uncalled for. You aren't shady (no irony here, I'm seriously apologizing). But, let's go over what behaviors you're doing that make me think you're not completely honest in your intentions. Then you can explain them to me and we can come to an understanding. First off, if we're going to throw out legal challenges then lets compare project names. You have a very nasty habit of picking project names that are very similar to names of already established or more famous projects. Let's compare: * Ruby/EventMachine -- http://rubyforge.org/projects/eventmachine/ * Ruby/Event -- http://www.zedshaw.com/projects/ruby_event/ * monorail -- http://rubyforge.org/projects/monorail/ * monorail -- http://www.castleproject.org/index.php/MonoRail * Which is really similar to "mongrel rails", but let's just say that wasn't your intention. Then, you also have a habit of creating these to be similar to existing ones, pimping them in what seems like an attempt to wipe out the existing projects: "Monorail is the lightweight, fast, scalable and SECURE alternative to Ajax-application frameworks. Its native-HTTP server incorporates SSL and auth/az services natively. Page development is Rails-like but simpler." It looks like you're capitalizing on Rails fame and Mongrel fame at the same time, then telling people that your framework is more SECURE. Yet, you have this in your monorail:http.cpp file: // This processing depends on the fact that the end // of the data buffer we receive will have a null terminator // just after the last byte indicated by the length parameter. Anyone worth his SECURE salt knows that using \0 buffer termination is *not* secure. Not to mention this gem of a buffer overflow: else if (!strncasecmp (header, "cookie:", 7)) { const char *s = header + 7; while (*s && ((*s==' ') || (*s=='\t'))) s++; setenv ("HTTP_COOKIE", s, true); } (HINT: A while loop that waits for a \0 terminator is always wrong.) Finally, in every communication I've had with you, you've never contributed anything to Mongrel or any of my work. You've been very adamant about me using *your* work, and me *doing the work* to use your stuff, but you've never contributed. Mr. snacktime has done more to get Mongrel working with EventMachine than you have. In fact, I've contributed more to your software than you have to mine: http://rubyforge.org/forum/forum.php?forum_id=6607 Which means, in my *opinion* you take and do not give. In fact, I wrote this: http://mongrel.rubyforge.org/not_mongrel.html Partially in response to your behavior. If you remember you e-mailed me repeatedly asking me to use your Ruby/EventMachine to power Mongrel, despite my concerns about your licensing, copyright and motivations (which I told you then). In summary, the fact that you: * Create competitive projects that are closely named to mine. * Make false security claims about your work. * Imply that your work is more secure than mine (yet without a security testing policy, unlike Mongrel). * Use my advice and work to further your own means without contributing back in kind. * AND accuse me of libel (which only a profit motivated "open source" person would do). All point to why I don't much appreciate your behavior and don't think highly of your true motivations. Now, I don't know you personally, you may be a great guy for all I know. But I am basing my *opinion* of your business practices on the above evidence. If there's a misunderstanding in how you behave and act toward me then feel free to talk to me about it off list. Until then, I'd appreciate it if you'd stop naming your projects after mine, stop pimping your projects on *my* mailing list, and stop accusing me of libel when I have supporting evidence of my opinion. You're free to compete with Mongrel, but don't use my project to further your gains. Thanks for your time. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From garbagecat10 at gmail.com Sun Aug 20 19:49:30 2006 From: garbagecat10 at gmail.com (Francis Cianfrocca) Date: Sun, 20 Aug 2006 19:49:30 -0400 Subject: [Mongrel] http parser In-Reply-To: <1156113131.7991.50.camel@localhost.localdomain> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> Message-ID: <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> On 8/20/06, Zed Shaw wrote: > > First off, if we're going to throw out legal challenges then lets > compare project names. You have a very nasty habit of picking project > names that are very similar to names of already established or more > famous projects. Let's compare: > > * Ruby/EventMachine -- http://rubyforge.org/projects/eventmachine/ > * Ruby/Event -- http://www.zedshaw.com/projects/ruby_event/ I picked the name for EventMachine before I was aware of yours. I used the word "Ruby" in my title because EM doesn't work only with Ruby, and that was intended to indicate a version that had Ruby bindings. As far as "Event" is concerned, there are plenty of projects with that word in their titles (libevent for one), that have primacy over yours. But no one is trying to make money off this, so where's the issue? * monorail -- http://rubyforge.org/projects/monorail/ > * monorail -- http://www.castleproject.org/index.php/MonoRail > * Which is really similar to "mongrel rails", but let's just say that > wasn't your intention. "Monorail" was picked out of the air by a guy who works for me as we were thinking about a lighter-weight version of Rails. You've evidently researched this project, which is gratifying, but it's not a released project, and anyway has evolved a great deal. It's no longer a lighter Rails, but something else entirely, and not competitive to Rails. As far as competing against Mongrel in this connection, I have to smile at your self-importance, but Mongrel wasn't even on our radar. In regard to the Castle guys, we became aware a couple of weeks ago that they were using "Monorail," and we're still looking into whether we have priority over the name (our first pub was last April, and theirs is a recent name change). If it turns out theirs was published before ours, we'll change ours. Then, you also have a habit of creating these to be similar to existing > ones, pimping them in what seems like an attempt to wipe out the > existing projects: I create a lot of projects, Zed, and I (and the guys who work for me) make up a lot of code names. They can't all be unique gems, especially not for the open source ones where the point isn't to make any money. I spend a lot of time (and money) coming up with well-researched names for my commercial projects. And if you think I have it in mind to wipe out Rails, all I can say is that I have far more realistic goals in life, nor do I think Rails, which benefits a lot of people, deserves to be wiped out. But if you think I have in mind to wipe out Mongrel, then I have to laugh and ask you why you're afraid of me! > > // This processing depends on the fact that the end > // of the data buffer we receive will have a null terminator > // just after the last byte indicated by the length parameter. > > Anyone worth his SECURE salt knows that using \0 buffer termination is > *not* secure. In the first place, Zed, this comment is in code that is NOT in the EventMachine, but in a project based on it. Note the code in EM that creates the buffers that are passed to the code path where the comment you quoted appears. There is specific language in there specifying a guaranteed behavior that all buffers generated by EM for passing to user code will have an extra appended null terminator. > Not to mention this gem of a buffer overflow: > > else if (!strncasecmp (header, "cookie:", 7)) { > const char *s = header + 7; > while (*s && ((*s==' ') || (*s=='\t'))) > s++; > setenv ("HTTP_COOKIE", s, true); > } > > (HINT: A while loop that waits for a \0 terminator is always wrong.) You're reaching, Zed, and it's not impressing me. That while loop stops when it finds a character that isn't blank or tab. Obviously it's also going to stop if it hits the end of the string. It would be far less safe (not to mention wrong) if it didn't. Also notice the (only) call to this (private) method that contains this code path. The line immediately preceding it ensures the null terminator is present. On contributing to your work: you have it pretty well under control, so what help do you need from me? I wrote to you back in April or May to ask if you had an interest in it, and you made it quite clear that you didn't. So I didn't bother to ask the question again. That's no problem for you or for me. But if you think I was "adamant" about you using my work, all I can say to that is that I'm an experienced technology salesman, and I try to convince people by being persuasive, not adamant. Again, you made it clear you weren't interested, so that's the end of that story. As far as you contributing to my work, you pointed out that you had had a problem with your Event library that I hadn't tested for. You also said you hadn't been able to solve it. I solved it, then solved it again in a better way. I acknowledged you for pointing out the problem, which I do with everyone who helps me out, but your point here would be a lot more compelling if you had actually contributed a solution. But again, this is open-source freeware, Zed. We're all supposed to be helping each other, and no one is trying to take food out of anyone's mouth. None of us are involved in this for money. You really need to lighten up. * Imply that your work is more secure than mine (yet without a security > testing policy, unlike Mongrel). > * Use my advice and work to further your own means without contributing > back in kind. You're really giving the game up here, Zed. I've never so much as mentioned Mongrel in any public communication that I'm aware of, much less implied that an unpublished product in a totally different space is more secure than yours. This isn't personal, Zed. The fact that you're making it personal really makes me wonder about you. * AND accuse me of libel (which only a profit motivated "open source" > person would do). I said your statements "border on libel." You stated that my friends and I are somewhat shady in your opinion, and perhaps desperate for cash. Libel is a written statement of disparaging character that is not substantiated by facts, and you haven't provided any. I don't let ANYONE mess with me the way you did. > it if you'd stop naming your projects after mine, stop pimping your > projects on *my* mailing list, I'll name my projects however I wish, but I already do make a practice of not knowingly infringing on other people's marks. I've paid enough money to trademark lawyers over the years to know where the lines are. I have never ONCE written a single thing on your mailing list until this afternoon, and that was in answer to your unwarranted and borderline-libelous comments about me, not to "pimp" anything. Once again, you need to lighten up. You're free to compete with Mongrel, > but don't use my project to further your gains. If I had any interest in competing against Mongrel, believe me, you'd know it. If you think I am getting "gains" from giving away open-source freeware, then you flatter me unduly. If you think I'm stealing from you, you're flattering yourself unduly. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060820/d97c718f/attachment.html From zedshaw at zedshaw.com Sun Aug 20 20:56:14 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sun, 20 Aug 2006 17:56:14 -0700 Subject: [Mongrel] http parser In-Reply-To: <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> Message-ID: <1156121774.6076.20.camel@localhost.localdomain> On Sun, 2006-08-20 at 19:49 -0400, Francis Cianfrocca wrote: When you have statements like this: > Libel is a written statement of disparaging character that is not > substantiated by facts, and you haven't provided any. I don't let > ANYONE mess with me the way you did. (You forgot "that causes damages", of which you have none). ...is when I get worried. I'll of course take it personally when you take an off-handed sentence as a reason to make threats like the above. I take threats of lawsuit very seriously. *This* is the reason nobody should trust you. You are a stated "technology salesman" who has threatened a free project developer with a law suit in public for a few sentences in an e-mail. It doesn't get much more predatory than that. Feel free to file your lawsuit with the stated damages from the above e-mail exchange. I'll gladly give you my lawyer's number so you can file the complaint. I'm sure everyone will love you for shutting down a popular open source project. Or, we can end this here with you accepting my apology for saying you're shady (yes, that was wrong), and for you apologizing for threatening me with legal action (twice). Even mentioning "libel" in this world is cause for threat. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From garbagecat10 at gmail.com Sun Aug 20 21:38:27 2006 From: garbagecat10 at gmail.com (Francis Cianfrocca) Date: Sun, 20 Aug 2006 21:38:27 -0400 Subject: [Mongrel] http parser In-Reply-To: <1156121774.6076.20.camel@localhost.localdomain> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> <1156121774.6076.20.camel@localhost.localdomain> Message-ID: <3a94cf510608201838h3cdf047nb1e3da7510fc85ae@mail.gmail.com> On 8/20/06, Zed Shaw wrote: > On Sun, 2006-08-20 at 19:49 -0400, Francis Cianfrocca wrote: > > > Libel is a written statement of disparaging character that is not > > substantiated by facts, and you haven't provided any. I don't let > > ANYONE mess with me the way you did. > (You forgot "that causes damages", of which you have none). > > ...is when I get worried. > I didn't threaten you, Zed, not at any point. You made statements not substantiated by facts that are potentially damaging to my reputation, and I take that seriously. You apologized for calling me and my friends shady. Accepted. But what was your basis and your evidence for saying that we are desperate for cash? Especially since neither you nor I make our livings from our freeware Ruby projects! I can't understand your motivations but I think any reasonable person would read your statements, in a forum that you control and in which you are well-respected, as intended to cast doubt on (and thus impair the value of) a project that I have contributed a great deal of time and effort to. If that wasn't your intention, then say so and we're done. This is your list, so you can also tell me to pound sand and not post here again, and I'll respect that too. From zedshaw at zedshaw.com Mon Aug 21 00:36:20 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Sun, 20 Aug 2006 21:36:20 -0700 Subject: [Mongrel] http parser In-Reply-To: <3a94cf510608201838h3cdf047nb1e3da7510fc85ae@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> <1156121774.6076.20.camel@localhost.localdomain> <3a94cf510608201838h3cdf047nb1e3da7510fc85ae@mail.gmail.com> Message-ID: <1156134980.5788.20.camel@localhost.localdomain> On Sun, 2006-08-20 at 21:38 -0400, Francis Cianfrocca wrote: > On 8/20/06, Zed Shaw wrote: > > On Sun, 2006-08-20 at 19:49 -0400, Francis Cianfrocca wrote: > > > > > Libel is a written statement of disparaging character that is not > > > substantiated by facts, and you haven't provided any. I don't let > > > ANYONE mess with me the way you did. > > (You forgot "that causes damages", of which you have none). > > > > ...is when I get worried. > > > > I didn't threaten you, Zed, not at any point. You made statements not > substantiated by facts that are potentially damaging to my reputation, > and I take that seriously. > Don't even mention the word "libel" again unless you file a suit. You're free to say what you want about me, and anyone I know, but don't threaten me ever again or even imply the threat of lawsuit. Since you refuse to apologize this will be my last e-mail on the topic with you. > If that wasn't your intention, then say so and we're done. This is > your list, so you can also tell me to pound sand and not post here > again, and I'll respect that too. I don't believe in censoring people who have a difference of opinion with me, I feel that everyone has a right to express their opinions in an open forum and censoring you would be wrong. Like I said before, I've got no problem with you since I don't know you, I have a problem with your behavior. That's the difference, I would have handled the same situation by e-mailing you personally and ask you to retract your statements, not attack you in your own backyard. I'd assume that maybe you were having a bad day and give you a chance make amends. I wouldn't go on a Freudian innuendo rampage about your insecurities and toss around empty threats of "libel". Have a good day Francis. -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support? From zedshaw at zedshaw.com Mon Aug 21 08:26:34 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 21 Aug 2006 05:26:34 -0700 Subject: [Mongrel] The Public Appology To Francis Cianfrocca Message-ID: <1156163194.8358.13.camel@localhost.localdomain> Dear Mongrel Users, It appears that Francis still isn't satisfied with my attempts to apologize and he's now asked me privately to retract my statements. So, just to be sure he finally gets it: I retract my statements that Francis and his friends are "shady" and "desperate for cash". He is in no way a shady guy, having dealt with this situation with the utmost of professionalism and courtesy with me. He is also obviously not threatened by any of my work and feels no pressure to compete with me, infect his work into mine, or any of the other statements he so quickly felt slighted by. And again, sincere apologies all around to anyone who's felt he was in the right and I'm a bad guy. I shall use my power to influence people more appropriately with rational technical comparisons from now on. Hopefully, this will put a final end to any misconceptions as to the depth of my remorse for having said that Francis is shady or desperate for cash. My heart felt apologies. Zed From zedshaw at zedshaw.com Mon Aug 21 08:28:30 2006 From: zedshaw at zedshaw.com (Zed Shaw) Date: Mon, 21 Aug 2006 05:28:30 -0700 Subject: [Mongrel] http parser In-Reply-To: <3a94cf510608201838h3cdf047nb1e3da7510fc85ae@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> <1156121774.6076.20.camel@localhost.localdomain> <3a94cf510608201838h3cdf047nb1e3da7510fc85ae@mail.gmail.com> Message-ID: <1156163310.8358.15.camel@localhost.localdomain> On Sun, 2006-08-20 at 21:38 -0400, Francis Cianfrocca wrote: > On 8/20/06, Zed Shaw wrote: > > On Sun, 2006-08-20 at 19:49 -0400, Francis Cianfrocca wrote: > > > > > Libel is a written statement of disparaging character that is not > > > substantiated by facts, and you haven't provided any. I don't let > > > ANYONE mess with me the way you did. > > (You forgot "that causes damages", of which you have none). > > > > ...is when I get worried. > > > > I didn't threaten you, Zed, not at any point. You made statements not > substantiated by facts that are potentially damaging to my reputation, > and I take that seriously. > > You apologized for calling me and my friends shady. Accepted. But what > was your basis and your evidence for saying that we are desperate for > cash? Especially since neither you nor I make our livings from our > freeware Ruby projects! I can't understand your motivations but I > think any reasonable person would read your statements, in a forum > that you control and in which you are well-respected, as intended to > cast doubt on (and thus impair the value of) a project that I have > contributed a great deal of time and effort to. > > If that wasn't your intention, then say so and we're done. This is > your list, so you can also tell me to pound sand and not post here > again, and I'll respect that too. Now, will you please leave me alone? I have to get another release of Mongrel out so that Apple can include it in their next release of OSX. Sent to the list just now, so please take it as a full retraction and apology, and again if you're not satisfied then from now on have your lawyer talk to me instead. ----- Dear Mongrel Users, It appears that Francis still isn't satisfied with my attempts to apologize and he's now asked me privately to retract my statements. So, just to be sure he finally gets it: I retract my statements that Francis and his friends are "shady" and "desperate for cash". He is in no way a shady guy, having dealt with this situation with the utmost of professionalism and courtesy with me. He is also obviously not threatened by any of my work and feels no pressure to compete with me, infect his work into mine, or any of the other statements he so quickly felt slighted by. And again, sincere apologies all around to anyone who's felt he was in the right and I'm a bad guy. I shall use my power to influence people more appropriately with rational technical comparisons from now on. Hopefully, this will put a final end to any misconceptions as to the depth of my remorse for having said that Francis is shady or desperate for cash. My heart felt apologies. Zed From garbagecat10 at gmail.com Mon Aug 21 08:58:41 2006 From: garbagecat10 at gmail.com (Francis Cianfrocca) Date: Mon, 21 Aug 2006 08:58:41 -0400 Subject: [Mongrel] The Public Appology To Francis Cianfrocca In-Reply-To: <1156163194.8358.13.camel@localhost.localdomain> References: <1156163194.8358.13.camel@localhost.localdomain> Message-ID: <3a94cf510608210558q40e20f84n165b05733ca9be0@mail.gmail.com> On 8/21/06, Zed Shaw wrote: > Dear Mongrel Users, > > It appears that Francis still isn't satisfied with my attempts to > apologize and he's now asked me privately to retract my statements. > > So, just to be sure he finally gets it: > > I retract my statements that Francis and his friends are "shady" and > "desperate for cash". He is in no way a shady guy, having dealt with > this situation with the utmost of professionalism and courtesy with me. > He is also obviously not threatened by any of my work and feels no > pressure to compete with me, infect his work into mine, or any of the > other statements he so quickly felt slighted by. > > And again, sincere apologies all around to anyone who's felt he was in > the right and I'm a bad guy. I shall use my power to influence people > more appropriately with rational technical comparisons from now on. > > Hopefully, this will put a final end to any misconceptions as to the > depth of my remorse for having said that Francis is shady or desperate > for cash. > > My heart felt apologies. > > Zed > Your statements have had the (perhaps inadvertent) effect of maligning not only myself but also several well-respected members of the Ruby Community who have contributed to the EventMachine project generously and without thought of recompense. Their names are listed on the Rubyforge project page and at various points in the EM source code. On behalf of all those people, I accept your gracious and sincere apology. From drewr at pobox.com Mon Aug 21 12:31:55 2006 From: drewr at pobox.com (Drew Raines) Date: Mon, 21 Aug 2006 11:31:55 -0500 Subject: [Mongrel] Problem with: service mongrel_cluster start References: <57AB69ED-924B-4652-80E8-658EB33D38E2@mac.com> Message-ID: Nathan Donaldson wrote: > Starting all mongrel_clusters... > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21: > command not found: mongrel_rails cluster::start -c sonar_radiant.yml > mongrel_rails cluster::start returned an error. > > I can see what is happening, it is calling mongrel_rails > cluster::start -c config_file_without the directory. No, "command not found" is being reported by the shell that runs mongrel_cluster_ctl from /etc/init.d/mongrel_cluster. You need get mongrel_rails into its PATH. Try something like: ln -s `find /usr/local -type f -name mongrel_rails 2>/dev/null | head -1` /usr/local/bin > It should say: > > mongrel_rails cluster::start -c /etc/mongrel_cluster/sonar_radiant.yml The path to the config file doesn't need to be fully qualified. mongrel_cluster_ctl changes to CONF_DIR before executing the mongrel_railses. -Drew From kraemer at webit.de Mon Aug 21 16:20:26 2006 From: kraemer at webit.de (Jens Kraemer) Date: Mon, 21 Aug 2006 22:20:26 +0200 Subject: [Mongrel] http parser In-Reply-To: <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> Message-ID: <20060821202026.GA22036@cordoba.webit.de> Hi, regarding the 'monorail' name: I remember having investigated the castle project 10 months ago or so. I still have this download lying around: 2005-09-27 12:01 downloads/Castle.MonoRail.beta-4.zip so it seems the castle guis claimed that name somewhat earlier... Jens On Sun, Aug 20, 2006 at 07:49:30PM -0400, Francis Cianfrocca wrote: > On 8/20/06, Zed Shaw wrote: [..] > > * monorail -- http://rubyforge.org/projects/monorail/ > >* monorail -- http://www.castleproject.org/index.php/MonoRail > >* Which is really similar to "mongrel rails", but let's just say that > >wasn't your intention. > > "Monorail" was picked out of the air by a guy who works for me as we were > thinking about a lighter-weight version of Rails. [..] > In regard to the > Castle guys, we became aware a couple of weeks ago that they were using > "Monorail," and we're still looking into whether we have priority over the > name (our first pub was last April, and theirs is a recent name change). If > it turns out theirs was published before ours, we'll change ours. [..] -- webit! Gesellschaft f?r neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Kr?mer kraemer at webit.de Schnorrstra?e 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 From garbagecat10 at gmail.com Mon Aug 21 16:46:10 2006 From: garbagecat10 at gmail.com (Francis Cianfrocca) Date: Mon, 21 Aug 2006 16:46:10 -0400 Subject: [Mongrel] http parser In-Reply-To: <20060821202026.GA22036@cordoba.webit.de> References: <1f060c4c0608200250l12030574q426e070b64aa6dfa@mail.gmail.com> <1156104507.6252.16.camel@localhost.localdomain> <3a94cf510608201404h2f020bc2rfc70159fc7f8d310@mail.gmail.com> <1156113131.7991.50.camel@localhost.localdomain> <3a94cf510608201649q19cbc55gdd680e59b744fe2c@mail.gmail.com> <20060821202026.GA22036@cordoba.webit.de> Message-ID: <3a94cf510608211346uc112b17l26c83eef2c824b94@mail.gmail.com> On 8/21/06, Jens Kraemer wrote: > Hi, > > regarding the 'monorail' name: I remember having investigated the castle > project 10 months ago or so. I still have this download lying around: > > 2005-09-27 12:01 downloads/Castle.MonoRail.beta-4.zip > > so it seems the castle guis claimed that name somewhat earlier... > > Jens Thanks, Jens, I appreciate you running that down. If that information checks out, we'll change the name of our project. From nick.snels at gmail.com Tue Aug 22 05:58:51 2006 From: nick.snels at gmail.com (Nick Snels) Date: Tue, 22 Aug 2006 11:58:51 +0200 Subject: [Mongrel] Problem getting Mongrel to start at startup Message-ID: <857ffc970608220258k6fd18e57vb5e462f12f2ea919@mail.gmail.com> Hi, I'm running CentOS 4.3 and the latest Mongrel (0.3.13.3) and mongrel_cluster (0.2.0). I have set up a cluster, following the instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I created a symbolic link in the directory /etc/mongrel_cluster . When I run mongrel_rails cluster::start -c test.yml, the mongrel servers start up. But at boot, the command '/sbin/service mongrel_cluster start' gets run, when I run it I get the error: Starting all mongrel_clusters... /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27: command not found: mongrel_rails cluster::start -c test.yml mongrel_rails cluster::start returned an error. I have tried many things, but nothing works. I hope somebody can help me out. Thanks. Kind regards, Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060822/37b9a021/attachment-0001.html From nick.snels at gmail.com Tue Aug 22 06:56:00 2006 From: nick.snels at gmail.com (Nick Snels) Date: Tue, 22 Aug 2006 12:56:00 +0200 Subject: [Mongrel] Problem getting Mongrel to start at startup In-Reply-To: <857ffc970608220258k6fd18e57vb5e462f12f2ea919@mail.gmail.com> References: <857ffc970608220258k6fd18e57vb5e462f12f2ea919@mail.gmail.com> Message-ID: <857ffc970608220356i7e95b48cld29372350de90c13@mail.gmail.com> Hi, I found the problem. I had ruby installed from source and it ended up in /usr/local/bin, so I had to create the following extra symbolic links to get it working. ln -s /usr/local/bin/ruby /usr/bin/ruby ln -s /usr/local/bin/mongrel_cluster_ctl /usr/bin/mongrel_cluster_ctl ln -s /usr/local/bin/mongrel_rails /usr/bin/mongrel_rails Kind regards, Nick On 8/22/06, Nick Snels wrote: > > Hi, > > I'm running CentOS 4.3 and the latest Mongrel (0.3.13.3) and > mongrel_cluster (0.2.0). I have set up a cluster, following the > instructions at http://mongrel.rubyforge.org/docs/mongrel_cluster.html . I > created a symbolic link in the directory /etc/mongrel_cluster . When I run > mongrel_rails cluster::start -c test.yml, the mongrel servers start up. > But at boot, the command '/sbin/service mongrel_cluster start' gets run, > when I run it I get the error: > > Starting all mongrel_clusters... > /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27: command > not found: mongrel_rails cluster::start -c test.yml > mongrel_rails cluster::start returned an error. > > I have tried many things, but nothing works. I hope somebody can help me > out. Thanks. > > Kind regards, > > Nick > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060822/9910c456/attachment.html From jay.turpin at gmail.com Tue Aug 22 09:05:02 2006 From: jay.turpin at gmail.com (Jay Turpin) Date: Tue, 22 Aug 2006 06:05:02 -0700 Subject: [Mongrel] Mongrel and Service behave differently Message-ID: <4eda9d210608220605k37d89abcid4a2fcdd15a7e49b@mail.gmail.com> I have a rails application running under the latest version of Mogrel Win32. Seems to run just fine. However, when I attempt to run it under the Win32 Mongrel service, it appears to hand after hitting certain controller actions. I'm sure there is a bug in my code that's causing this - but I just am not sure what it is yet. Is there anything about the mongrel-service that would cause an application to behave differently? Besides the -B option to turn on debugging, are there any other tricks for me to get visibility to what is going on underneath the covers? If I can't track down this issue, is there any to using mongrel_rails from a scheduler instead of the service? Thanks! -- -- Jay Turpin "One test is worth a thousand expert opinions." - Bill Nye (The Science Guy) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060822/8be429b2/attachment.html From hax at cheaphacks.info Tue Aug 22 11:47:30 2006 From: hax at cheaphacks.info (hax) Date: Tue, 22 Aug 2006 11:47:30 -0400 Subject: [Mongrel] Multiple mongrels for one app Message-ID: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> Hi mongrel-users, This is my first post, so I'm not sure if it's been asked before, but I can't find an answer anywhere. If I have one rails application running, one processor I'm running it on, and mongrel is multi-threaded, why should I have more than one mongrel running? Everyone seems to agree on 3-5 mongrels per rails app, but why? I must be missing something, sorry if it's obvious. TIA --hax From jarkko at jlaine.net Tue Aug 22 12:01:39 2006 From: jarkko at jlaine.net (Jarkko Laine) Date: Tue, 22 Aug 2006 19:01:39 +0300 Subject: [Mongrel] Multiple mongrels for one app In-Reply-To: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> References: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> Message-ID: <724A8D0F-91A4-4D83-A391-FD82DA5C26BD@jlaine.net> On 22.8.2006, at 18.47, hax wrote: > Hi mongrel-users, > > This is my first post, so I'm not sure if it's been asked before, but > I can't find an answer anywhere. > > If I have one rails application running, one processor I'm running it > on, and mongrel is multi-threaded, why should I have more than one > mongrel running? > > Everyone seems to agree on 3-5 mongrels per rails app, but why? Rails is not threadsafe. http://rubyforge.org/pipermail/mongrel-users/2006-August/000930.html //jarkko -- Jarkko Laine http://jlaine.net http://odesign.fi From mongrel at philip.pjkh.com Tue Aug 22 12:31:21 2006 From: mongrel at philip.pjkh.com (Philip Hallstrom) Date: Tue, 22 Aug 2006 11:31:21 -0500 (CDT) Subject: [Mongrel] Multiple mongrels for one app In-Reply-To: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> References: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> Message-ID: <20060822112934.H19989@bravo.pjkh.com> > This is my first post, so I'm not sure if it's been asked before, but > I can't find an answer anywhere. > > If I have one rails application running, one processor I'm running it > on, and mongrel is multi-threaded, why should I have more than one > mongrel running? > > Everyone seems to agree on 3-5 mongrels per rails app, but why? Performance... somewhere Zed has an article on how to benchmark things.. something along the lines of benchmark a blank static html page. That's as fast as your server will go. Then create a simple action that renders "Hello" as text say, with one mongrel. Benchmark that. Keep increasing the number of mongrels until you don't get any more performance improvements. For us, it was 4. -philip From defeated2k4 at gmail.com Tue Aug 22 14:05:58 2006 From: defeated2k4 at gmail.com (Ed C.) Date: Tue, 22 Aug 2006 14:05:58 -0400 Subject: [Mongrel] IIS and response timeout In-Reply-To: <4eda9d210608190718y207f3be8o70e00bbf41293eff@mail.gmail.com> References: <4eda9d210608190718y207f3be8o70e00bbf41293eff@mail.gmail.com> Message-ID: <736593a0608221105o43787c58u270f0d28860560cf@mail.gmail.com> Are you using SQL Server? I think the connection times-out after 30s, so you're probably seeing a SQL Timeout error. On 8/19/06, Jay Turpin wrote: > I apologize if this has been covered before, I checked the archives and > didn't see anything over the last few months. > > I am running IIS6 with IsapiRewriter and a single mongrel service for each > Rails application. One of my apps does a long query to the database to > produce a CSV file. After the request has gone beyond 30 seconds, the user > get a 500 Internal Server Error. > > I've looked around for ways to adjust the response timeout, either in IIS or > mongrel, but haven't found anything yet. Any ideas? > > -- > -- Jay Turpin > "One test is worth a thousand expert opinions." - Bill Nye (The Science Guy) > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > > From hax at cheaphacks.info Tue Aug 22 15:11:16 2006 From: hax at cheaphacks.info (hax) Date: Tue, 22 Aug 2006 15:11:16 -0400 Subject: [Mongrel] Multiple mongrels for one app In-Reply-To: <724A8D0F-91A4-4D83-A391-FD82DA5C26BD@jlaine.net> References: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> <724A8D0F-91A4-4D83-A391-FD82DA5C26BD@jlaine.net> Message-ID: > Rails is not threadsafe. > > http://rubyforge.org/pipermail/mongrel-users/2006-August/000930.html > > //jarkko So what happens when the mongrel gets more than one request at a time? When I run httpref against it, the mongrel process can serve up large number of rails pages before it gets bogged down. And when it does break, it says "mongrel timed out this thread: too many open files". So it must be doing some threading, even if rails isn't threadsafe. If it was 1 request per mongrel process, 1 process shouldn't be able to serve up very many per second. httpref tells me its prettty fast though. Thoughts? --hax From snacktime at gmail.com Tue Aug 22 15:29:38 2006 From: snacktime at gmail.com (snacktime) Date: Tue, 22 Aug 2006 12:29:38 -0700 Subject: [Mongrel] Multiple mongrels for one app In-Reply-To: References: <6E290A95-7FD9-4251-9495-18986FF39F79@cheaphacks.info> <724A8D0F-91A4-4D83-A391-FD82DA5C26BD@jlaine.net>