similar to: Serious bug in routing ?

Hi, I can''t install Mongrel on Ruby 1.8.6 (patchlevel 279), using Windows XP. My environment: C:\ruby18>gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-07-17 patchlevel 279) [i386-mingw32] - INSTALLATION DIRECTORY: c:/ruby18/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby18/bin/ruby.exe - EXECUTABLE DIRECTORY: c:/ruby18/bin -

I''m running two sets of mongrels using mongrel 1.1.4, one for production one for staging. When executing ''ps'' from a linux shell, the production mongrels report as expected, however the staging processes are listed as [ruby 18]. The result seems to be that mongrel_rails cannot stop the staging processes because it doesn''t recognize [ruby18] as a mongrel

Hello... I am trying to switch to mongrel from webrick to get rid of the . puppetmaster is FreeBSD 6.2 with ruby, puppet, and mongrel all from ports (latest as of this morning). I get "Server is not a class". --verbose, --debug do not spit out any useful info. puppet-0.22.4 ruby-1.8.6.111_1,1 ruby18-bdb46-0.6.2 ruby18-gems-0.9.4 rubygem-daemons-1.0.8 rubygem-fastthread-1.0

A small note to all the FreeBSD folks about Ruby performance. While trying to tune Mongrel to run faster on FreeBSD I was stumped as to why it was so horribly slow compared to Linux. Linux on the same machine was getting about 800 req/sec, and FreeBSD was maybe pushing 23 req/sec. Pathetic. I managed to tweak the thread model in Mongrel and get FreeBSD up to about 210 req/sec but still that

I know this has been brought up before but I''m receiving the error ... Process environment requires procfs(5) ... when trying to restart my cluster. I''ve narrowed it down to ''find_pid'' method in init.rb. I''m running a FreeBSD 6.2 server and mongrel_cluster version 1.0.5. The command that gives me the error is ... ps -ewwo pid,command ... but

Hi! I''m observing some problems using gem inside Rails. My understanding is that after following sequence in irb: $ irb irb(main):001:0> require ''rubygems'' => true irb(main):002:0> require ''active_record'' => true irb(main):003:0> gem ''acts_as_taggable'' => true I should have access to acts_as_tagable mixins, like:

Hello Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

I''ve been troubleshooting this problem for several hours now and haven''t been able to figure out what''s wrong. I have two boxes, dev and prod, both are identical except that prod uses Ruby 1.8.5 and dev uses 1.8.4. Both are running Slave 1.2.0, Daemons 1.0.5, and Backroundrb 0.2.1. The behavior I''m seeing is this. When I first start Backgroundrb, this is what

=> Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails application starting on http://0.0.0.0:1337 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:1337 ** Starting Rails with development environment... Exiting /opt/local/lib/ruby/gems/1.8/gems/rails-1.2.3/lib/commands/servers/ mongrel.rb:15: warning:

Thank you very much Luis. After re-installing Mongrel and related gems and selecting "Ruby" rather than "win32", mongrel appears to be working fine! > Date: Fri, 20 Apr 2007 23:30:14 -0300 > From: "Luis Lavena" <luislavena at gmail.com> > > Hi Randy, > > It seems you''re using ruby from cygwin, and not mswin32 (wich is > one-click

hi all, i am new to ROR,I have one ROR app developed in old version i upgrade it with following version: RubyGems Environment: - RUBYGEMS VERSION: 1.3.2 - RUBY VERSION: 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] - INSTALLATION DIRECTORY: D:/Ruby/lib/ruby/gems/1.8 - RUBY EXECUTABLE: D:/Ruby/bin/ruby.exe - EXECUTABLE DIRECTORY: D:/Ruby/bin - RUBYGEMS PLATFORMS: - ruby -

I''m running FreeBSD 6.1 and installed the 1.0.1.1 mongrel_cluster prerelease. I had a problem with the mongrels not stopping, and it turns out it''s because ps is reporting my processes as just [ruby18] instead of someting more like "mongrel_rails start -d ......." Not sure why it''s doing that, but it is. Any ideas? For the time being I just changed line

** Daemonized, any open files are closed. Look at /var/www/vhosts/ gophotoswap.com/httpdocs/shared/pids/mongrel.8000.pid and /var/www/ vhosts/gophotoswap.com/httpdocs/shared/log/mongrel.8000.log for info. ** Starting Mongrel listening at 127.0.0.1:8000 ** Initiating groups for "mongrel":"mongrel". ** Changing group to "mongrel". ** Changing user to

I''ve having issues with some part of Mongrel start up process stalling with versions of Mongrel greater than 1.1 Using Mongrel Gem version 1.1 both ./script/server and ./merb boot fine But from gem version 1.1.1 both processes stall immediately I can get it to continue by attempting to force quit with CTRL -C system info Mac OS X 10.5.5 Ruby 1.8.7 (2008-05-31 patchlevel 0)

Like most people, I''ve got two machines: one for development and one for production. I''ve done everything I can to make sure the ruby/rails environments are the same, but of course they''re not identical (I''ll get into that in a moment). The error that I''m getting happens when I call a method in a background task controller on the production machine; I

Hi Is there some definitive guide for upload progress plugin ? We have in this mailing list a lot of testimonials, bug reports, bug fixes, but there are still people like me who cannot use it correctly. Here is my config: - mongrel 1.0RC and upload progress plugin 0.2.1 - a 6 mongrels cluster - config/mongrel_upload_progress.conf: uri "/", :handler =>

Hi I''m running a 2-instance Mongrel cluster behind Apache 2.2.4 with Rails 1.2.3. If no requests are received by the application for several hours (this usually happens overnight) then Mongrel stops responding and no requests are detected by Rails (at least nothing is in the Rails log). Nothing untoward is in the Mongrel log. If you try and visit the application, the request times out

Hello. I''m trying to use the ''acts_as_ferret'' gem with Rails. Rails: 1.1.4 and 1.2.3 OS: WinXP I''ve installed both Ferret and the plugin using Ruby Gems: C:\>gem install ferret Successfully installed ferret-0.11.4-mswin32 Installing ri documentation for ferret-0.11.4-mswin32... Installing RDoc documentation for ferret-0.11.4-mswin32... C:\>gem install

I''m new to Rails and Mongrel and I''m trying to get mongrel running for the first time. I''m running Rails 1.2.3 under Cygwin on Windows Server 2003 (SP1) with Apache 2.0. The Rails apps works fine when proxied through Apache and running under WebRick, but Mongrel seems unhappy about something. The Apache service is running as the "Local System" user

Howdy, I''m trying to debug a situation where a Rails app running on Mongrel +Apache stops listening to requests. Restarting Mongrel and Apache brings it back to life. First off, here''s some info on versions, etc...: Red Hat Enterprise Linux ES release 3 (Taroon Update 8) ruby 1.8.5 (2006-12-04 patchlevel 2) [x86_64-linux] Mongrel 1.0.1 Rails 1.2.1 fastthread (0.6.2)