similar to: killall kills god

Hi, I''m trying to use god to monitor my mongrels. When they are running everything looks OK but when a mongrel process dies and god tries to restart it I get the following error: command exited with non-zero code = 1 The weird thing is that if I try use the exact same command as god is using but on the command line then the mongrel starts back up. I''ve seen this error

Hey All, I just wanted to get other peoples take on problems when running merb in production? Just as Rails used to do, the mongrels tend to get heavy/unresponsive over time so need a good kicking by a watcher daemon like god or monit. However, I have had serious problems getting God to restart the process, as the "merb -k <port>" command doesnt appear to work reliably

I''m using god* to monitor my mongrels. God looks at pid files to know the status of the cluster. It seems as though mongrel does not write a pid file until it has loaded the entire rails/project environment, which in my case, takes upwards of 90 seconds. Meanwhile, god is freaking out because it thinks that there aren''t mongrels running, and it tries to start them. Thankfully I

When I started Rails Development, I needed to use ''killall -g dispatch.fcgi'' whenever I made a change to a Model to see the change on my website. Now it seems I need to do this to see any change to the Controller as well. Any ideas of what I am doing wrong??? -- Posted via http://www.ruby-forum.com/.

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

Hi, I am using resque, resque-scheduler gems in my rails app. To monitor the working of resque workers, I am using God tool. I want to add such a god configuration, which will monitor the time of job running in the resque worker. If process execution exceeds the time limit, then it should restart the worker. I read post at http://god.rubyforge.org/. However, couldn''t peek the right

Our Mephisto install kills Mongrels and causes Apache to pound the CPU. This started when we moved to Apache+mod_proxy_balancer+Mongrel. Here''s what we know: The following things are working OK, except when used in the combination listed above: mongrel, mongrel_rails, MySQL, Apache, mod_proxy_balancer. We believe these are all OK because we moved five other Rails apps to this

* cross posted to the mongrel mailing list* Hi, I''m running into a strange issue where one mongrel will sometimes develop hundreds of CLOSE_WAIT TCP connections, mostly to apache (I think -- see sample lsof output below). I haven''t had a chance to get the mongrel with this behavior into USR1 debug mode yet. I wrote a little loop below that will catch it next time. This

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.

I was able to run god earlier in the day, but now I get this error: # god load config/mms-service.god The server is not available (or you do not have permissions to access it) Anybody know what this error means? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

Just so you know, I''ve read the manual :) http://mongrel.rubyforge.org/docs/choosing_deployment.html No php or ssl needed - that is me - simple. So I should be good to go but thought I''d ask. BTW, sorry about the stupid subject. Listening to BNL, you know ;) On 6/27/06, mongrel-users-request at rubyforge.org <mongrel-users-request at rubyforge.org> wrote: > Send

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

Hello, Although it is off topic, but I wanted to share my idea with the group of shorewall There were greek,Egyptian,.... gods they have gods for everything I think it is our turn to make a god for the internet it is a virtual thing, but I think it is a nice idea and he/she should be the protector and so on as the internet is like the Sky /water, and fire If no one likes the idea , do not

Hi all, I''ve been having problems with the apache 2.2-mod_proxy_balancer- mongrel setup. My setup is: CentOS 4.3 apache 2.2.3 (compiled from source) with mod_proxy_balancer mysql 4.1 ruby 1.8.4 mongrel 0.3.14 (I know I need to update but I think this problem is independent of the mongrel version) mongrel_cluster 0.2.0 rails_machine 0.1.1 I have apache setup as per Coda''s

Oh well, needed a good subject, sounds funny enough? http://dev.rubyonrails.org/ticket/5475 Add "automatic" mongrel support to script/server Status: closed, commited in rev #4486. That is good news, right? Ok, back to work, enoguh relax for me ;-) -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of

Paul Did you ever get to the bottom of this. I''m having a similar (though possibly different) problem with a Rails app failing occasionally and on just one mongrel instance, which from the trace and behaviour seems to be ImageSceince/RubyInline related. See my post on Rails deployment group:

Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file

Hi, I''ve started a new project that uses Mongrel. It basically lets you defer requests to it until other Mongrels in your (Rails) pool becomes free. Rubyforge project page: http://rubyforge.org/projects/qrp/ gems, tarballs and git repo in case they haven''t hit the mirrors yet: http://bogomips.org/ruby/ I should also add that nginx 0.6.7 or later is required for 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 deploying Unicorn on a Rails application with RUnit. Technically I''m using Chef''s deployment tools, if any of you are familiar with it (https://github.com/opscode-cookbooks/application_ruby) but to be clear they aren''t doing anything magical, so this is purely an issue with RUnit and Unicorn. The TL;DR of the following post, which has lots of