@MIke: Thanks. You are right, there's one :)
@Robert: In the future, if such thing happens, how do i dump couchdb
dangling process info for you guys, so you can analyze what went wrong?
On Fri, Aug 9, 2013 at 5:40 PM, Mike Marino wrote:
> Yes, there's a heartbeat process that restarts the serv
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.koupria...@gmail.com> wrote:
> I tried killing beam, but it was start
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 wrote:
> check the pidfile (might be empty). If so, just kill the beam.smp
> processes. There's a known issue with pidfile management
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 wrote:
> Hi guys,
>
> Im having trouble stopping couchdb service using the 'service couchdb
> sto
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:
tcp0 0
