Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 11642 invoked from network); 27 Feb 2009 09:42:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Feb 2009 09:42:28 -0000 Received: (qmail 82730 invoked by uid 500); 27 Feb 2009 09:42:25 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 82700 invoked by uid 500); 27 Feb 2009 09:42:25 -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 82320 invoked by uid 99); 27 Feb 2009 09:42:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2009 01:42:24 -0800 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lasizoillo@gmail.com designates 209.85.220.165 as permitted sender) Received: from [209.85.220.165] (HELO mail-fx0-f165.google.com) (209.85.220.165) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2009 09:42:16 +0000 Received: by fxm9 with SMTP id 9so1092591fxm.11 for ; Fri, 27 Feb 2009 01:41:56 -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=Xr72jrd/Uv1bVuM6cO+ZxUmcSChJrIglUKcK2UQeKok=; b=mbT1dFMXrTsc1x7iezt/vgt5npfCdoa9tpkHIS/vEXZAscdXPxN+wxqWZa1xgAH7Jf 11lQBfSWHZuF7e2njtOK/cIiyaTCzlcq25jat2ZS0onJuCfn2MP4fhhf6kbr58BQoaag sEahq3EAGaDkPUkCidf1rYODUMzbDIU8CWdUI= 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=Bbx4+mGlYGiXaqQ7MfYO92ty0aWX++ghxRnMilVDJDOmEsK8nTxKeLdetoOPy0OV++ guNh9SV9haB8b5m9ffFBjbmOCdQy+HvV+t0wX0nsTSPjmKTpf7t9hkyQIJrqhx+rS5+y WYPe97q5fVVffHECdDSlQ+sDBy3Gf6dzJRRIA= MIME-Version: 1.0 Received: by 10.223.122.15 with SMTP id j15mr3107899far.10.1235727716146; Fri, 27 Feb 2009 01:41:56 -0800 (PST) In-Reply-To: <7fe7e0900902270036y6a9511b1oaac662b9e51f4d6d@mail.gmail.com> References: <7fe7e0900902270036y6a9511b1oaac662b9e51f4d6d@mail.gmail.com> Date: Fri, 27 Feb 2009 10:41:55 +0100 Message-ID: <49414f570902270141t5562904dsda99f42edb9d2c5a@mail.gmail.com> Subject: Re: Segmentation fault on PUT From: lasizoillo To: user@couchdb.apache.org, tim.somers@securysat.be Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 2009/2/27 Tim Somers : > Hi all, > > I've been using couchdb in combination with py-simplecouchdb since a coup= le > of weeks now on a small dataset (only 51 docs) with lots of updates. > Yesterday I checked out the latest update from svn, and left my applicati= on > running all night. This morning, the couchdb process had closed. > After restarting it, everything seems to be running fine for read access, > but on an update of any document, I get this error: > [debug] [<0.64.0>] 'PUT' /heasys/alert_3505_nomessages {1,1} > Headers: [{'Accept',"application/json, text/javascript, */*"}, > =A0 =A0 =A0 =A0 =A0{'Accept-Charset',"ISO-8859-1,utf-8;q=3D0.7,*;q=3D0.7"= }, > =A0 =A0 =A0 =A0 =A0{'Accept-Encoding',"gzip,deflate"}, > =A0 =A0 =A0 =A0 =A0{'Accept-Language',"en-us,en;q=3D0.5"}, > =A0 =A0 =A0 =A0 =A0{'Connection',"keep-alive"}, > =A0 =A0 =A0 =A0 =A0{'Content-Length',"239"}, > =A0 =A0 =A0 =A0 =A0{'Content-Type',"application/json; charset=3DUTF-8"}, > =A0 =A0 =A0 =A0 =A0{'Host',"localhost:5985"}, > =A0 =A0 =A0 =A0 =A0{'Keep-Alive',"300"}, > =A0 =A0 =A0 =A0 =A0{'Referer'," > http://localhost:5985/_utils/document.html?heasys/alert_3505_nomessages"}= , > =A0 =A0 =A0 =A0 =A0{'User-Agent',"Mozilla/5.0 (X11; U; Linux i686; en-US;= rv:1.9.0.6) > Gecko/2009020409 Iceweasel/3.0.6 (Debian-3.0.6-1)"}, > =A0 =A0 =A0 =A0 =A0{"X-Requested-With","XMLHttpRequest"}] > Segmentation fault > No difference in the error except for the headers whether I test it with = my > application or the futon interface. > > Any ideas, anyone? I have some days ago a segmentation fault when I modify one register. I was a corrupted database with only one problematic register. I don't advance in the problem because my couchdb is not a master repository. Compactation (for generate a new db file) did not solve my problem. I have to rebuild my couchdb from my master repository. Exists any tool for diagnostic and check db file structure? Regards, Javi PD: Excuse my poor english. > > Thanks > Tim Somers >