ID: 50356
Comment by: j dot amend at gmail dot com
Reported By: monochromec at gmail dot com
Status: No Feedback
Bug Type: MySQL related
Operating System: Windows 7
PHP Version: 5.2.11
New Comment:
Config:
Windows 7 x64
Apache 2.2.14 x86 using php5_module
PHP 5.3.1 thread safe x86 VC6
MySQL 5.1 x86
Doesn't work:
?php
mysql_connect('localhost');
?
mysql_errno(): 2002
mysql_error(): A connection attempt failed because the connected party
did not properly respond after a period of time, or established
connection failed because connected host has failed to respond.
This works:
?php
mysql_connect('127.0.0.1');
?
I'm thinking this has something to do with IPv6 (localhost is resolving
to ::1 when I ping it).
Clients like mysql's CLI (mysql -h localhost) connect without issues.
Previous Comments:
[2009-12-09 01:00:01] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, 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.
[2009-12-06 12:49:24] jonathan at techcube dot net
Same problem with 64bit windows 7.
Sample code:
http://sg.php.net/manual/en/mysql.examples-basic.php
This would show the problem.
As long as mysql_connect() is present, the problem would occur.
[2009-12-01 21:10:07] paj...@php.net
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with ?php and ends with ?,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.
Please avoid embedding huge scripts into the report.
[2009-12-01 21:02:12] monochromec at gmail dot com
Description:
When executing mysql_connect with 5.2.11 running as a module under
Apache 2.2.14 on a Windows 7 platform, mysql_connect times out and the
browser reports connection reset or similar depending on the used
browser. This behaviour was first observed with phpMyAdmin 3.2.3 (file
library/dbi/mysql.dbi.lib.php, line 38). When changing the invocation
type from module to (f)cgi, the problem disappears. This behaviour is
reproducible with 5.3.1 (vc6-x86). MySQL is version 5.1, client side
5.0.51a (as reported by phpinfo).
Reproduce code:
---
Cf. mysql.dbi.lib.php
--
Edit this bug report at http://bugs.php.net/?id=50356edit=1
