Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CouchDB dies if log directory is full

Open
#5,283 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
erlang
Domain
databases, observability-sre

Research direction

Start by reproducing the failure with the filesystem containing the CouchDB file-based log full, as described in the issue. Trace the file-based logging entry point and determine how disk-full errors affect the service; done means CouchDB remains running and the separate data directory continues to work while logging stops.

Written by the indexing model from the issue text.

Description

bug needs-triage

CouchDB dies and systemd tries to restart it over and over, if the log directory for file based logging is full.

Steps to Reproduce

Fill the disk (for example with fallocate) where the CouchDB log is written to and watch CouchDB go down.

Expected Behaviour

I expect, that CouchDB just stops logging and still works. The CouchDB data directory is on a separate disk and still has plenty of space to work with.

Your Environment

Debian 12 with the official CouchDB 3.3.3 package.

Dominant language
Erlang
Stars
7k
Forks
1.1k
Avg merge
2d 24m
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/couchdb

All issues in apache/couchdb

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.