Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of tisdall@gmail.com designates
 209.85.215.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1395402372.93156.YahooMailNeo@web171406.mail.ir2.yahoo.com>
References: <1395402372.93156.YahooMailNeo@web171406.mail.ir2.yahoo.com>
Date: Fri, 21 Mar 2014 09:19:42 -0400
Message-ID: 
 <CAGxYWpbWD0B1RC=+dT_sUpL9+tzeKieNfxD_Bs9zWvLVTFh90g@mail.gmail.com>
Subject: Re: Corrupt database file
From: Tim Tisdall <tisdall@gmail.com>
To: user@couchdb.apache.org, Chris Ashton <chrisjashton@yahoo.co.uk>
Content-Type: multipart/alternative; boundary=001a113484bc1adc6504f51dbdf5

--001a113484bc1adc6504f51dbdf5
Content-Type: text/plain; charset=ISO-8859-1

I don't think there's any tool for fixing corrupted db files...  What I'd
try doing is dumping all the content from the DB and reconstructing it.
 You can fetch everything in the database by downloading
http://127.0.0.1:5984/my_database/_all_docs?include_docs=true (where the IP
and domain is your server, and 'my_database' is your DB).  You'd then need
to write some sort of script to read that JSON document and then write the
values back into a _new_ database.

Does anyone know if there's a way to do this same sort of thing with
replication?  (I have to do it the other way because I don't have enough
space for 2 copies of my DB on my system)


On 21 March 2014 07:46, Chris Ashton <chrisjashton@yahoo.co.uk> wrote:

> Hi
>
> I am a novice with CouchDB and really struggling to support a product that
> someone developed before leaving the company. No one else has any skills in
> Couch so I'm trying to pick up the pieces.
>
> Our database has stopped responding and we've tried compacting but to no
> avail.
>
> We are getting errors like the following in the log file, which I presume
> mean that we have a corrupt db file for one reason or another:
>
>
> [Fri, 21 Mar 2014 10:06:56 GMT] [error] [<0.213.0>] ** Generic server
> <0.213.0> terminating
> ** Last message in was {'EXIT',<0.217.0>,
>                                {file_corruption,<<"file corruption">>}}
>
> I was wondering if there was a utility which would scan DB files and
> remove badly formed parts or anything like that? We are running on Windows.
>
> Many thanks
>
> Chris
>

--001a113484bc1adc6504f51dbdf5--