From user-return-3321-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Feb 04 14:12:50 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 43650 invoked from network); 4 Feb 2009 14:12:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Feb 2009 14:12:50 -0000 Received: (qmail 20799 invoked by uid 500); 4 Feb 2009 14:12:49 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 20748 invoked by uid 500); 4 Feb 2009 14:12:49 -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 20737 invoked by uid 99); 4 Feb 2009 14:12:49 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 06:12:49 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.198.230 as permitted sender) Received: from [209.85.198.230] (HELO rv-out-0506.google.com) (209.85.198.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Feb 2009 14:12:41 +0000 Received: by rv-out-0506.google.com with SMTP id g9so2012391rvb.3 for ; Wed, 04 Feb 2009 06:12:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=M/rj93w8+BfNqqcZswis+XT5b9sAo+D9NaXAKcds06U=; b=E1N5po3HnzLyzbpkvRzrr6xDSwbM6lPncmN8bvsKbpU6qDxvdFnZdbVMio+ckEIPRA 4TRRSUMJjq8CMkjEQTINR7ey6kKS6h6XxMd2qTQLVEOyjem8FO5CyUG9JDUly3Ml8Bsx eK+tFs/Ltmk/zi55W8+lB3uLU3VOA8Li/2bR0= 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:content-transfer-encoding; b=Au1ysQFL3mfWYdnlra8YP24YXmBI+Xhv9m/BFIr2YdpV+kO/BBppNUOaKC38NyRSOf sWuzAAKwDNAVFeejJufdpwnonxh8IdLmGqxKzyi3zZoEIxUFovjtCNl8nso1rf5LsPLd +hRLtCEOcJDmBomLzsngywMgkqfU55qf+f/Us= MIME-Version: 1.0 Received: by 10.140.127.13 with SMTP id z13mr1335342rvc.30.1233756739782; Wed, 04 Feb 2009 06:12:19 -0800 (PST) In-Reply-To: References: <226d73360902040201n1aef49fbm19507255fae268d@mail.gmail.com> Date: Wed, 4 Feb 2009 09:12:19 -0500 Message-ID: Subject: Re: CouchDB Crash during large data import... From: Paul Davis To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Feb 4, 2009 at 5:17 AM, Philip Fennell wrote: > Ulises, > >> As for couchdb crashing, it does look like it was couch_log going poop > > When I re-named the log file and re-started Couch the 'gen_event handler > couch_log crashed' messages disappeared from the terminal window. > > >> I can't really tell if it did because of the disk being full or > otherwise > > The shared drive that VMWare Player was using to run Linux has 221GB of > free space. > You might want to double check on this as: {{badmatch,{{error,enospc},5315956736}}, [{couch_btree,'-write_node/3-lc$^0/1-0-',3}, points pretty directly at being at least *told* that there's no space left. > > Regards > > Philip Fennell > > > > > > -----Original Message----- > From: Ulises [mailto:ulises.cervino@gmail.com] > Sent: 04 February 2009 10:01 > To: user@couchdb.apache.org > Subject: Re: CouchDB Crash during large data import... > >> Would it be possible for Couch to start a new log file each day like >> Tomcat does? > > I'd suggest you look at logrotate actually for this. > > As for couchdb crashing, it does look like it was couch_log going poop > but I can't really tell if it did because of the disk being full or > otherwise. > > HTH, > > U > > http://www.bbc.co.uk/ > This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. > If you have received it in error, please delete it from your system. > Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. > Please note that the BBC monitors e-mails sent or received. > Further communication will signify your consent to this. > >