At least in my case, the issue is definitely related to the size of the log. All the sapped memory gets freed as soon as I truncate the production.log.
I tried SyslogLogger today (http://rails-analyzer.rubyforge.org/hacks/classes/SyslogLogger.html) but couldn't get the rails log to only show up in one place when following the README's directions It was logging to /var/log/production.log as well as /var/log/messages. Server load jumped up to 2, I assume because of all the disk IO. Anyone who's deployed SyslogLogger and has insight, comments welcome. Also, anyone tried Analogger? http://analogger.swiftcore.org/ ed On Feb 13, 2008 3:13 PM, Joey Geiger <[EMAIL PROTECTED]> wrote: > So, it's the size of the LOG that is causing the issue? > > I'm rotating every night anyway using logrotate, but I was thinking > about moving to syslogger if I could find a nice how-to. > > > On Feb 13, 2008 1:11 PM, John Joseph Bachir <[EMAIL PROTECTED]> wrote: > > On Feb 13, 2008 10:50 AM, Sean Brown <[EMAIL PROTECTED]> wrote: > > > > > If anyone would > > > like to see our logrotate configuration, let me know. > > > > I would be interested in seeing your config, thanks for offering. > > Perhaps it's worthy of a new thread? > > > > -- > > John Joseph Bachir > > http://blog.johnjosephbachir.org > > http://lyceum.ibiblio.org > > http://dissent.cc > > http://jjb.cc > > _______________________________________________ > > > > Mongrel-users mailing list > > Mongrel-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
