Rotating Ruby on Rails Log Files
April 20th, 2006
Long story short for those who aren't thrilled with my prose. If your Rails log file(s) are growing too large, log into your shell account and run this:
This blog had a rough time today. This morning I noticed that my disk space usage had increased to 418MB! Wow - my account only allows 500MB. So, I went and hunted down the culprit. My production.log had piled up to more than 300MB! Holy crap, what's going on?
My guess is that since I'm using the latest trunk version of Typo, there's probably some "issues." Either way, I started googling and found this page. Two solutions are presented. One involves edited something for Apache. One is a seemingly straightforward ruby fix. I chose to try the ruby solution.
Ruhtrow Raggy! That's what killed RubyNoob. Of course, I didn't realize that that's what did it until later. I googled around some more and kept running into the same variation of this solution. It was pretty frustrating. I moved that line of code all over the place in my environment.rb file, but each time RubyNoob would bite the dust.
Finally, I found this super excellent article. Julik gives some really awesome advice for Optimizing Rails apps including the gem that I kicked off this article with. Man, I wish I had found that before I went through all sorts of pain. Once again, though, this problem turned into an excellent learning opportunity.
That said, though, if you know how to automate this process inside of Rails without blowing up my blog, please leave a comment. I'd be really grateful!!
rake clear_logs
This blog had a rough time today. This morning I noticed that my disk space usage had increased to 418MB! Wow - my account only allows 500MB. So, I went and hunted down the culprit. My production.log had piled up to more than 300MB! Holy crap, what's going on?
My guess is that since I'm using the latest trunk version of Typo, there's probably some "issues." Either way, I started googling and found this page. Two solutions are presented. One involves edited something for Apache. One is a seemingly straightforward ruby fix. I chose to try the ruby solution.
Ruhtrow Raggy! That's what killed RubyNoob. Of course, I didn't realize that that's what did it until later. I googled around some more and kept running into the same variation of this solution. It was pretty frustrating. I moved that line of code all over the place in my environment.rb file, but each time RubyNoob would bite the dust.
Finally, I found this super excellent article. Julik gives some really awesome advice for Optimizing Rails apps including the gem that I kicked off this article with. Man, I wish I had found that before I went through all sorts of pain. Once again, though, this problem turned into an excellent learning opportunity.
That said, though, if you know how to automate this process inside of Rails without blowing up my blog, please leave a comment. I'd be really grateful!!
Leave a Reply