Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 22630 invoked from network); 29 Oct 2010 13:43:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Oct 2010 13:43:53 -0000 Received: (qmail 83792 invoked by uid 500); 29 Oct 2010 13:43:52 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 83588 invoked by uid 500); 29 Oct 2010 13:43:51 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 83580 invoked by uid 99); 29 Oct 2010 13:43:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 13:43:50 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rusvdw@gmail.com designates 209.85.216.52 as permitted sender) Received: from [209.85.216.52] (HELO mail-qw0-f52.google.com) (209.85.216.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 13:43:43 +0000 Received: by qwc9 with SMTP id 9so2288402qwc.11 for ; Fri, 29 Oct 2010 06:43:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=NX398VAxOhVkjBBi213hp2R2DqbN5+n8O3qXoLl10P8=; b=sGdG2InIVYeY3iVns1TLMjC61ub3bdORLH5B7AhhLYKUjZvfrjm7NLdt9CJfIU+n97 +wqnTinEanL0MKt/acnZljLEYhIZct8jAr2+eQDPF8yXblus+l/pxllm/x76osvElEDA U0YjWnW2SFRgOvMfwFwQLNbFFZhIUhrre+k6E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=TkiC5uv4LcIuJ+Z4yC/B9LGzl7q2GSuK2YzpWEFGDcejc6nqKapdfe5g19NaV0ySi3 act9kFf3wcfux4wxb8acdT8FF7w4bW3irHoZDKC8NsbLkBPBPupBd5M4eJf9qiXiUtSb T6bhPOjEHSUxKLyMGbyGLKDtqIEgD6+pjr/tY= MIME-Version: 1.0 Received: by 10.224.28.144 with SMTP id m16mr232687qac.2.1288359802719; Fri, 29 Oct 2010 06:43:22 -0700 (PDT) Received: by 10.229.246.76 with HTTP; Fri, 29 Oct 2010 06:43:22 -0700 (PDT) In-Reply-To: References: Date: Fri, 29 Oct 2010 15:43:22 +0200 Message-ID: Subject: Re: Couch crashing every couple of days From: Russell To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Thanks guys, I'll definitely give the auto restart a go, but I am a little worried about what the debug level logging is going to do to my production servers. On Fri, Oct 29, 2010 at 11:21 AM, Randall Leeds wrote: > On Fri, Oct 29, 2010 at 02:08, Dirkjan Ochtman wrote: >> On Fri, Oct 29, 2010 at 11:05, Russell wrote: >>> I am well aware that a crash report with no information is useless, >>> but I cannot find any logs that tell me what happened. So my question >>> is: >>> >>> 1. Where should I be looking for information about the crash? >> >> You could try to turn on debug-level logs to see what happens right >> before it goes down. Also, is there any memory pressure on the server? >> You might also want to check your syslog. >> >>> 2. What is the best way to auto restart couch on Ubuntu whenever this happens? >> >> I think you can just use normal monitoring services (monit, >> supervisor, that kind of thing). > > There's heartbeat option (-r X) which will restart the server after X > seconds if it dies. > If you're starting couchdb from an init script you may also find > /etc/default/couchdb (or something equivalent in your distro) is a > good place to set this. >