Yeah I tried a completely different machine, it does the same thing so I
doubt it's the hardware at all. I've tried quite a few configurations of
apache/mysql/php and it still happens. What's interesting is if I kill a
process with -SEGV mod_whatkilledus logs it, but when the actual seg
faults occu
If the hardware is relatively the same id say start by checking the
differences in the configs. What MPM are you running? Do you have
keepalives on? On a server that experiences many hits I found better
results in turning keepalives off or setting the max keepalive timeout
to <=5. Are you noticing
Thanks for the reply, the hard drives are different, the distro is
different (gentoo and mandriva), I've tried apache 2.0, and 2.2.2,
MaxClients is set to 512, most it sees is 200 or so. mod_whatkilledus
doesn't do anything, that's whats weird, no output at all, same for core
dumps. By mod_systemst
you can
see from my log output mod_whatkilledus is not doing anything. Is there
something im missing to make both of these work? Any help would be appreciated
as this is driving me nuts =]
-Nick
Nick Wilson
Web Developer
Digitally Imported, Inc.
http://www.di.fm
http://www.sky.fm
: [EMAIL PROTECTED] help with Segmentation fault
On 7/25/06, Nick Wilson <[EMAIL PROTECTED]> wrote:
> At first I thought it was a ram issue, but when I moved it to another
web
> server running apache 2.0.58/php5.0.4 the same thing happens. I've
attempted
> to setup a core dump
the
EnableExceptionHook directive on and the module is loaded, however as you can
see from my log output mod_whatkilledus is not doing anything. Is there
something im missing to make both of these work? Any help would be appreciated
as this is driving me nuts =]
-Nick
Nick Wilson
Web
