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 mmarino@gmail.com designates
 209.85.212.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAG+HO1x8MzJgiiK=fgeoOKH4WEo-B29XE8nF0NQjJMhgwrinXg@mail.gmail.com>
References: 
 <CAG+HO1ySP_fTQdb-1A-P+d=Hpu9G45=-_FJONMXxH_s7CKcOjg@mail.gmail.com>
 <CABvT1DEX5HvUb_RX8dT9M7k7i31VfEsmKKJi_jx+JgR2sHRG7Q@mail.gmail.com>
 <CAG+HO1x8MzJgiiK=fgeoOKH4WEo-B29XE8nF0NQjJMhgwrinXg@mail.gmail.com>
From: Mike Marino <mmarino@gmail.com>
Date: Fri, 9 Aug 2013 12:40:31 +0200
Message-ID: 
 <CAKiq=tAg5HYJsvMJpB3aKZtJfwWjFMnND7oxh6U82iGuKQ4vvg@mail.gmail.com>
Subject: Re: Couchdb service script does not stop the service
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=001a11c25bf69013cb04e3816838

--001a11c25bf69013cb04e3816838
Content-Type: text/plain; charset=ISO-8859-1

Yes, there's a heartbeat process that restarts the server if it dies (or is
killed).  Try

ps -ef | grep couch

and you should see the heartbeat process.

Cheers,
Mike


On Fri, Aug 9, 2013 at 12:37 PM, Andrey Kuprianov <
andrey.kouprianov@gmail.com> wrote:

> I tried killing beam, but it was starting over and over again. There's a
> heartbeat process for couch, isnt there?
>
>
>
> On Fri, Aug 9, 2013 at 4:52 PM, Robert Newson <rnewson@apache.org> wrote:
>
> > check the pidfile (might be empty). If so, just kill the beam.smp
> > processes. There's a known issue with pidfile management on first
> > startup on some OS's.
> >
> > B.
> >
> >
> > On 9 August 2013 10:45, Andrey Kuprianov <andrey.kouprianov@gmail.com>
> > wrote:
> > > Hi guys,
> > >
> > > Im having trouble stopping couchdb service using the 'service couchdb
> > > stop'. I've just installed fresh couhdb-1.3.1 with couchdb-lucene
> 0.10.0
> > on
> > > Ubuntu 12.04 LTS and saw that couchdb log is full of eaddrinuse error
> > again.
> > >
> > > netstat -anlp | grep 5984 was showing this:
> > >
> > > tcp        0      0 0.0.0.0:5984            0.0.0.0:*
> > LISTEN
> > >      30992/beam.smp
> > > tcp        0      0 10.248.7.104:34314      10.248.14.201:5984
> > >  ESTABLISHED 30992/beam.smp
> > > tcp        0      0 10.248.7.104:41687      10.248.14.201:5984
> > >  TIME_WAIT   -
> > > tcp        0      0 10.248.7.104:39102      10.248.14.201:5984
> > >  ESTABLISHED 30992/beam.smp
> > >
> > > The service script also doesnt print out any status about whether couch
> > is
> > > running or not, so it seems like it's a dangling process. Any ideas?
> > >
> > >   Andrey
> >
>

--001a11c25bf69013cb04e3816838--