Bug #2962
closed
logrotate : rudder reports
Added by Francois BAYART about 12 years ago.
Updated over 9 years ago.
Description
your logrotate rules use delaycompress, I suppose it's for easily read log in case of problem. In my case /var/log/rudder/reports use 2.5Go and delayed log file use 1.5Go of this 2.5Go.
So I think it could be better if you don't use delaycompress option, what's your opinion ?
- Category set to 11
- Status changed from New to Discussion
- Assignee set to Jonathan CLARKE
- Priority changed from N/A to 2
As I can understand, the use of delaycompress prevent logs to be compressed until concerned app has closed all writings in its logfile. It is useful to prevent some errors but with Rudder which could create logs as heavy as yours, it seems to me that this option should be removed like you suggested. At least for the reason that prevent a log file heavier than 1Go is a useless loss of space.
What do you think about it, Jon ?
Thanks to report us your experience with Rudder :)
- Tracker changed from Question to Bug
- Status changed from Discussion to 2
- Assignee changed from Jonathan CLARKE to Nicolas PERRON
Nicolas PERRON wrote:
As I can understand, the use of delaycompress prevent logs to be compressed until concerned app has closed all writings in its logfile. It is useful to prevent some errors but with Rudder which could create logs as heavy as yours, it seems to me that this option should be removed like you suggested. At least for the reason that prevent a log file heavier than 1Go is a useless loss of space.
What do you think about it, Jon ?
Absolutely, this is painful for users. Let's remove it.
- Status changed from 2 to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:21df761d0ca6af0d0c0645cdc482a3eb5a90bef9.
- Status changed from Pending technical review to Released
- Project changed from Rudder to 34
- Category deleted (
11)
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF