similar to: Getting Started without Rails

Hi everybody, I have installed mongrel and mongrel cluster in a new linux box .... at the end of the day I was able to lunch mongrel (mongrel_rails start -e production) and all is working fine with. However, when I tried to set a mongrel cluster the command mongrel_rails cluster::start get the following output : starting port 8000 starting port 8001 starting port 8002 But when I lunched the

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,

I am having different results between when I start mongrel with script/ server and with mongrel_rails start. When I run script/server to boot mongrel everything runs fine, no errors. When I run mongrel_rails start I get the following errors - verified the problem on a fresh app and on two different environments (mac and yes, windows server 2008). The actual line of fault changes but the problem

Hi, I am a Newbie to Mac and Rails. I have a rails apps made using instantrails in windows, and have been trying to transfer it to a mac. I am using Leopard and installed mac ports and Xcode. I copied the folder from rails_apps and added all the gems. Anything else I need to do? Any Ideas? Thank you! This is the set of errors that I am getting after starting the server: Exiting

I assume some of you have run into this error before when trying to run mongrel on port 80 (or another port < 1024) in OSX: $ mongrel_rails start -p 80 ** Starting Mongrel listening at 0.0.0.0:80 /usr/local/lib/ruby/gems/1.8/gems/mongrel-0.3.14/lib/mongrel/tcphack.rb:12:in `initialize_without_backlog'': Permission denied - bind(2) (Errno::EACCES) from

** 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 am followint this article, http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ ...but I keep getting this error in the log...not sure what to try next... ** Daemonized, any open files are closed. Look at log/mongrel.8000.pid and log/mongrel.log for info. ** Starting Mongrel listening at 127.0.0.1:8000

On Thu, Jun 25, 2009 at 2:07 AM, Michael Pliskin<mike at comapping.com> wrote: > Hi all, > > > > Some disclaimer first: I am a complete newbie in mongrel and this list, so > please forgive me if I say something weird. I have a problem, I?ve googled > for a solution for quite a while and failed so far, so decided to ask here. > > > > I am trying to set up my

Hello world, I''m having some problems setting up a new Debian deployment box...just installed the rails stack, mongrel, etc... When I go to start mongrel I''m getting a weird error I can''t figure out. Some help please? -> mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000

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)

I''m trying to run mongrel on port 80 and switch to a different user/group from root. As root, this works: mongrel_rails start -p 3000 -u rails --group rails This: mongrel_rails start -p 80 -u rails --group rails dies with: --------------------------- ** Changing group to rails. ** Changing user to rails. ** Starting Mongrel listening at 0.0.0.0:80

Hi Today I got an alert mail from my watcher script, telling me that there was no Mongrel running, and that it started one (so the site was down for a few seconds.) This is the first time I got this error (AFAICS), but I''d like to resolve and prevent it for the future. From mongrel.log: ** Starting Mongrel listening at 0.0.0.0:foo ** Starting Rails with production environment... **

Good morning all, I''ve been using the imap_authenticatable plugin for about a year now without incident. All of a sudden, I tried logging in this morning and this error is showing up in the logs. Does anyone have any idea what could be causing this or how to fix it? Thanks, Pete NoMethodError (undefined method `disconnect'' for nil:NilClass):

I''m working on upgrading to rails 1.2.2 from 1.1.6 and getting the mongrel error below in development mode. Now things seem to work fine with 1.1.6and 1.2.2 (in prod mode). Any ideas what might cause this? Googling gave me very little to work with. This was the closest thing i found http://dev.rubyonrails.org/ticket/6716 I''m running Ubuntu with mongrel 1.0.1 and fastthread

Hi, I am newbie started learning ruby on rails i had an application which used to run pretty well latter i upgraded from webbrick to mongrel 1.1.5 then I am getting the foloowing errors and a default application runs on port 3000 i have attached its screen shot as an attachement and error which i get in terminal below => Booting Mongrel (use ''script/server webrick'' to force

Thanks Bill for the answer ! In fact, my application is working well with webrick and also with a single mongrel instance lunched via the command : mongrel_rails start When I check what is the difference in the gem loaded in both cases (mongrel_rails start and mongrel_rails cluster::start) it seems that mongrel_rails cluster::start does not load all the gems that the first command is loading. So

I was wondering if anyone here has seen a similar error to this... >From mongrel.log /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/ transactions.rb:85:in `transaction'': Transaction aborted (ActiveRecord::Transactions::TransactionError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/ configurator.rb:293:in `call'' from

I was hoping that someone can help me with this, which have been driving me nuts -- I have had my mongrel cluster dying daily. And yes, I have gone through the check list of possible causes: I don''t do log rotating I use active_record for session storage I don''t use SQLite and Berkeley DB The MySQL timeout is set to 3600 I am using only 10% of the memory. I am using RedHat

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

Hi am a newbie to mongrel. am using mongrel cluster in my ruby application. When i start mongrel cluster it is working fine and when i stop it it says already stopped port 8000. it is giving the error as follows ********* simple selection ********* ********* selection by list ********* -A all processes -C by command name -N negate selection -G by real