Thanks for the tips Miles. One of them really hit home: I love writing to stdout, and it's all over the place in my app. It's great because you can run your scripts / apps as foreground and get a live trace, or daemonized and it goes to the log file. Your warning on this one sounds like the voice of experience, and I believe it. But I'd like to understand the details.
Any ideas why this is a dangerous thing to do? Thanks, Pete BTW. I don't know if lighty has a keepalive feature, but I'll look into this. Sounds like it was the main issue for you, and it could be for me too. On May 7, 2007, at 8:26 AM, Miles Egan wrote: > We've had this here too, to the point where it was becoming a bit of > a crisis. I've seen several suggested remedies: > > 1. make sure your log rotation is done outside mongrel, not using > ruby's log rotation features > 2. make sure your rails app doesn't ever try to write to stdout or > stderr > 3. avoid pstore-based sessions > 4. disable http keepalive on the apache frontend > > We tried all of these and it looks like #4 might have finally done > the trick. > > -- > miles > > "If money played an instrument it would be the saxophone." - Achewood > _______________________________________________ > 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
