php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #31982 child pid $PID exit signal Segmentation fault (11) Apache 2.0.53
Submitted: 2005-02-15 11:08 UTC Modified: 2005-02-15 17:55 UTC
From: taskazan at metu dot edu dot tr Assigned:
Status: Not a bug Package: Apache2 related
PHP Version: 4.3.10 OS: debian-linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: taskazan at metu dot edu dot tr
New email:
PHP Version: OS:

 

 [2005-02-15 11:08 UTC] taskazan at metu dot edu dot tr
Description:
------------
We have used php4-apache2 series in our web servers without any problems until last week. This week when we upgrade apache2.0.50 to 2.0.53,  httpd processes suddenly get killed by a segfault as seen below in the error_log:
Mon Feb 14 17:14:26 2005] [notice] child pid 16788 exit signal Segmentation fault (11)
[Mon Feb 14 17:14:26 2005] [notice] child pid 16787 exit signal Segmentation fault (11)
[Mon Feb 14 17:14:27 2005] [notice] child pid 16789 exit signal Segmentation fault (11)
[Mon Feb 14 17:14:28 2005] [notice] child pid 16802 exit signal Segmentation fault (11)
[Mon Feb 14 17:14:28 2005] [notice] child pid 16801 exit signal Segmentation fault (11)
[Mon Feb 14 17:14:28 2005] [notice] child pid 16800 exit signal Segmentation fault (11)
[Mon Feb 14 17:14:28 2005] [notice] child pid 16791 exit signal Segmentation fault (11)
...

There is no core file, so we try to debug httpd process with 
gdb. Here is the outputs:

# gdb /usr/local/httpd-2.0.53/bin/httpd
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...

(gdb) run -X
Starting program: /usr/local/httpd-2.0.53/bin/httpd -X

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 27979)]
apr_proc_mutex_child_init (mutex=0x4, fname=0x821dd98 "\xef\xbf\xbd031\b", pool=0x821dd
98)
    at proc_mutex.c:818
818     proc_mutex.c: No such file or directory.
        in proc_mutex.c

(gdb) bt
#0  apr_proc_mutex_child_init (mutex=0x4, fname=0x821dd98 "\xef\xbf\xbd031\b", pool=0x821dd98)
    at proc_mutex.c:818
#1  0x4014abd2 in apr_global_mutex_child_init mutex=0x821dd98,
fname=0x821dd98 "\xef\xbf\xbd031\b", pool=0x821dd98) at global_mutex.c:88
#2  0x0807f986 in util_ldap_child_init (p=0x821dd98, s=0x81d86d0) at util_ldap.c:1615
#3  0x080bb90d in ap_run_child_init (pchild=0x821dd98, s=0x81d86d0) at config.c:150
#4  0x080b901f in child_main (child_num_arg=136437144) at worker.c:1104
#5  0x080b93a6 in make_child (s=0x821dd98, slot=0) at worker.c:1248
#6  0x080b9439 in startup_children (number_to_start=0) at worker.c:1302
#7  0x080b9e7a in ap_mpm_run (_pconf=0x819b4f8, plog=0x81d35d8, s=0x0)
    at worker.c:1617
#8  0x080c113f in main (argc=2, argv=0xbffffc74) at main.c:618
(gdb)

Can anybody know what to do?

Yours,

feyza




Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-02-15 14:20 UTC] taskazan at metu dot edu dot tr
when we try the latest snapshot, given in the previous link, 
we saw segmentation fault in the error log again.

When we debug the httpd process, again we get following logs:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 10502)]
apr_proc_mutex_child_init (mutex=0x4, fname=0x821ee08 "�031\b", 
    pool=0x821ee08) at proc_mutex.c:818
818     proc_mutex.c: No such file or directory.
        in proc_mutex.c
(gdb) bt
#0  apr_proc_mutex_child_init (mutex=0x4, fname=0x821ee08 "�031\b", 
    pool=0x821ee08) at proc_mutex.c:818
#1  0x4014abd2 in apr_global_mutex_child_init (mutex=0x821ee08, 
    fname=0x821ee08 "�031\b", pool=0x821ee08) at global_mutex.c:88
#2  0x0807f986 in util_ldap_child_init (p=0x821ee08, s=0x81d86d0)
    at util_ldap.c:1615
#3  0x080bb90d in ap_run_child_init (pchild=0x821ee08, s=0x81d86d0)
    at config.c:150
#4  0x080b901f in child_main (child_num_arg=136441352) at worker.c:1104
#5  0x080b93a6 in make_child (s=0x821ee08, slot=0) at worker.c:1248
#6  0x080b9439 in startup_children (number_to_start=0) at worker.c:1302
#7  0x080b9e7a in ap_mpm_run (_pconf=0x819b4f8, plog=0x81d35d8, s=0x0)
    at worker.c:1617
#8  0x080c113f in main (argc=2, argv=0xbffffc64) at main.c:618
 [2005-02-15 17:55 UTC] jorton@php.net
Thank you for taking the time to report a problem with PHP.
Unfortunately you are not using a current version of PHP -- 
the problem might already be fixed. Please download a new
PHP version from http://www.php.net/downloads.php

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PHP.

Per ASF bugzilla, this is a mod_ldap bug.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Fri Mar 01 16:01:31 2024 UTC