|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PhillyOnRails] Monit + Mongrel
|
- From: "Randy Schmidt" <randy.schmidt@gmail.com>
- To: talk@phillyonrails.org
- Subject: Re: [PhillyOnRails] Monit + Mongrel
- Date: Sun, 27 Jan 2008 22:55:19 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=7k0iFVCQzs8dba7brclBGHozYaVofddVf9GnMURrRZI=; b=W2c2g7pWQfFfc0+T1Nbl6daGd/VNImldItyhAlyCs5KUHoT6Zu5eTcV1XyqL5hN2RTqkCOxTWSWB/Q1U/dOzmJDKVEj7/34Naf0h1PKe2HJB+99YT6xxQhxIm34cgU/IR/owTnIkWXbO4BMXcKxq8KdNmXBfk2gnKaS2caDyfFk=
- List-archive: <http://lists.phillyonrails.org/pipermail/talk>
- Reply-to: talk@phillyonrails.org
- Sender: talk-bounces@phillyonrails.org
Evan,
That's working in that I now have a responsive app when starting,
however, I still get the failed to start message and then an email
with "Execution failed Service mongrel_6000". Some info:
tyler ~: monit -g wire_staging_mongrels restart all
'mongrel_6000' trying to restart
'mongrel_6000' stop: /usr/bin/env
stopping port 6000
'mongrel_6000' start: /usr/bin/env
'mongrel_6000' failed to start
starting port 6000
check process mongrel_6000 with pidfile
/var/www/apps/wire/staging/current/log/mongrel.6000
start program = "/usr/bin/env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/
INLINEDIR=/var/www/apps/wire/staging/current/tmp/inline
HOME=/home/deploy mongrel_rails cluster::start -C
/var/www/apps/wire/staging/current/config/staging/mongrel_cluster.yml
--clean --only 6000"
stop program = "/usr/bin/env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/
INLINEDIR=/var/www/apps/wire/staging/current/tmp/inline
HOME=/home/deploy mongrel_rails cluster::stop -C
/var/www/apps/wire/staging/current/config/staging/mongrel_cluster.yml
--only 6000"
if mem is greater than 110.0 MB for 4 cycles then restart # eating up memory?
if cpu is greater than 50% for 2 cycles then alert # send an email to admin
if cpu is greater than 80% for 3 cycles then restart # hung process?
if loadavg(5min) greater than 4 for 8 cycles then restart # bad, bad, bad
GROUP wire_staging_mongrels
Thanks for your help so far!
Randy
_______________________________________________
To unsubscribe or change your settings, visit:
http://lists.phillyonrails.org/mailman/listinfo/talk
|
|