couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Markham (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (COUCHDB-1380) logrotate doesn't work correctly with couchdb 1.2.x
Date Tue, 17 Jan 2012 09:46:39 GMT
logrotate doesn't work correctly with couchdb 1.2.x
---------------------------------------------------

                 Key: COUCHDB-1380
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1380
             Project: CouchDB
          Issue Type: Bug
    Affects Versions: 1.2
         Environment: CentOS 5.6 x64, couchdb 1.2.x (13th Jan 2012 - 1.2.0a-08d8f89-git),
logrotate 3.7.4
            Reporter: Alex Markham
            Priority: Minor


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?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message