Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of zachary.zolton@gmail.com
 designates 209.85.219.208 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=p8/oi+Pxl/IBi/H0/1t0HTaJWslK4Yu/T6q4JevPCWzvJ3nmqFkns9ssKjnNjlv/nU
         FPfUcNvGiXMTbRz4t1xMxaSQrxOAQgaderWIZkZ1A2v/CGRME/N9UfMbp3xgnjpNRI4G
         mz39yg+ehsEDzE1WdPa8UR0a2UTIIcuKK5f6g=
MIME-Version: 1.0
In-Reply-To: <55047b710910051156i4efcb060o7d9f84a05576355f@mail.gmail.com>
References: <5E259690-AAE4-46AB-8346-3ACD10921500@freshout.us>
	<55047b710910050045rda81e37qb214558b22168645@mail.gmail.com>
	<293FA6BA-A2F9-439F-8F5C-96A52E640D57@freshout.us>
 <55047b710910051005h7192d0ber46c0b4136142041f@mail.gmail.com>
	<46aeb24f0910051022g40ab18b3y64be22dd8818066f@mail.gmail.com>
	<F754E739-32C6-4016-BC7A-990DD8CC1390@freshout.us>
 <46aeb24f0910051048g3c3f273aod1cd6bd838a0d644@mail.gmail.com>
	<55047b710910051156i4efcb060o7d9f84a05576355f@mail.gmail.com>
From: Zachary Zolton <zachary.zolton@gmail.com>
Date: Mon, 5 Oct 2009 14:12:06 -0500
Message-ID: <f728979f0910051212k2bddb92m4a053a7dcb480e54@mail.gmail.com>
Subject: Re: couchdb and monit
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Yeah, we've been using monit quite happily, as well:

check process couchdb with pidfile /usr/local/var/run/couchdb/couchdb.pid
group database
start program =3D "/etc/init.d/couchdb start"
stop  program =3D "/etc/init.d/couchdb stop"
if failed host 127.0.0.1 port 5984 then restart
if cpu is greater than 40% for 2 cycles then alert
if cpu > 60% for 5 cycles then restart
if 10 restarts within 10 cycles then timeout
depends on data_fs

You'll note that it depends on data_fs which is an Amazon EBS drive
that also is monitored. Furthermore, we can be notified of high CPU
usage for traffic spikes...

