[COUCHDB-1380] logrotate doesn't work correctly with couchdb 1.2.x

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.2, 1.3
• Labels: logging logrotate

Environment

CentOS 5.6 x64, couchdb 1.2.x (13th Jan 2012 - 1.2.0a-08d8f89-git), logrotate 3.7.4

• Assignee: Robert Newson
• Reporter: Alex Markham
• Created: 17/Jan/12 09:45
• Updated: 15/Nov/18 23:02
• Resolved: 17/Jan/12 14:47

Description

Running logrotate -f with couchdb 1.2.x leaves null data at the start of the couch.log file, I'm guessing equal to the size of data that should have been removed and rotated into the log.1 (eg "head -c 1000000000 couch.log" is blank)

This does not happen on couchdb 1.1.1, 1.0.2 or 1.0.3

The log files then stay large, and when trying to grep or less them, they are reported as binary.

This seems to have happened to another user, but no details of OS or version were reported: http://comments.gmane.org/gmane.comp.db.couchdb.user/16049

The logrotate config used is very similar to the one installed with couchdb -
/var/log/couchdb/*.log {
size=150M
rotate 5
copytruncate
compress
delaycompress
notifempty
missingok
}

Has there been any changes to the interaction with log files/file handles since 1.1.1? Does couchdb need to receive a SIGHUP? Or can anyone reproduce this?

Issue Links

• is related to: COUCHDB-1218 Better logger performance