On Tue, Aug 25, 2009 at 10:32 AM, Frank Wiles <fr...@wiles.org> wrote:
> > Hmmm, that's a difficult situation to debug. Are you running anything > in front of apache/mod_perl like perlbal or nginx? If so, those might > be the cause. > I am running perlbal in front of apache, yes. perlbal is a complete lifesaver for me, because my site is high traffic and perlbal takes care of lingering prowsers and such, to keep the number of my apache processes down. When I restart apache, I do not restart perlbal. I use perlbal everywhere, including on my old Fedora server, and it seems to be very stable. > > My suggestion would be to run a separate instance of your app on a > high port with a single apache instance and see if you can find a way > to reliably reproduce the problem. Then, if there isn't anything > useful in the error log, use the debugger to step through the code as > you reproduce the issue from the browser. > > I am afraid that it is hard to reproduce. Since I run ads and such, I cannot really afford to pause for very long to debug the issue, plus it happens randomly. My 5 minute restarter saves me from a very big trouble