On Mon, Oct 5, 2009 at 1:56 PM, Nicholas Orr <nicholas.orr@zxgen.net> wrote=
:
> I've changed mine to do the -r 5and to send an alert if it is not running=
.
> as long as -r 5 does what it is suppose to do everything will be ok
> if it fails at least I'll know about is - this is where monit is useful, =
no
> matter how smart/capable an erlang app is "suppose" to be, I'd like to kn=
ow
> if it goes down :)
>
> Nick
>
> On Tue, Oct 6, 2009 at 4:48 AM, Robert Newson <robert.newson@gmail.com>wr=
ote:
>
>> Understood. All I'm saying is that Erlang applications should already
>> have rich support for process restarting, heartbeat/keep-alive.
>>
>> monit is a generic wrapper to add those things when they are absent. A
>> correctly configured Erlang application shouldn't need monit, imo.
>>
>> B.
>>
>> On Mon, Oct 5, 2009 at 6:40 PM, Francisco Viramontes <paco@freshout.us>
>> wrote:
>> > I dunno but I tried with the respawn parameter for couchdb command in
>> Gentoo
>> > but it did not work. Also I have other services setup with monit so it=
s
>> more
>> > convenient for me to have everything in one place.
>> >
>> > PAco
>> > On Oct 5, 2009, at 12:22 PM, Robert Newson wrote:
>> >
>> >> Isn't couchdb (at least in the Debian package) monitored by heart?
>> >>
>> >> B.
>> >>
>> >> On Mon, Oct 5, 2009 at 6:05 PM, Nicholas Orr <nicholas.orr@zxgen.net>
>> >> wrote:
>> >>>
>> >>> great!
>> >>> i was wondering what to put for the "test" conditions.
>> >>> Yours work well, so thanks to you as well ;)
>> >>>
>> >>> Nick
>> >>>
>> >>> On Tue, Oct 6, 2009 at 4:01 AM, Francisco Viramontes
>> >>> <paco@freshout.us>wrote:
>> >>>
>> >>>> Nicholas
>> >>>>
>> >>>> Thanks man it worked I had been banging on my head for a week becau=
se
>> of
>> >>>> this
>> >>>>
>> >>>> my final monit scipt is
>> >>>>
>> >>>> check process couchdb
>> >>>> =A0with pidfile /var/run/couchdb/couchdb.pid
>> >>>> =A0#start program =3D "/etc/init.d/couchdb start"
>> >>>> =A0#stop program =3D "/etc/init.d/couchdb stop"
>> >>>> =A0start program =3D "/usr/bin/sudo -u couchdb /usr/bin/couchdb -b =
-o
>> >>>> /dev/null
>> >>>> -e /dev/null -p /var/run/couchdb/couchdb.pid"
>> >>>> =A0stop program =A0=3D "/usr/bin/sudo -u couchdb /usr/bin/couchdb -=
b -o
>> >>>> /dev/null
>> >>>> -e /dev/null -p /var/run/couchdb/couchdb.pid -d"
>> >>>> =A0if failed host 127.0.0.1 port 5984 then restart
>> >>>> =A0if failed url http://localhost:5984/ and content =3D=3D '"couchd=
b"' then
>> >>>> restart
>> >>>> =A0group couchdb
>> >>>>
>> >>>> PAco
>> >>>>
>> >>>>
>> >>>> On Oct 5, 2009, at 2:45 AM, Nicholas Orr wrote:
>> >>>>
>> >>>> =A0My monit script is verbatim, as monit is run as root I want couc=
hdb
>> >>>>>
>> >>>>> run as couchdb so do the following
>> >>>>>
>> >>>>> check process couchdb with pidfile /var/run/couchdb/couchdb.pid
>> >>>>> =A0start program =3D "/usr/bin/sudo -u couchdb /usr/bin/couchdb -b=
 -o
>> >>>>> /dev/null -e /dev/null -p /var/run/couchdb/couchdb.pid"
>> >>>>> =A0stop program =A0=3D "/usr/bin/sudo -u couchdb /usr/bin/couchdb =
-b -o
>> >>>>> /dev/null -e /dev/null -p /var/run/couchdb/couchdb.pid -d"
>> >>>>>
>> >>>>> try that and see what happens...
>> >>>>>
>> >>>>> On Mon, Oct 5, 2009 at 7:49 AM, Francisco Viramontes <
>> paco@freshout.us>
>> >>>>> wrote:
>> >>>>>
>> >>>>>> Hey Guys
>> >>>>>>
>> >>>>>> has anyone tried to monitor couch with monit?
>> >>>>>>
>> >>>>>> I am using this settings and monit successfully monitors but when
>> >>>>>> couchdb
>> >>>>>> dies it fails to restart the service and I can find out why
>> >>>>>>
>> >>>>>> here is my couchdb.monitrc file:
>> >>>>>>
>> >>>>>> check process couchdb
>> >>>>>> =A0with pidfile /var/run/couchdb/couchdb.pid
>> >>>>>> =A0start program =3D "/etc/init.d/couchdb start"
>> >>>>>> =A0stop program =3D "/etc/init.d/couchdb stop"
>> >>>>>> =A0if failed host 127.0.0.1 port 5984 then restart
>> >>>>>> =A0if failed url http://localhost:5984/ and content =3D=3D '"couc=
hdb"'
>> then
>> >>>>>> restart
>> >>>>>> =A0group couchdb
>> >>>>>>
>> >>>>>> BTW I am using couch 0.9.1 and about once a day it dies on me the
>> only
>> >>>>>> thing
>> >>>>>> I get from the log are strange erlang error messages saying OS
>> procees
>> >>>>>> timeout, anyone know whats that about?
>> >>>>>>
>> >>>>>> PAco
>> >>>>>>
>> >>>>>>
>> >>>>
>> >>>
>> >
>> >
>>
>