similar to: mongrel_cluster 1.0.1.1 does not create /var/run/mongrel_cluster

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

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

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

Hi, Im a newbie to ruby and rails. I installed mongrel using the command: sudo gem install mongrel --include-dependencies When i try to start mongrel with mongrel_rails start -d, its throwing the same error as it did to you: /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `gem_original_require'': no such file to load -- http11 (LoadError) from

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:

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

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 ?

I''m running FreeBSD 6.1 and installed the 1.0.1.1 mongrel_cluster prerelease. I had a problem with the mongrels not stopping, and it turns out it''s because ps is reporting my processes as just [ruby18] instead of someting more like "mongrel_rails start -d ......." Not sure why it''s doing that, but it is. Any ideas? For the time being I just changed line

Hi, I''m trying to setup my mongrel clusters to start on boot. I have followed the instructions under the "On Boot Initialization Setup" section at http://mongrel.rubyforge.org/docs/mongrel_cluster.html. When I try to start it up, I get the following error: me at mybox.com: sudo /etc/init.d/mongrel_cluster start Starting all mongrel_clusters... !!! Path to log file not

Hi Y''all, Just a quick note announce an update to mongrel_cluster. Changes: - ''mongrel_rails cluster::restart'' now calls ''mongrel_rails stop'' and ''mongrel_rails start''. ''cluster::restart'' now accepts the ''force'' argument instead of ''soft''. - Added ''.conf'' as

On one of my development servers mongrel dies when idle for any length of time. Since I''ve not been able to solve that problem I thought I''d route around it by using monit to kick things when necessary. My monitrc contains the following... -------------------------------------------------------------------------------- check process mongrel_8310 with pidfile

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

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

Hello all. I''ve recently installed the 0.2.2 pre-release of mongrel_cluster to try out the new --clean option. However, after installing, when I give a simple "mongrel_rails" command, the cluster::status command is not listed. The error I receive when I do try and run the full "mongrel_rails cluster::status" is... ERROR RUNNING

Hey y''all: I''ve added some new stuff to mongrel_cluster. Give it try and let me know if it works for you. * Added ''--clean'' to cluster::start to force removal of the pidfile before trying to start the cluster member. This is useful for recovering from unexpected process death. * Added ''--only PORT'' to cluster::* to support running a

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

Hello! Run problems after upgrading to mongrel 1.0.3 from 1.0.1: # uname -sr FreeBSD 7.0-BETA1 # mongrel_rails start ** Starting Mongrel listening at :3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload

Hi there, I''m using Mongrel (0.3.13 prerelease, installed today) to serve up some Rails apps in production. Everything works fine if I give all the appropriate options on the command line, such as: $ mongrel_rails start -c /home/mcornick/rails/mcornick.org/current -P log/mongrel.pid -l log/mongrel.log -e production -d -a 127.0.0.1 -p 6833 So, having accomplished that, I thought it

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

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