Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12875
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4149C952.2070507@hristov.com>
Date: Thu, 16 Sep 2004 19:11:46 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a3) Gecko/20040817
MIME-Version: 1.0
To: Sam Hobbs <SoCalSam@GMail.com>,  internals@lists.php.net
References: <20040916040105.25425.qmail@pb1.pair.com> <Pine.LNX.4.58.0409152141160.1427@t42p.lerdorf.com> <20040916170712.94973.qmail@pb1.pair.com>
In-Reply-To: <20040916170712.94973.qmail@pb1.pair.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] mysql_connect using version 5.0.1 accesses the internet
 when host and client are the same system
From: php@hristov.com (Andrey Hristov)

Sam Hobbs wrote:
> "Rasmus Lerdorf" <rasmus@php.net> wrote in message 
> news:Pine.LNX.4.58.0409152141160.1427@t42p.lerdorf.com...
> 
>>I am not sure why you assume this to be a PHP problem.
> 
> 
> I thought I was being reasonable. I thought I was clear about saying I was 
> not sure it is a PHP problem. I was trying to help by helping diagnose a 
> problem. If it is not a problem then you could say so in a more reasonable 
> manner. If you always react to people this way when they are trying to help 
> then you will have an inferior product since you discourage people from 
> helping.
> 
> I am not assuming; that is why I am asking this question. You really can say 
> the same thing except without the emotions. You can simply state the fact 
> that as far as you know it is not a PHP problem. It really, really helps to 
> keep in mind that it is better to simply state facts. That keeps things less 
> emotional and generally keeps things at a more reasonable level.
> 
> 
>>Sounds like your
>>firewall is blocking both local and external connections.  Can you telnet
>>to port 10061 on localhost with the firewall enabled?
> 
> 
> I think the PHP messages need to be documented. It is unclear whether 10061 
> is a port or an error code. Are you sure it is a port? I am not aware of 
> MySQL using port 10061. I did not change anything to specify port 10061 and 
> this is a fresh install of MySQL.
> 
> Again, if you think that what I described sounds like it is normal behavior, 
> then simply saying so helps a lot. If it is normal behavior, then it would 
> probably help a lot of people to say so somewhere.
> 
> One reason I say that the PHP messages need to be documented better is 
> indicated by all the many others with the same problem. If you search for:
> 
>     +mysql_connect +10061
> 
> You will find many web sites that have that error. It is a common problem 
> that many people are encountering and it appears that many people don't know 
> how to solve it; their web sites are down. Many of the other results are 
> from people asking about the problem and it is not clear how many of them 
> have not solved the problem. It appears that many have not.
> 
AFAIK this is _not_ a PHP error message. You see it thrown by ext/mysql however
it comes from the underlying libmysql. Therefore all scripting and non-scripting
languages relying on this library will show you the same error. I hope you have
read the appendix of the mysql manual where it is stated that users may have
problem connecting to mysql over tcp/ip under windows if they have enabled
firewall software like ZoneAlarm or Windows Personal Firewall. In this case either
don't do tcp/ip and enable windows pipes, which are faster (i saw today a
synthetic benchmark which stated that they are 3x faster), or allow connections
to 3306.

Andrey