similar to: mongrel_rails cluster::start problem with multiple runs?

Is there anything mongrel cluster gives you that monit doesn''t? I''ll be using monit to monitor a number of other services anyways, so it seems logical to just use it for everything including mongrel. Chris

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel

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

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

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

Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a

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, 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 am having trouble getting rake vlad:start to work.. here is the output: ivan:04:39 PM:www2.sustainablewebsites.com> rake vlad:start (in /Users/ivan/Sites/www2.sustainablewebsites.com) !!! PID file log/mongrel.8000.pid does not exist. Not running? mongrel::stop reported an error. Use mongrel_rails mongrel::stop -h to get help. !!! PID file log/mongrel.8001.pid does not exist. Not running?

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

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

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

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: new_notes Type: application/octet-stream Size: 5801 bytes Desc: not available Url : http://wrath.rubyonrails.org/pipermail/rails/attachments/20060723/34e20e45/new_notes.obj

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

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

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:

Hello, I''ve install ror/mongrel etc, etc on a linux server (rhes). As i''m not root, all package startinf from ruby have been install into ~/gconf/usr ruby-1.8.6 and all of this gem package: -r-xr--r-- 1 dimnce dba 168448 Aug 9 14:53 rails-1.2.3.gem -r-xr--r-- 1 dimnce dba 84480 Aug 9 14:56 rake-0.7.3.gem -r-xr--r-- 1 dimnce dba 217088

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

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