www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Begley <d.beg...@uws.edu.au>
Subject general/10129: "ExtendedStatus On" causes Apache to crash on startup
Date Mon, 11 Mar 2002 13:15:46 GMT

>Number:         10129
>Category:       general
>Synopsis:       "ExtendedStatus On" causes Apache to crash on startup
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Mar 11 05:20:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     d.begley@uws.edu.au
>Release:        2.0.32
>Organization:
apache
>Environment:
Operating System:
  Sun Solaris 2.7 (SPARC)
Compiler:
  GNU CC (gcc) 2.8.1
Additional Third-Party Apache Modules:
  (none)
>Description:
Apache configured/built as per:

$ CC="gcc" ; CFLAGS="-O -pipe -g" ; LDFLAGS="-g" ; export CC CFLAGS LDFLAGS
$ ./configure \
> --disable-shared --enable-so --enable-info --enable-status \
> --enable-dav --enable-dav-fs --enable-expires --enable-rewrite \
> --prefix=/opt/cwis

With "ExtendedStatus On" in httpd.conf, Apache/2.0.28 works but 2.0.32 core
dumps;  error_log reports:

  seg fault or similar nasty error detected in the parent process

Running GDB over the core file reports:

#0  0x6b0dc in ap_update_child_status_from_indexes (child_num=0, thread_num=0,
    status=1, r=0x0) at scoreboard.c:415
415             if (status == SERVER_READY || status == SERVER_DEAD) {
(gdb) backtrace
#0  0x6b0dc in ap_update_child_status_from_indexes (child_num=0, thread_num=0,
    status=1, r=0x0) at scoreboard.c:415
#1  0x5cc78 in make_child (s=0x17d6c0, slot=0) at prefork.c:756
#2  0x5cd90 in startup_children (number_to_start=5) at prefork.c:830
#3  0x5d0c0 in ap_mpm_run (_pconf=0x5, plog=0x128680, s=0x17d6c0)
    at prefork.c:1021
#4  0x62b1c in main (argc=1562304, argv=0xe8600) at main.c:501

The (for now) work-around is to disable extended status reporting - Apache is
then able to successfully fire-up and start answering queries.

Basic Apache compilation/configuration information:

# ./httpd -V
Server version: Apache/2.0.32
Server built:   Mar 11 2002 23:05:40
Server's Module Magic Number: 20020128:0
Architecture:   32-bit
Server compiled with....
 -D APACHE_MPM_DIR="server/mpm/prefork"
 -D APR_HAS_MMAP
 -D APR_USE_FCNTL_SERIALIZE
 -D APR_USE_PTHREAD_SERIALIZE
 -D APR_HAS_OTHER_CHILD
 -D AP_HAVE_RELIABLE_PIPED_LOGS
 -D HTTPD_ROOT="/opt/cwis"
 -D SUEXEC_BIN="/opt/cwis/bin/suexec"
 -D DEFAULT_ERRORLOG="logs/error_log"
 -D SERVER_CONFIG_FILE="conf/httpd.conf"

Any additional information required?
>How-To-Repeat:
No URL necessary - Apache doesn't even manage to start-up in the first place.
>Fix:
As above - the temporary work-around is to disable extended status reporting;
longer-term, however, this is an unacceptable "solution".
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 


Mime
View raw message