Displaying 20 results from an estimated 10000 matches similar to: "MySQL timeout value (was: mongrel - monit issue)"
2007 Nov 07
8
mongrel - monit issue
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
2006 Oct 31
9
Problems with mongrel dying
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
2006 Sep 21
10
How do you use Mongrel?
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
2008 Jan 21
14
properly restarting mongrel instances
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
2006 Nov 05
2
logrotate, mongrel cluster and monit
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
2008 Jan 09
9
mongrel, monit, and the many, many messages
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
2007 Feb 02
1
Monit / mongel_cluster 0.2.2 / mongrel 1.0.1
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
2006 Sep 07
4
How to setup a sweeper to restart stale or hung mongrel servers
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
2007 Aug 10
10
what is the correct way to stop/start a mongrel instance using monit with mongrel cluster
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
2007 Nov 05
29
Mongrel and memory usage
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
2006 Oct 02
3
Mongrel cluster FreeBSD rc.d script
Hello all
After installing Mongrel, Mongrel Cluster and all it''s dependencies via gems
under FreeBSD. Next I have configured all config/mongrel_cluster.yml for each
Rails app, then:
% mkdir /usr/local/etc/mongrel_cluster
and likend each railsapp.yml to it''s refering app/config/mongrel_cluster.yml
My question is, after preparing all base configs now I need to add some rc.d
2006 Sep 01
2
Making Mongrel play well with Monit
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 =
2007 Mar 26
4
Monit + Mongrel woes
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
2007 Mar 29
4
Machine reboot - monit fails to start mongrels
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
2007 Apr 03
11
monit vs mongrel cluster
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
2007 Aug 26
1
monit not executing start/stop/restart mongrels
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
2007 May 06
28
mongrel becoming unresponsive
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
2007 Sep 21
2
mysql storeconfigs needs mysql gem
Recently I started noticing that after running for a while
puppetmaster would freeze after a client called `freshness` which
would eventually result in the client getting a timeout and the client
dyeing. I tracked the freeze down to the call to
ActiveRecord::Base.verify_active_connections! in rails.rb on line 26.
After scouring the nets I finally found:
2006 Sep 05
1
Simple Mongrel performance question
Zed,
Do you have a feeling for how Mongrel''s speed has changed since you
started out? Just Mongrel with a plain static file; not burdened with
having to go through Rails.
You initial numbers were substantially faster than webrick. Now that
there is a lot more stuff in Mongrel, are they still substantially
faster in your benchmarks?
Thanks,
Kirk Haines
2007 Feb 27
3
mongrel_cluster and Monit
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