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 truemped@googlemail.com
 designates 209.85.215.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=uZAKA2kM9ad6TjYUoFCpEakwZLs3n+l+cRQYtHt+/KeTTsD1wIlz0jB0LU4kcKVjyy
         UPXadxjUleCThLZSVjwkITpDZN5Jt6aWUb/0/2fhZCmZQQSI7+dR097w+q6lVbJ/ORN8
         8DSRkSdfJlvNBwOgWzXI/SV3Rn7mQQQIA3o58=
Message-ID: <4D8727D1.1090300@googlemail.com>
Date: Mon, 21 Mar 2011 11:26:25 +0100
From: Daniel Truemper <truemped@googlemail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: user <user@couchdb.apache.org>
Subject: CouchDB stops
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi there,

I have a CouchDB running on a production system where one process stores 
documents and attachments into couch and (several) other processes 
listen to changes (on different events). Every 12 hours I am running a 
compaction, which worked just fine for the last 3 days.

This morning though CouchDB stopped after running compaction. About a 
minute before, there was a log message related to compaction:

--
.. Compaction file still behind main file(update seq=27140, compact 
update seq=27136). Retrying.

.. Compaction for db "live" completed.
--

Then a handful of docs get written and CouchDB stopped. In 
"couch.stderr" I see 6 messages complaining about missing version info 
of libcurl

--
couchjs: ../libcurl.so.4: no version info available (required by couchjs)
--

but this does not affect view building or anything else.

(Note: I had to compile several libraries from source since I do not 
have appropriate rights to install packages.)

Then there are the following two messages:

--
heart: Erlang has closed.
heart: Executed "couchdb -k". Terminating
--

In "couch.stdout" there is no error message, and nothing like an 
"erl_crash.dump" is anywhere. None of the listening or pushing other 
processes show an error (except the one after CouchDB is stopped and 
they cannot access it anymore).

Does anyone have an idea where I should look and _what_ I should look for?

Best
Daniel