mysql connecting OK on 127.0.0.1 but not localhost

[Anon]

Hi,

Here's a strange one for you...

I have an existing PHP installation statically compiled into apache that connects to a mySQL database using "localhost".

I just created a new PHP/mysql CGI executable, and the same scripts no longer connect.

If I change mysql_connect("localhost", "username", "password") to mysql_connect("127.0.0.1", "username", "password") the scripts will work again.

gethostbyname("localhost") returns 127.0.0.1, so PHP can do the translation. It is as if mySQL is denying access...but the same mySQL server allows the same usernames in the same scripts running under the other PHP installation.

Any ideas are appreciated.

Scott

[Anon]

Print the error message that Mysql gives you in PHP ans see what the exact error is.

[Anon]

change the line in your apache httpd.conf file to from:

ServerName 127.0.0.1 to:
ServerName localhost

Save the changes, and restart the server....

Andrew Heebner
[e-mail]
http://evilwalrus.com

[Anon]

Thanks for the reply.

Unfortunately, that's not the problem, because:

a) I'm compiling PHP as a CGI, and testing it directly on the command line.

b) I don't have any Servername 127.0.0.1 entry in my httpd.conf anyway.

So to summarise my problem, I have a PHP/mySQL compiled binary that I am testing on the command line (to simplify things).

It will connect to databases if I specify 127.0.0.1 as the servername parameter in mysql_connect(). It will spit the dummy if I call it "localhost".

The same scripts (using 'localhost') work fine under my production version of PHP (compiled many moons ago - I wish I could work out what I did differently).

When trying to connect to localhost, PHP returns this error:
<b>Warning</b>: MySQL Connection Failed: Can't connect to local MySQL server
in <b>test-mysql.php</b> on line <b>2</b><br>
where line 2 is the mysql_connect statement.

mysql_error() and mysql_errno() returns NULL.

Thanks anyway :-)

Scott.

[Anon]

Does your production PHP use the same MySQL server as the PHP that is giving you problems?

[Anon]

Yes, it is using the same mySQL server.

The production PHP is running as a statically compiled apache module, while my test PHP is currently compiled as a CGI binary (to simplify things).

The mySQL server I am attempting to connect to is the production mySQL server, which happily accepts localhost connections from other scripts now.

Strange one, this.

Vincent wrote:

Does your production PHP use the same MySQL server as the PHP that is giving you problems?

[Anon]

I have figured it out.

This may help other users with similar problems.

It appears that the mySQL libraries were for a different version of mySQL.

I have mySQL 3.22.32 running, so I reinstalled the mySQL-devel RPM for that version of mySQL.

On recompiling PHP, the 'localhost' problem disappeared.

I was hinted to the solution by reading the PHP4 installation docs. They mention that you should specify the include path of your mySQL libraries rather than using the built in code if you plan on running the server module concurrently with other server modules. I wondered whether the libraries were a different version to the server.

Thanks for everyone's help!

Scott.

[Anon]

Confirming that scott is right...

i'm using debian, and installed mysql with the hand... then installed php and all the other things.... then we did a install op proftpd-mysql with apt-get... and that imported a new mysql client librarie...

it's kind of weird... you can update your mysql without doing php.. and this doesn't work...

anybody can explain this?