Hi Morten, Thanks a lot,
By putting an eval around the code I found out, that the segfault was produced by next request to the same child after the $r->print failed. $r->print is still failing from time to time, but it's not producing segfaults anymore! Thanks Denis -----Ursprüngliche Nachricht----- Von: Morten Bjørnsvik [mailto:morten.bjorns...@experian-da.no] Gesendet: Montag, 23. November 2009 10:16 An: mod_perl list Betreff: RE: AW: print throwing intermittent Segfaults Hi I've had a similar error I "fixed" it by adding an eval block around the offending code which was tracked back to MASON. http://rt.cpan.org/Public/Bug/Display.html?id=49031 We compile everything from scratch apache,perl,mod_perl,mason, all modules by an automated build script. Earlier when we run on mod_perl1.99 and the redhat stack it worked fine. But then we had other worries :-) -- Morten Bjoernsvik, Developer, Decision Analytics -----Original Message----- From: André Warnier [mailto:a...@ice-sa.com] Sent: 23. november 2009 09:46 To: mod_perl list Subject: Re: AW: print throwing intermittent Segfaults Denis Banovic wrote: > Hi Willian, > > Thanks for your checklist, I've run through it, segfaults still there... > Right now it takes less then a minute from apache restart to the first > segfault. > This is from the error_log from the RedHat 5 Production machine: > > Apache2::RequestIO::print: (103) Software caused connection abort at > > The guys from rackspace are saying that I should recompile all my perl > modules installed directly from CPAN ( see above ) , do you think this would > help? > Or has someone another hint? > Just my grain of salt : in my own experience, 99% of the "segfault" cases I have encountered, was when Apache or Perl tried to run a piece of code not meant for this machine (such as a library meant for another machine or another OS version). Maybe one of the modules you are using installed a wrong library ? In that sense, the guys from rackspace may be right, although I believe that the CPAN modules don't generally contain object-code libraries, or else they do compile them at installation. So maybe it is a library from the RHEL repository which is wrong.
