For what it is worth and in case anyone googles for this issue in
future, the segvs went away when I applied the latest kernel patches and
glibc stuff for redhat9, and the latest perl install, from
updates.redhat.com

the kernel is now 2.4.20-30.9smp

perl is now perl 5.8.0 with MAINT18379 patch


I did not recompile modperl or apache after the OS upgrade.

strace on child processes started working again as well.


I think base redhat9 (shrike) with no updates is not quite trustworthy
for apache.

thanks for the explanation, though, it'll help in future.

-justin

SB> justin wrote:
>> Our modperl servers with apache+modperl >= versions 1.3.28 and modperl
>> 1.28, crash randomly with
>> 
>> [Tue Mar  9 18:02:17 2004] [notice] child pid 10940 exit signal Segmentation fault 
>> (11)
SB> [...]
>> How can I best debug this? perhaps capture the segv and do a stack trace
>> or write a core file? it only happens in production, or if it happens in
>> dev, then I need a production-like request rate anyway.

SB> Configure the system to allow core files dumping as explained here:
SB> http://perl.apache.org/docs/2.0/devel/debug/c.html#Getting_the_core_File_Dumped
SB> once you have the core file, you can get the backtrace to find where it fails:
SB> http://perl.apache.org/docs/1.0/guide/help.html#How_to_Report_Problems
SB> or may be you will have luck with this module:
SB> http://search.cpan.org/dist/Debug-FaultAutoBT/

SB> __________________________________________________________________
SB> Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
SB> http://stason.org/     mod_perl Guide ---> http://perl.apache.org
SB> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
SB> http://modperlbook.org http://apache.org   http://ticketmaster.com



-- 
Best regards,
 justin                            mailto:[EMAIL PROTECTED]


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to