ID: 26490
Comment by: christian at jul dot net
Reported By: chris dot noden at monstermob dot com
Status: Verified
Bug Type: MySQL related
Operating System: *
PHP Version: 4CVS, 5CVS (2004-03-13)
New Comment:
Happened for me on php 4.3.8 / mysql 4.0.20 / debian unstable
Seems like putting the db connection after the fork solved the problem.
Apparently the connection dies when the connecting process exits, but
should be kept alive as long as there is living child processes.
Previous Comments:
------------------------------------------------------------------------
[2004-08-03 07:27:29] adams at mars-project dot com
I also get this error, but its on an internal mysql server.
PHP 4.3.7
MySQL 4.0.18
FreeBSD 4.10
And just to note when i do get this error i get a php core dump as
well.
------------------------------------------------------------------------
[2004-07-21 17:20:59] florian dot heigl at m4f dot net
I got the same error w/o using php - connecting via bin/mysql...
It only happens *sometimes* :)
ERROR 2013 at line 78: Lost connection to MySQL server during query
OS is Tru64 5.1B-4, MySQL 4.0.20
------------------------------------------------------------------------
[2004-07-20 15:00:52] garak at studenti dot it
Same problem.
Connect to mysql server on LAN.
PHP 4.3.7
MySQL 4.0.20
Linux 2.4.19
------------------------------------------------------------------------
[2004-07-17 09:58:07] jdittmer at ppp0 dot net
Just wanted to say, that I see the very same error with php 4.3.8 and
postgres. (pconnect & connect) System is Debian/GNU Linux
------------------------------------------------------------------------
[2004-07-16 19:51:09] genio at qwest dot net
I've been able to reproduce the error on OpenBSD using php5 and mysql5
alpha. I assumed the error occured due to the fact im using an alpha
release version of mysql, in my case it might not be a php bug because
Im able to reproduce a similar mysql error with a jsp servlet
connection
------------------------------------------------------------------------
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/26490
--
Edit this bug report at http://bugs.php.net/?id=26490&edit=1
