Comments on: Rotating Rails Log Files http://www.nullislove.com/2007/09/10/rotating-rails-log-files/ Code for Coders Thu, 28 Aug 2008 13:46:48 +0000 http://wordpress.org/?v=2.5.1 By: Martin http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-1214 Martin Fri, 18 Jul 2008 14:39:43 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-1214 Thanks for the excellent article! I've tried (following different advice from various sources) using the method suggested by Matt, but I can't get it to work. I will definitely try this method. I feel that in most cases that the job of rotating logs is probably not the job of the application or web server. It's probably debatable as to where this kind of functionality should sit (as is the question of any domain-specific functionality), but it probably comes down to each individual case. Thanks for the excellent article! I’ve tried (following different advice from various sources) using the method suggested by Matt, but I can’t get it to work. I will definitely try this method. I feel that in most cases that the job of rotating logs is probably not the job of the application or web server. It’s probably debatable as to where this kind of functionality should sit (as is the question of any domain-specific functionality), but it probably comes down to each individual case.

]]> By: Simply Internet Trash » rotate those rails logs http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-1062 Simply Internet Trash » rotate those rails logs Wed, 12 Mar 2008 15:39:42 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-1062 [...] established a standard deployment location of /usr/local/sites/sitename for our apps. Following this advice I think I’ll use standard logrotate to move the logs around. I’ve read that log [...] [...] established a standard deployment location of /usr/local/sites/sitename for our apps. Following this advice I think I’ll use standard logrotate to move the logs around. I’ve read that log [...]

]]> By: Matt Tarbit http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-912 Matt Tarbit Thu, 24 Jan 2008 21:04:00 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-912 You can actually do log rotation from within rails by adding the following line to the Rails::Initializer.run block in your app's /config/environment.rb: config.logger = Logger.new(config.log_path, 50, 1024**2) The 2nd argument being the number of .log files you'd like to keep, and the 3rd being the size in bytes that the files are allowed to reach before they'll be rotated. So this line would keep up to a maximum of 50 1MB files. Not quite as configurable as logrotate perhaps (it doesn't support compression for example), but it's nice to be able to keep all of the config within the app. See here for more: http://blog.caboo.se/articles/2005/12/15/who-said-size-is-not-important You can actually do log rotation from within rails by adding the following line to the Rails::Initializer.run block in your app’s /config/environment.rb:

config.logger = Logger.new(config.log_path, 50, 1024**2)

The 2nd argument being the number of .log files you’d like to keep, and the 3rd being the size in bytes that the files are allowed to reach before they’ll be rotated. So this line would keep up to a maximum of 50 1MB files. Not quite as configurable as logrotate perhaps (it doesn’t support compression for example), but it’s nice to be able to keep all of the config within the app.

See here for more:
http://blog.caboo.se/articles/2005/12/15/who-said-size-is-not-important

]]> By: Ian Lotinsky http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-778 Ian Lotinsky Thu, 29 Nov 2007 20:35:14 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-778 Kevin -- Thanks. I did some more research and discovered that the daily/weekly/monthly option is to specify criteria for backup. So if you have it set to daily and, for some reason, the cron job runs twice, the log(s) will not be rotated. Of course you can override this behavior with the -f (--force) option. Thanks for the post! Kevin –

Thanks. I did some more research and discovered that the daily/weekly/monthly option is to specify criteria for backup. So if you have it set to daily and, for some reason, the cron job runs twice, the log(s) will not be rotated.

Of course you can override this behavior with the -f (–force) option.

Thanks for the post!

]]> By: Kevin Skoglund http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-766 Kevin Skoglund Mon, 26 Nov 2007 17:02:04 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-766 @Ian: It runs as a cron job, so it will run at whatever time your daily, weekly or monthly cron jobs run. AFAIK, you can't give it a more specific time. @Ian: It runs as a cron job, so it will run at whatever time your daily, weekly or monthly cron jobs run. AFAIK, you can’t give it a more specific time.

]]> By: Ian Lotinsky http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-763 Ian Lotinsky Sat, 24 Nov 2007 18:52:46 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-763 Thanks for the great post! Question: is there any way to specify what time you want the rotation to run? If not, is there a standard time it backs up at? Thanks! Thanks for the great post! Question: is there any way to specify what time you want the rotation to run? If not, is there a standard time it backs up at? Thanks!

]]> By: Laurent http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-758 Laurent Thu, 22 Nov 2007 14:32:43 +0000 http://www.nullislove.com/2007/09/10/rotating-rails-log-files/#comment-758 Kevin, Thanks much for this excellent article. I particularly appreciate the detailed explanations for each configuration statement that goes in logrotate.conf. The advantage of copytruncate over create is clear as crystal now. Kevin,

Thanks much for this excellent article. I particularly appreciate the detailed explanations for each configuration statement that goes in logrotate.conf.

The advantage of copytruncate over create is clear as crystal now.

]]>