This same bug is still present, and caused my server to stop functioning because it generated so many files that it used all the inodes available!
This is caused by a bug in the CouchDB logrotate config. This is the default config:
However, the target path of
couchdb/couch.* combined with copytruncate means that each previous copy is copied again every time logrotate runs, resulting in an exponential number of copies!
This is fixed by changing the path to only target the current
couch.log file, and not the generated copies:
In my case, I started with a clean Bitnami deployment of CouchDB 2.3.0 on Google Cloud with minimal config changes. After running for a while, I noticed the CPU consistently running at 100%, with a lot of "disk full" errors in my server logs. It is made worse because the default CouchDB log level is "info", which generates a lot of logs.
Please fix this configuration bug since this is present even as recent as version 2.3.0, and will end up crashing the server due to the proliferation of log files!