httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44639] New: Segmentation fault 11 errors right after server started up
Date Wed, 19 Mar 2008 18:42:51 GMT

           Summary: Segmentation fault 11 errors right after server started
           Product: Apache httpd-2
           Version: 2.2.3
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Keywords: ErrorMessage
          Severity: critical
          Priority: P2
         Component: All

I am running Apache 2.2.3 on Solaris 5.9 and the MPM is prefork. I got this
Segmentation fault 11 error right after the Apache started up and the errors
kept going forever.

The only workaround is to start the Apache as non-root user on the port other
than 80, say 8080.

Note, my Solaris uses LDAP as system level user/group authentication (not the
Apache's modules, mod_ldap or mod_auth_ldap for HTTP basic auth). And
everything was working fine using LDAP in previous Apache 1.3. So I wonder if
this issue has anything to do with the support of LDAP as system level
authentication in Apache 2.2.3.

The parent process stayed up and the 5 child processes errored out with
Segfault 11 and then another 5 new child processes were created, then errored
out again...

----httpd-errors log
[Wed Mar 05 14:56:24 2008] [notice] Apache/2.2.3 (Unix) mod_ssl/2.2.3
OpenSSL/0.9.8d configured -- resuming normal operations
[Wed Mar 05 14:56:24 2008] [info] Server built: Oct 31 2007 06:21:59
[Wed Mar 05 14:56:24 2008] [debug] prefork.c(991): AcceptMutex: fcntl (default:
[Wed Mar 05 14:56:25 2008] [notice] child pid 19514 exit signal Segmentation
fault (11), possible coredump in /opt/Apache2
[Wed Mar 05 14:56:25 2008] [notice] child pid 19513 exit signal Segmentation
fault (11), possible coredump in /opt/Apache2
[Wed Mar 05 14:56:25 2008] [notice] child pid 19516 exit signal Segmentation
fault (11)

I added some debuggings in Apache sources and found it failed in getting the
system group privileges (native call - nss_search()). So I am guessing that
each child process was trying to verify the user's group privileges by calling
the native nss_search() but something went wrong during nss_search() that the
child was forced to segfault out.

My questions are:
1. Is there a known issue in Apache 2.x with ldap as os or system level
authentication? Or is it supported?  (Again, it was working fine in previous
Apache 1.3)
2. If I rebuild Apache2 with configure option like "--with-ldap" or
"--enable-ldap", would that help? My understanding of mod_ldap or mod_auth_ldap
is for Apache application level of http basic auth. But curious if this config
option, --with-ldap, would do anything when deal with system level

 I appreciate if any folk here can provide any pointer related to this issue.
 I might be complete wrong with ldap as root cause but curious if anyone
encounter the same error and also using ldap.


--- /etc/nsswitch.conf ---------
passwd:  files  ldap
group:   files  ldap

---Apache Configure options used ---------------------------------
        ./configure \
        --prefix=$TOP/sys/toolkits/http/apache2/installation \
        --with-ssl =/sys/toolkits/http/apache2/openssl/sol \
        --enable-usertrack --enable-unique-id \
        --enable-most --enable-so --enable-vhost-alias \
        --enable-info --enable-access --enable-expires --enable-headers \
        --enable-imagemap --enable-rewrite --enable-speling --enable-cern-meta
        --disable-proxy --disable-log-forensic --enable-mime-magic --enable-ssl

Configure bugmail:
------- 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