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 curt.arnld@gmail.com designates
 209.85.222.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=QudonV3bPf3BSVRvO1e2CWBuwQDwl3XjlcI+7Eu0QYypqBMbW2dDUBgbtPqiGxTcH0
         eIyj7A8dW9jaV7llVa4imF1Nd99MApVS3C5C11s7lx1KmScp2Bo1wgYjIWh+hwCeMkgo
         gVjvI2202bCkqdNWnKp1Os6T6h8vJz+1eqIvE=
Sender: Curt Arnold <curt.arnld@gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: Re: Timeout Error when trying to access views + Indexing problems
From: Curt Arnold <carnold@apache.org>
In-Reply-To: <6cfccb3d0910052346hb4ca0b3o7eb6e77fec4ac1a7@mail.gmail.com>
Date: Tue, 6 Oct 2009 08:29:48 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <19F6C39C-20E9-4DA5-B5C8-D01CA1D51675@apache.org>
References: <6cfccb3d0910030910m678c9157o811a57e02ffbeff0@mail.gmail.com>
  <6cfccb3d0910031824q5d9362c2k7719b32a779e956f@mail.gmail.com>
  <1521F562-7878-423B-BEC3-FF2A1916DA0C@gmail.com>
 <6cfccb3d0910032307i1df64f79u437d5c803bff2c50@mail.gmail.com>
  <A60F21CC-9C57-4202-84C1-04BEF84CD141@apache.org>
 <6cfccb3d0910052346hb4ca0b3o7eb6e77fec4ac1a7@mail.gmail.com>
To: user@couchdb.apache.org


On Oct 6, 2009, at 1:46 AM, Glenn Rempe wrote:
>
> - there is some kind of corruption in the main DB file and when this  
> point
> is reached (or a specific record in the DB?) that it crashes? If so  
> how can
> I best identify this?

Inserting mal-encoded documents into CouchDB could interfere with  
document retrieval and indexing, see https://issues.apache.org/jira/browse/COUCHDB-345 
.  Possibly one of those got into your database and now it is stopping  
the rebuilding of views.  A patch recently got added to prevent mal- 
encoded documents from being accepted, but it does not fix the problem  
on an existing database that has been corrupted.   I do not know if  
the symptoms are the same as what you are observing, but I think it  
would be a likely culprit.