One great tool that would help with the diagnosis is the very useful mp2bug, found in mod_perl-2.0/bin/mp2bug
Can you run that from your mod_perl install and post the output? Version details are a huge clue in solving mysteries like this. On Tue, Aug 25, 2009 at 10:10 AM, Igor Chudov<ichu...@gmail.com> wrote: > > > On Tue, Aug 25, 2009 at 10:50 AM, Frank Wiles <fr...@wiles.org> wrote: >> >> >> > 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 >> >> No of course, that's why I suggested running it on a higher port and >> leaving your production site alone. Just to isolate the problem down >> as small as possible. (i.e. no perlbal, single apache process, no >> other users, etc. ) to see if you can narrow down what piece of the >> puzzle is the one causing the issue. >> >> Frank, I tried to run apache2 -X and did thousands of queries, they did >> not break anything. It is "something else". > > Re: segfaults: I do get segfaults in apache, indeed. > > Re: httpd config file: See attached. It is kind of big. >
