#16272 [Com]: SegFault in MySQL

From: Date: Sun, 20 Oct 2002 22:59:30 +0000
Subject: #16272 [Com]: SegFault in MySQL
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-22898@lists.php.net to get a copy of this message
 ID:               16272
 Comment by:       shanti@mojo.cc
 Reported By:      jweiss@greyzone.com
 Status:           No Feedback
 Bug Type:         MySQL related
 Operating System: Linux 2.4.x
 PHP Version:      4.1.2
 New Comment:

hi people,

i cant get a rest .. this issue just took me weeks for now .. is there
some new knowledge around about this BUG? well ist it one .. is it just
bad php-code .. i am totally lost in this issue .. plz anybody gives
more info and a status about this .. i touched this problem using
latest version am xams(.sourgeforge.net) .. its annoying


Previous Comments:
------------------------------------------------------------------------

[2002-10-02 01:12:50] odysseus@soa.co.nz

Getting the same problems as the last poster - lots of SIGSEGVs then
the apache processes seem to hang - can't get any data out of them.

------------------------------------------------------------------------

[2002-08-12 06:37:18] bartvb@iae.nl

Please change the status of this bug..

This bug is really bothering me, all my users are affected by this bug
because it gives them empty pages :\

Here's a snippet from my errorlog:

[Mon Aug 12 12:01:16 2002] [notice] child pid 20887 exit signal
Segmentation fault (11)
[Mon Aug 12 12:03:09 2002] [notice] child pid 20929 exit signal
Segmentation fault (11)
[Mon Aug 12 12:03:28 2002] [notice] child pid 20938 exit signal
Segmentation fault (11)
[Mon Aug 12 12:05:09 2002] [notice] child pid 20562 exit signal
Segmentation fault (11)
[Mon Aug 12 12:05:18 2002] [notice] child pid 21044 exit signal
Segmentation fault (11)
[Mon Aug 12 12:06:30 2002] [notice] child pid 20925 exit signal
Segmentation fault (11)
[Mon Aug 12 12:07:07 2002] [notice] child pid 21078 exit signal
Segmentation fault (11)
[Mon Aug 12 12:07:13 2002] [notice] child pid 21086 exit signal
Segmentation fault (11)
[Mon Aug 12 12:07:17 2002] [notice] child pid 20559 exit signal
Segmentation fault (11)
[Mon Aug 12 12:07:29 2002] [notice] child pid 21091 exit signal
Segmentation fault (11)
[Mon Aug 12 12:07:37 2002] [notice] child pid 21094 exit signal
Segmentation fault (11)
[Mon Aug 12 12:10:19 2002] [notice] child pid 21237 exit signal
Segmentation fault (11)
[Mon Aug 12 12:10:26 2002] [notice] child pid 21240 exit signal
Segmentation fault (11)
[Mon Aug 12 12:10:57 2002] [notice] child pid 21249 exit signal
Segmentation fault (11)


Mainly using phpBB 2.0.1 on that site. Furthermore I'm using PHP
version 4.2.2 on Linux 2.4.18-5, Apache/1.3.26 with MySQL 3.23.47.
See http://www.bokt.nl/klad/info.php for phpinfo().

------------------------------------------------------------------------

[2002-08-07 13:42:16] db@dbinteractive.com

I don't know if my uneducated comment will really contribute to the
understanding of this bug, but I'll offer it up anyway:

I encountered the same problem with the exact same Apache/PHP/MySQL
setup as b0nfire@fdns.net. When I changed the connection type from
persistent (using mysql_pconnect) to a regular MySQL connection (using
mysql_connect), the problem went away--the script worked fine and no
further segfaults appeared in the http error log.

If others find the same results, then it may be safe to assume the
problem is limited to persistent connections only.

------------------------------------------------------------------------

[2002-07-26 01:00:10] php-bugs@lists.php.net

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

------------------------------------------------------------------------

[2002-06-25 13:27:51] sniper@php.net

Please try this snapshot:

http://snaps.php.net/php4-latest.tar.gz


------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/16272

-- 
Edit this bug report at http://bugs.php.net/?id=16272&edit=1



Thread (22 messages)

« previous php.bugs (#22898) next »