Feature #4553
Either add documentation on rotating logs or make it default
| Status: | Closed | Start date: | 08/17/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 1.1.0 | |||
| Keywords: | roadmapped | Affected URL: | ||
| Branch: | Affected Dashboard version: | |||
| Votes: | 0 |
Description
On Mon, Aug 16, 2010 at 3:32 PM, Steven L. Seed slseed1969@gmail.com wrote:
I found the root cause of my problem. After running of about 1 month using the development environment my log file grew to over 24GB. I had no idea this log file was even there since it’s in a less than standard location (/opt/puppet-dashboard/log/development.log). I switched to using the production environment and that initially helped along with purging about 3GB of my report data from the database, but ultimately, the very large log file was impacting things as well.
At the least we should add something to the README about rotating logs using logrotate or ‘rake log:clear’. I’ve also seen that you can configure rails to something similar with config.logger = Logger.new(“#{RAILS_ROOT}/log/#{RAILS_ENV}.log”, 50, 1.megabyte), so maybe we want to make something like that a default?
Related issues
History
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Needs Decision
Updated by Anonymous over 1 year ago
- Target version set to 1.0.5
Updated by Nigel Kersten over 1 year ago
- Status changed from Needs Decision to Accepted
- Keywords set to roadmapped
Updated by Jesse Wolfe about 1 year ago
- Status changed from Accepted to Closed
Merged into next as commit:f5ba67141ec0082bcb3a70ee1e6fa5d171664cb7
Merged into master as commit:308dcbbfc892ccbaf13b3be4d997c6cdcb6b44af as part of Iteration-2010-11-10
Updated by James Turnbull 10 months ago
- Target version changed from 1.0.5 to 1.1.0