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 -
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?
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|5h 2m||1||Robert Newson||17/Jan/12 14:47|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||1.2 [ 12315198 ]|
|Fix Version/s||1.3 [ 12318350 ]|
|Resolution||Fixed [ 1 ]|
|Assignee||Robert Newson [ rnewson ]|
|Priority||Minor [ 4 ]||Blocker [ 1 ]|