similar to: OSX requires sudo for using ports < 1024

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

Time for some all time pimpage folks. Me and Matt Pelletier wrote a small PDF book on Mongrel entitled: "Mongrel: Serving, Deploying, and Extending Your Ruby Applications" since we really wanted you to know what it was about. It''s published by Addison Wesley Professional, has just over 100 pages of goodness, and is available for $14.99 at: http://safari.oreilly.com/0321483502

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

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 I have a rather strange problem with mongrel and I would be grateful if anyone could assist me with resolving. I have an application running mongrel 1.1.1 and rails 1.2.5 with ruby 1.8.6. It was all working fine and starting as expected. But I did a server reboot once and mongrel has refused to start up since. I get the following error:

Hello, I don''t know if this is really relevant anymore because a new version is about to be released it seems, however I''ve been trying to run mongrel 0.3.12.4 on a development server in development mode (simply with mongrel_rails start). I try to access the server and the first page (static file) loads, but then the server dies and I get this in the logs. I''m

Howdy, I''m getting an error message when trying to run one of my rails apps, which seems to have started after updating to 10.5.3. mattdaw-2:v1.5_patch mdaw$ mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../ lib/mongrel/tcphack.rb:12:in

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 by name iphone configuration utility i am unable to attach the screen shot as it is saying file to large. Error which i get in terminal is listed below => Booting

Zed, I purchased your book and was reading through it. On page 25 it states: "Mongrel will give precedence to the parameter values in the config file over those in the command line." I was wondering why this is not the other way around, preference given to the command line options. Thanks, ~Wayne

I try to config XLSUITE in my system. I''m facing some problem i resolved it one by one. now im facing this error => Booting Mongrel (use ''script/server webrick'' to force WEBrick) => Rails 2.2.0 application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 Exiting

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

Hi, everyone. I am in the process of learning Ruby. I''ve concluded that there are couple of quirks with mod_ruby that are limiting me a fair bit, so I''m looking for an alternative. From what I''ve read, Mongrel is The Answer. However, this has left me with a few questions. I''m looking for some help getting a non-rails Mongrel started... I can''t

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

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

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 All, I''ve been running into quite a few people who''ve claimed that they have Apache (or lighttpd) serving static files, but then they paste in error messages from Mongrel that shows not only Mongrel not serving the files, but Rails is serving them. Everyone using apache should run this very simple test: 1) Setup your apache so that it point at one backend. 2) Start your

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

Hey folks, I''m working on the Mongrel book with Zed, and wanted to get some feedback from the core users (this list) about how they use Mongrel. That sounds a bit vague, but I''m interested in hearing things about frustrating problems / workaround, preferred configurations, if you have a particular way you set up / store your config files when developing / deploying an

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 made a new rails app and when i started the server ,it gave following error message. => Booting Mongrel => Rails 2.3.8 application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server Exiting /usr/lib/ruby/1.8/mongrel/tcphack.rb:12:in `initialize_without_backlog'': Address already in use - bind(2) (Errno::EADDRINUSE) from