similar to: Mongrel hangs, consumes all CPU on

> We see this on all of our Mac''s here as well. We''ve tried it with > different versions of Ruby (1.8.4, 1.8.5, and 18.6), and the problem > happens with all of them. > We run macs w/ compiled adaptors on local mysql instances and there are no issues. F -------------- next part -------------- An HTML attachment was scrubbed... URL:

With the latest version of Mongrel, will Mongrel reopen log files when sent a HUP signal? I would like to do a log rotate, but would prefer not to restart the mongrel instances as monit is watching after them all. monit is great for restarting the individual instances, but I would prefer not to do a restart all through monit. I would be curious if this is advisable. -- ----- Christopher

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

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

Monit 4.9, Mongrel 1.0.1, Rails 1.2.6, Mac OS X 10.4.11 (PPC) I don''t know whether this is a mongrel issue or a monit issue. I''m trying to poke my way around a system set up by someone else. I have no more experience w/ mongrel that local Rails dev at this point, and a conceptual understanding of how monit is working. I have the Deploying Rails beta book, and I''m

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

Hi! I run a mongrel cluster with 6 mongrels in it. I want to monitor them individually for process hangs (and then restart them) and this is the solution I came up with: Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program =

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

Is there any documentation I can look at that might talk about how to put memory limits on mongrel? For instants, I might want to limit mongrel to 100 megs of ram. I know that I can monitor mongrel with monit and restart it automatically if it becomes a ram piggy.

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''m doing development with Mongrel 1.0.1 on Ruby 1.8.4 / OS X 10.4.10, and I''ve found that often when I shut down my server with ^C, it hangs for a while, gobbling up all CPU. Sometimes it stops after a few seconds, sometimes it''s run for several minutes at least. This happens across all the apps I develop on, but it seems to hang longer after

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

I''m trying to set up a system that will allow users to upload files using the mongrel upload progress gem to a model that includes other information. While I''m willing to hack around with this myself for a while to get it working, I was hoping that someone had done this before and might be able to give me some hints/code to look at. My mediafile has a description, mediatype,

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

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

I just got the fire to clean up how our app is deployed and upgrading mongrel. Currently, our app is being deployed in a user''s home directory. This has caused some problems regards to user/group permissions... We decided we were going to move everything to /var/www/app which led me to the whole general layout of our deployment and some questions. ENV Ruby 1.8.5p12 Rails 1.2.3 Mongrel

Hi gurus, here at Scuola IaD we have some Rails applications in production, I''m the sysadmin so I made a script for governing mongrel instances via the service command and integrating their management in a RHEL environment. This script, available with more information here: http://bitsandchaos.wordpress.com/2007/12/14/mongrel-integration-for-rhel-fedora-and-derivatives-new-release/ has

At 03:24 PM 11/7/2007, mongrel-users-request at rubyforge.org wrote: > > Thanks for this Kirk. Yep, I was using 14400. I''m switching this > to > > 2 weeks: 1209600 and we''ll see if any further restarts are needed > by > > monit. > >I''ve always wondered why 14400 is the number that is always passed >around when talking about extending

Thought I''d drop a note about my experience with running mongrel directly under the solaris service management framework. So far I''m very impressed. SMF is the solaris replacement for the init system. It''s tied much more closely to the OS and for instance doesn''t use pid files. I''ve found you can completely eliminate mongrel cluster, and for that