similar to: mongrel - monit issue

Hello, I''m running mongrel behind apache via proxypass. Every now and then, a spammer tries to proxy traffic through apache, and for some reason, apache forwards the request to mongrel, even though it''s not a site being hosted by me. At times this seems to cause mongrel to become unresponsive, and all requests to the site then fail with a proxy error until mongrel is

After reading the digital shortcut and the documentation on the web site I''m confused. Which one should I use? pen, balance or nginx ? I don''t want to use a behemoth like appache and ssl is not needed so it reduces my choice to those three only.... What are the pros and cons of each? I don''t have much money, so the less ressources I use the better it is for me.... As

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

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

Hi guys, I''ve been running mongrel for a while now with Ruby 1.8.4, and last week upgraded to 1.8.6. Since upgrading, each morning when I wake up there''s a big problem: 1. Accessing the site returns a "500 Internal Server Error" 2. All the mongrel_rails processes are still running, but none of them are active (when I run top) 3. Lighttpd and pound are still

So here''s a random question: if a (Ruby) multi-threaded rails server could exist (bug free), would it be faster than using a mongrel cluster? (I.e. 10 mongrel processes versus 10 Ruby threads). I''m not sure if it would. RAM it might save, though. Any thoughts? -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

Hi guys, Does anyone know if mongrel has a built-in timeout for requests that take too long? If so, how do you increase it? I''ve found that some server requests are timing out. Complicated requests are already being farmed out to asynchronous processes. But some of the more basic requests are timing out when we have our peak server load in the mornings (the bottleneck is the

Hi folks. Using mongrel_rails and the mongrel_cluster capistrano recipes, I often encounter a situation where some of the mongrel processes don''t die in time to be restarted. The output of capistrano will tell me something like "mongrel on port 8001 is already up", but that''s only because capistrano/mongrel_rails failed to take it down in the first place. The solution

Hey folks, I''m working on the Mongrel book with Zed, and wanted to get some feedback from the core users (this list) about how they use Mongrel. That sounds a bit vague, but I''m interested in hearing things about frustrating problems / workaround, preferred configurations, if you have a particular way you set up / store your config files when developing / deploying an

I''m trying to sent a file to the iphone (which requires byte-range request support) using the rails send_file method. However, this fails, I think because of mongrel. I think so because if I send the iphone a file handled by nginx, it plays it fine. But then when I serve the file with rails the iphone can''t play it. Any ideas? Alex

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

How do I setup a sweeper to restart stale or hung mongrel servers? -- Jared Brown jaredbrown at gmail.com (765) 409-0875 7001 Central Ave Indianapolis, IN 46220 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060907/0994017f/attachment.html

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

Hello Mongrels, Building on the last messages about Fastthread, can we get a detailed survey of the different ways people are deploying their applications? It will help with near-future Mongrel development. Please include the following things: * Framework, if any (Camping, Merb, Rails, Nitro, Ramaze, IOWA, Rack...) * Mongrel version * Mongrel handlers used (rails, dirhandler, camping,

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, I am running mongrel 1.1 in production mode behind a lighttpd with mod_proxy. At first everything works fine, however, after a few days, the mongrel servers stop answering at all, even if I try to connect to them directly. I have checked logs but there is no sign of anything at all, and even when there was not a single request for a few days, it did freeze, and that on repeated occasions.

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