httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53329] New: Segmentation fault in ap_mpm_pod_check() method
Date Wed, 30 May 2012 13:11:55 GMT

          Priority: P2
            Bug ID: 53329
           Summary: Segmentation fault in ap_mpm_pod_check() method
          Severity: critical
    Classification: Unclassified
                OS: Solaris
          Hardware: Sun
            Status: NEW
           Version: 2.2.22
         Component: mpm_worker
           Product: Apache httpd-2

Apache httpd consistently crashing on Solaris SPARC. The processes are OK
during one week. But some day, the processes are dying almost every minute. It
has been found, that it is during read() operation in
mpm_worker:ap_mpm_pod_check() method. 

I use the last 2.2 version:
/opt/csw/apache2/sbin/httpd -V
Server version: Apache/2.2.22 (Unix)
Server built:   Apr 14 2012 04:26:36
Server's Module Magic Number: 20051115:30
Server loaded:  APR 1.4.5, APR-Util 1.3.12
Compiled using: APR 1.4.6, APR-Util 1.3.12
Architecture:   32-bit
Server MPM:     Worker
  threaded:     yes (fixed thread count)
    forked:     yes (variable process count)
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/worker"
 -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
 -D HTTPD_ROOT="/opt/csw/apache2"
 -D SUEXEC_BIN="/opt/csw/apache2/bin/suexec"
 -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D AP_TYPES_CONFIG_FILE="etc/mime.types"
 -D SERVER_CONFIG_FILE="etc/httpd.conf"

There is always only one line at the time of crash at error log:
[Wed May 30 12:40:32 2012] [notice] child pid 13661 exit signal Segmentation
fault (11), possible coredump in /opt/csw/apache2

pstack of coredump contains message about zombie:
-----------------  lwp# 2 / thread# 2  --------------------
 ff123468 dummy_worker(), exit value = 0x00000000
    ** zombie (exited, not detached, not yet joined) **

callstack retrieved from coredump by dbx:
current thread: t@1
=>[1], 0xffbff70b, 0x1, 0x0, 0xffbff630, 0x1), at
  [2], 0xffbff70b, 0x1, 0x0, 0x1cf4, 0x9), at 0xfedbbaa4 
  [3] httpd.worker:ap_mpm_pod_check(0x197e50, 0x50610, 0x2, 0x0, 0x0, 0x1), at
  [4] 0x51698(0x0, 0x1d4c1, 0x7f284, 0x7c790, 0x7f278, 0xb4268), at 0x51698 
  [5] 0x5181c(0x8bf88, 0x0, 0xffffffff, 0x0, 0x7c400, 0x0), at 0x5181c 
  [6] 0x51f14(0x0, 0x1, 0x1, 0x1, 0x7400, 0x0), at 0x51f14 
  [7] 0x52208(0x0, 0x0, 0xffffffff, 0x80, 0xffbff938, 0xffbff948), at 0x52208 
  [8] httpd.worker:ap_mpm_run(0x0, 0xfffffe99, 0x99, 0x7c768, 0x7f26c,
0x7f400), at 0x524d0 
  [9] httpd.worker:main(0x7b3d8, 0x7c400, 0x46c80, 0x7c5dc, 0xffbffa28,
0x7c5ec), at 0x2a34c 

I'm not sure, but it may be the same problem as in bug 52510.

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message