couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Spike Grobstein <>
Subject Re: running out of space
Date Mon, 26 Nov 2012 17:11:11 GMT
Hi Robert,

Wow. You are correct. I can't believe I never thought to look at the logs. I guess when the
HTTP requests never failed, I didn't think to look there.

It's loading up with errors related to

[Mon, 26 Nov 2012 17:06:54 GMT] [error] [emulator] Error in process <0.20250.6> with
exit value: {{badmatch,no_valid_header},[{couch_db_updater,start_copy_compact,1}]}

I have almost no experience with couch administration outside of what I've done with chef.

What could be the reason for this?



On Nov 26, 2012, at 12:01 PM, Robert Newson wrote:

> Is the compaction completing successfully? The log should indicate that.
> On 26 November 2012 16:56, Spike Grobstein <>wrote:
>> Hi CouchDB mailing list,
>> I've been running Chef Server since about March and continue to run out of
>> space. I've emailed the Chef mailing list and although they were able to
>> help, none of their answers successfully solved my problem.
>> I'm running CouchDB v1.0.1:
>> chef-server:~$ curl localhost:5984
>> {"couchdb":"Welcome","version":"1.0.1"}
>> And I have a script running daily via cron that compacts the data and the
>> views:
>> unfortunately, this has not halted the growth of used space on my couchdb
>> partition. It doesn't seem to be cleaning up deleted documents:
>> chef-server:~$ curl -H "Content-Type: application/json" localhost:5984/chef
>> {"db_name":"chef","doc_count":1235,"doc_del_count":10212,"update_seq":536514,"purge_seq":0,"compact_running":false,"disk_size":45922017384,"instance_start_time":"1353948344088704","disk_format_version":5,"committed_update_seq":536514}
>> Currently, the couchdb partition is using up 43GB of the 60GB allocated to
>> it. Is there anything I can do?
>> The server is Ubuntu 12.04.1 LTS with all of the latest packages. I've
>> tried rebooting the server and restarting the couchdb daemon (as suggested
>> on the chef mailing list), but to no avail.
>> Any ideas?
>> Thanks!
>> ...spike

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message