similar to: Issues with mongrel PID files when restarting clusters with Capistrano

Hi, I am deploying a Rails website using Capistrano to a VPS running the site through Apache and Mongrel. ''cap deploy'' works fine, and mongrels are restarted. When I execute ''cap deploy:rollback'', however, my script fails to restart the mongrels giving this error: !!! PID file tmp/pids/mongrel.5000.pid already exists. Mongrel could be running already.

Hi all, I am out of my head here... I have a 3 node cluster with 10 mongrels running on each. When I deploy, I break all the mongrels every time. I have tried just about everything. I can restart my mongrels without a hitch manually, it''s only when I use cap deploy. Maybe I am missing something here... so if I can get some help it would be appreciated. The errors are the typical mongrel

Hello, I am trying to deploy on to OS X Server with capistrano+mongrel+apache2, etc. I''m trying to do a "cap cold_deploy" as recommended here: http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you/ I had a devil of a time getting cap to find the mongrel_rails command (which is in /opt/local/bin) on the server. I set the

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

Hi, I''m calling restart from my Capistrano task. I have this in my deploy.rb file: # until mongrel_cluster updates to cap2... namespace :deploy do task :start, :roles => :app do start_mongrel_cluster end task :stop, :roles => :app do stop_mongrel_cluster end task :restart, :roles => :app do restart_mongrel_cluster end end (What''s the scoop on

I''ve done a clean install of Ubuntu 7.04 server in 2 different machines and everytime I reboot the machine or manually run /etc/ init.d/mongrel_cluster restart/start the mongrels won''t start correctly. I have to manually start them by using mongrel_rails cluster::start from each app folder. I''ve been searching around and it looks like mongrel has some problems

Hi, I have an application which is dying horrible deaths (i.e. segmentation faults) in mid-flight, in production... And of course, I should fix it. But while I find and fix the bugs, I found something I think should be different - I can work on submitting a patch, as it is quite simple, but I might be losing something on my rationale. When Mongrel segfaults, it does not -obviously- get to clean

Hi all: New to the list. Im enjoying mongrel. Coming from a background of weblogic clusters this is a dream. However I have a few questions: I have used HTTPerf to analyze metrics for an application ( rails ). My question pertains to the CPU utilization threshold: 1) Test with single mongrel server : sustained cpu util @ 98% 2) Test with 2 mongrel nodes in a mongrel cluster with apache and

I transferred a site from Lighty+SCGI to Lighty+Mongrel, and now I''m having problems with it becoming unresponsive. It works fine for about 10-15 minutes, but then attempts to access the site just stall forever. Nothing is written in any of lighty''s or mongrel''s logs. Here''s my lighty config: $HTTP["host"] =~ "www.xyz.com" {

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:

Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,

I''m wondering if anyone has built a Capistrano task that will deploy mongrel either standalone or along with a rails app. I''ve been looking at possibilities for doing this but still new to using both having switched from using FCGI+Lighty and deploying by hand. Thanks, Curtis

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

Hello all... I know its been a while since the last one, but a new prerelease is available with a gratuitous increase in version numbers! gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ This one has some new features in it that need to be tested on all unix platforms. Please run --clean and cluster::status on every *nix you can find. I run linux so the rest are up

Hello. I recently deployed my new rails application. Everything went fine, except for the fast that my mongrel cluster managed by Capistrano is only serving up the first revision. For instance, i one of my revisions I added a new action to my application. I checked it into svn, and ran cap deploy in my application''s root directory. I didn''t get any serious errors, except for

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

If this was in the docs, I''ve missed it. How can I have multiple mongrel clusters on a server? All the documentation that I am seeing seems to assume that I am only running one cluster.

Hi There, I''ve got a mongrel cluster running on redhat 9 proxied behind an Apache 2.2 installation. I have run into a real stumbling block in that, while the rails app runs in production mode (you get a production.log file, for example, and I see this in the mongrel log: ** Starting Rails with production environment ... ), it always loads the development database configuration

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

Hi. Have anyone figured out a simple restart task for mongrel using Capistrano? Br. Morten