similar to: Three processes for each mongrel server?

I''m getting the following exceptions when running mongrel_rails. Any ideas what might be causing the problem? Error details... $ mongrel_rails /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.3/lib/mongrel/command.rb:168:in `run'': When creating '''': undefined method `downcase'' for nil:NilClass (NoMethodError) from

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,

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

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, I am working on deplying my Rail app to QA and then move to production. Since on our QA servers, there is no internet access and also for production servers, internet access is strictly prohibited. As a result, there is no way to install mongrel by use "gem install mongrel" command. The first option I tried is to put mongrel and all other gems under the vendor directly in my app,

Sorry for the newbie question but I''m stumped: I have an app that requires sudo to run mongrel_rails. For my capistrano recipe is do it like this: sudo "mongrel_rails start -e production -p #{application_port} -d -c #{current_path}" Which works famously. Now I have tried several things for my restart task. Here they are: sudo "cd #{current_path} && sudo

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

I''m using the latest Mongrel (0.3.13.4) and restarting causes Mongrel to die. From mongrel.log: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails start -C config/mongrel.yml /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in `exec'': Operation not supported - ruby

I''m using the mongrel_cluster recipes for Capistrano as laid out by codahale.com and the new ed. of the Agile Development book, but I''m having problems on restart and stop: I can start: [root current]# mongrel_rails cluster::start Starting 3 Mongrel servers... And I can see 3 processes running: [root current]# ps aux | grep mongrel mongrel 1947 0.0 8.2 24684 10776 ?

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

Z-Man, DHH recently said: "And [_why''s] latest work on sandbox looks stellar. Making it drop-dead easy to run multiple Rails applications in the same Mongrel process without conflicts. Thumbs up to both him and Matz for getting Sandbox on track for inclusion with the next Ruby release." Does that mean what I think it means - that one or more Mongrel processes may one day be

Hello, I''ve been trying (unsuccessfully) to hack my mongrel_cluster to re-ststart in an alternating manner. Specifically, this soluiton: http://blog.carlmercier.com/2007/09/07/a-better-approach-to-restarting-a-mongrel-cluster/#content Which means I an call to mongrel_rails cluster::restart to do this: mongrel_rails start 8001 mongrel_rails stop 8001 mongrel_rails start 8002

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 everyone, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment:

Hi, I am using a railsapp to call an external app and print some barcode-labels. My problem is, after a while there seems to be a timeout. Then I need to stop the Mongrel-Server and restart it. Below you can see the error message, when i stop the server. Has somebody seen this before? Greetings, Oli C:\etikett>mongrel_rails start -d -e production ** WARNING: Win32 does not support daemon

I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use

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

Hello all, So, I''ve been using monit with mongrel for a while now, since the 0.3.x days (I think it was). It used to work fine, but now I seem to be having some trouble. I''m currently using mongrel 1.0.1 and I am using the same monit configuration I''ve always been using, yet everytime monit should restart mongrel, I get "Execution failed". For the start