incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Dionne <dio...@dionne-associates.com>
Subject Re: Crash of CouchDB 1.2.x
Date Sun, 11 Mar 2012 12:33:49 GMT
Stefan,

At a glance I would suspect you've run out of disk space and the error thrown is not caught
resulting in the badmatch,

Bob

On Mar 11, 2012, at 6:41 AM, Stefan Kögl wrote:

> Hi,
> 
> I had my CouchDB 1.2.x (fb72251bc7114b07f0667867226ec9e200732dac)
> crash again twice today.
> 
> The first one was while the instance was pull replicating (which
> failed due to the source being unreachable), and compacting a rather
> large view (from ~216G disk size to about 57G data size, if that's
> relevant).
> 
> Here's the log that shows the crash
> 
> http://friendpaste.com/41Idie3gGdQRxJPEyVHpTR
> 
> After the crash the view compaction stopped, and I tried to restart it
> 
> $ curl -H "Content-Type: application/json" -X POST
> http://stefan:********@localhost:5984/mygpo/_compact/users-tmp
> {"error":"timeout","reason":"{gen_server,call,\n
> [<0.19783.69>,\n
> {start_compact,#Fun<couch_view_compactor.0.15011741>}]}"}
> 
> http://friendpaste.com/2A086gHN8dNEJHPpMkDrPO
> 
> I assume this is because deleting the .compact.view file took too
> long. The compaction started anyway, though. Besides the replication,
> there were no other activities on the server.
> 
> Please let me know if I can assist with debugging somehow.
> 
> 
> -- Stefan
> 
> 
> 
> On Fri, Mar 2, 2012 at 11:51 AM, Jan Lehnardt <jan@apache.org> wrote:
>> 
>> On Mar 2, 2012, at 11:29 , Stefan Kögl wrote:
>> 
>>> On Thu, Mar 1, 2012 at 9:39 PM, Jan Lehnardt <jan@apache.org> wrote:
>>>> Where in there did you do the git pull? And was a make clean or git clean
>>>> involved?
>>> 
>>> IIRC I did not pull in between, only apply the patch I mentioned
>>> earlier ( http://friendpaste.com/178nPFgfyyeGf2vtNRpL0w ). And I
>>> probably did a make clean && make && make install.
>>> 
>>> 
>>>> I think you should be in the clear with that procedure, but just to be
>>>> sure, I think it'd be worth rm'ing all .beam files you find manually
>>>> after the uninstall.
>>> 
>>> Done, I'll report back if the problem appears again.
>> 
>> Thanks Stefan, your help here is really appreciated :)
>> 
>> Cheers
>> Jan
>> --
>> 


Mime
View raw message