similar to: can''t seem to activate the ''-d'' option..

Hi all, i im using Capistrano2 to deploy my rails app and Apache/Mongrel as it''s env. All is well except deploy:rollback task. the following is log messages when running cap deploy:rollback : [DEPRECATION] Capistrano.configuration is deprecated. Use Capistrano:: Configuration.instance instead * executing `deploy:rollback'' * executing `deploy:rollback_code'' *

Hello, I am new to Rails and the Linux world coming from 12 years of advanced VB programming. I am writing to try and clear up some confusion on my part about installing Mongrel. Please don''t take this as a rant, I do appreciate the effort that y''all put into the community, but as a newbie, I was, and still am confused. I want to learn about Mongrel, so it found

Hi, I just did a clean install of Ruby 1.8.5 Rubygems 0.9.0 and the Mongrel and Mongrel_Cluster gems. I used only the Debian Etch package manager, nothing compiled myself. Now, on a testapp when I do a script/server, I get the: ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix warning. But it''s not serving my app. Ruby is immediately on 100% CPU load (and 0.7%

I''ve noticed that the copy of Mongrel installed by the camping-omnibus gem doesn''t work with Ruby 1.8.6. Or to be more specific, cgi_multipart_eof_fix (which Mongrel is dependent upon) doesn''t work: > $ sudo gem install mongrel --source http://code.whytheluckystiff.net > > ERROR: Error installing mongrel: > cgi_multipart_eof_fix requires Ruby version

I''m playing with the mongrel clustering, and am having a problem getting 2 mongrels to start up reliably. This should be a pretty simple cluster, with just 2 instances running. My mongrel config (mongrel_cluster.yml) looks like: cwd: /deployment/installed/myapp/current log_file: log/mongrel.log port: "8000" environment: production address: 127.0.0.1 pid_file:

Hello, I''ve install ror/mongrel etc, etc on a linux server (rhes). As i''m not root, all package startinf from ruby have been install into ~/gconf/usr ruby-1.8.6 and all of this gem package: -r-xr--r-- 1 dimnce dba 168448 Aug 9 14:53 rails-1.2.3.gem -r-xr--r-- 1 dimnce dba 84480 Aug 9 14:56 rake-0.7.3.gem -r-xr--r-- 1 dimnce dba 217088

Hello Everyone, Been head down with personal stuff, but I wanted to shoot out this email saying that I''ve collected the list of volunteers and decided that I''d just hand the keys over to them and see how they do. The list of people I have so far is: Ezra Zygmuntowicz <ezmobius at gmail.com> "Kirk Haines" <wyhaines at gmail.com> "Wayne E. Seguin"

hello all, i have been trying to figure this out for the last few hours, and after seemingly exhausting all the google search results, i figured i would try this mailing list... i just updated the ruby version on my ubuntu dapper drake box to the most recent version. i installed it into /usr/local/bin problematically, the previous installation was in /usr/bin mongrel still complains that:

Hi, I''m having difficulties getting mongrel running on my Debian Etch machine. It seems to install and is listed with my other gems, but things like... "mongrel_rails start ..." ... are not recognised. Perhaps this is something to do with the file "lib" not being found in the install process: ruby extconf.rb install mongrel --include-dependencies checking for main()

Hopefully that gets everyone''s attention. Evan Weaver has whined enough to make me do a release to change the requirements on the Mongrel gem so that it doesn''t need the cgi_multipart_eof_fix anymore. *************************** THIS ALSO MEANS THAT MONGREL WILL HAVE TO REQUIRE RUBY 1.8.6 OR GREATER! NO EXCEPTIONS! *************************** I know Debian guys like to hack

I just created a test rails app, and am having very wierd issues with mongrel cluster. Here''s what I''m doing: rails test sudo chown -R mongrel:mongrel test cd test sudo mongrel_rails \ cluster::configure -e production \ -p 8000 -N 3 -a 127.0.0.1 --user mongrel \ --group mongrel It correctly writes the mongrel_cluster.yml file to the config directory. Now,

Hi Guys, I?m getting this error with mongrel_cluster. I am able to start mongrel through mongrel_rails start but the cluster is not working. Initially mongrel_rails wouldn?t work but after I added $ORACLE_HOME and $PD_LIBRARY_PATH variables it worked but mongrel_cluster isn?t working still. The mongrel log file looks like below. Any help is appreciated. Thanks. -----------begin

It''s time again for your monthly cgi.rb DOS vulnerability. This latest vulnerability is different from the one that cgi_multipart_eof_fix.gem fixed. This one is related to the boundary taken from the web client being used incorrectly. You can read about the vulnerability: http://www.ruby-lang.org/en/news/2006/12/04/another-dos-vulnerability-in-cgi-library The applicable PATCH is

Hi, I made an interesting observation using webservers (not just mongrel) under red hat enterprise linux ES release 4 (Nahant Update 5). Maybe this is helpful or somebody with deeper networking expertise can comment on this. Once client said that 1-2% of the response of our server were unacceptably slow (really huge 3s-21s). So I did more ab and httperf tests and notice that very few

Hello, I''m trying to deploy my application with Capistrano using Mongrel recipes. Since I''ve installed Ruby from source code, mongrel scripts are found in /usr/local/bin. But the recipes can''t find mongrel_rails : "bash: mongrel_rails: command not found". The path of the user account used to deploy is OK. For sure, I can redefine

I''m trying to get a rails app running with this configuration: Mongrel, Apache 2.2, mod_proxy load balancer and Rails 1.1.6 error I have a rails app on another server working with (apparantly) the same configuration and it runs fine so I''m stumped. I''m wondering if anyone has any insight into the error I have pasted below. It seems to be one of those errors that

Hey folks. Sorry for the SUPER long email but if you''ve been experiencing the same problems with restarting your mongrel cluster with Capistrano, then I have two solutions that have worked for me and I''m pretty sure will for you as well. THE PROBLEM I was having trouble restarting my clusters using Capistrano. I''ve seen this come up before on the mailing list and

Hi I posted this to the Ruby on Rails Talk group but I thought I''d post it here too as it''s probably a more appropriate group. Hope this is ok. 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

This might just have affected my particular setup but thought it might be worth noting for others. >gem -v 0.9.2 >gem list --local cgi_multipart_eof_fix (1.0.0) Fix an exploitable bug in CGI multipart parsing which affects Ruby <= 1.8.5. mongrel (1.0.1, 1.0, 0.3.20, 0.3.18, 0.3.13.4) A small fast HTTP library and server that runs Rails, Camping, Nitro and Iowa apps.

Hi all, Forgive me if this has been asked before, but is there a reason mongrel_rails cluster::restart stops all ports and then restarts them again? Wouldn''t it be better to restart each port one-by-one in series so that upstream proxy servers can fail over while the restart is occurring, or am I missing something? Thanks, eden