PHP error mysql_pconnect()

[jetheller]

Has anyone else received this error?

PHP Fatal error: Call to undefined function: mysql_pconnect() in /var/www/html/zm/zm_db.php on line 21

I am running Core 3, but have upgraded mysql to 4.1. I'm running the mysql-compat libs and php 4.3.9 and I have php-mysql 4.3.9 installed.

Anyone know what I'm missing?

Thanks

[zoneminder]

It's always worth doing a search on the forums. Check this thread from yesterday.

Phil

[jetheller]

Thanks, but I've read that. His problem was he didn't have mysql-php installed. Mine is installed. In fact, yum just updated it for me:

Dependencies Resolved
Transaction Listing:
Update: php-mysql.i386 0:4.3.10-3.2

Performing the following to resolve dependencies:
Update: php.i386 0:4.3.10-3.2
Update: php-ldap.i386 0:4.3.10-3.2
Update: php-pear.i386 0:4.3.10-3.2

[jetheller]

The problem has to be that somehow, since I installed CORE 3 with php, but without mysql or php-mysql, that php was installed with --without-mysql. So I'll try to remove all of php and try again. I'll post an update to my results for posterities sake.

[zoneminder]

Try creating a simple script that just has

<?php

phpinfo();

?>

in it and then accessing that. You should gets lots of debug but if you search for mysql then you should see what the compile options were. Ordinarily I think it should be 'shared' but maybe you have something else.

The other reason this sometimes happens is if you have an old version of mysql which supports the mysql_connect call but not mysql_pconnect but if you have FC3 I doubt this is the case. Unless you've done an upgrade and have two versions in different places and the wrong one is being picked up.

Phil

[jetheller]

Well the fun never stops. I wasn't able to call my test script from apache, but I could run it on the command line. It appears that mysql is enabled. I then tried to put the mysql_pconnect string in my test script and run it from the command line (php test.php).:

PHP Warning: mysql_pconnect(): Client does not support authentication protocol requested by server; consider upgrading MySQL client in /var/www/html/test.php on line 3
Content-type: text/html
X-Powered-By: PHP/4.3.10

Could not connect to database: Client does not support authentication protocol requested by server; consider upgrading MySQL client[

And that looks nothing like what I get in /var/log/httpd/error
[client 127.0.0.1] PHP Fatal error: Call to undefined function: mysql_pconnect() in /var/www/html/zm/zm_db.php on line 21

I haven't a clue what is up or even where to start, except that maybe apache isn't configured to use php (but then wouldn't it crach before the db call?).

[jetheller]

Okay, for the records, the problem was that apache was not configured to run php. So a mysql_pconnect can also mean that.

But I now get the much more comprehendable error

[client xxx.xxx.xxx.xxx] PHP Warning: mysql_pconnect(): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13) in /var/www/html/zm/zm_db.php on line 21

Which I stand a much better chance of resolving.

Cheers

[zoneminder]

This will be one of two things usually,

1) Mysql is not running
2) Sometimes the apache/php/mysql library is built with a different idea of where the socket is than mysql itself. You may need to symlink the location where mysql.sock really is (/tmp?) to that which the libraries are trying to find.

Phil

[jetheller]

Both mysqld_safe and mysqld-max are running. And the only "mysql.sock" searching from / is /var/lib/mysql/mysql.sock.

There is a chance it could be some confusion on the domain name. I use a domain forwarding that is my domain, but my box thinks it is localhost.

So I hardcoded zm_db.php to hit 127.0.0.1 instead of the ZM_DB_SERVER and then made sure my user had priveleges from 127.0.0.1 and then I get a "Could not connect to database: localhostzoneminderzoneminderClient does not support authentication protocol requested by server; consider upgrading MySQL client"

So it appears I'm back to where I started. php 4.3.10 wants to use the old libmysqlclient.so.10 lib. MySQL 4.1 uses libmysqlclient.so.13. So I used mysql-shared-compat which didn't fix the problem, just made it a lot harder to figure out what it was.

So unless I hear otherwise, the moral of this story is that PHP 4.3 with MySQL 4.1 will not work, even if you use shared-compat. I still have enough drive in me to try php5, but after that, I throw in the towel and go back to MySQL 3.+


Thanks for the help, I really appreciate it.

[zoneminder]

I think you can work around the 'authentication protocol' message but I can't remember how. See if a search turns up something.

Phil

[jetheller]

The solution was to install php5. That took me a while as I'm not exactly a well seasoned sysadmin. But since php5 used the native client libs for mysql4.1 the new zoneminder install went sweet like butta. Now I can merryly peep in on my wife while I'm at work and feel safe that I'll be alerted the instant an intruder enters my house when we're out. Of course I had all that before I got a hair up my arse to move to mysql4.1 and this mess was just so I could enjoy the mysql-administrator, but just think of all that I learned [read lots of sarcasm here].

Anyways, I'm off to the tip jar, thanks for the great product and surprisingly kick ass support.

[angelhod]

i had the same problem, it started after i rebuilded apache and php again.....
the solution:
it is taken from mysql website - http://dev.mysql.com/doc/mysql/en/old-client.html

A.2.3. Client does not support authentication protocol
MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to connect to it with an older client may fail with the following message:

shell> mysql
Client does not support authentication protocol requested
by server; consider upgrading MySQL client

To solve this problem, you should use one of the following approaches:

Upgrade all client programs to use a 4.1.1 or newer client library.

When connecting to the server with a pre-4.1 client program, use an account that still has a pre-4.1-style password.

Reset the password to pre-4.1 style for each user that needs to use a pre-4.1 client program. This can be done using the SET PASSWORD statement and the OLD_PASSWORD() function:

mysql> SET PASSWORD FOR
-> 'some_user'@'some_host' = OLD_PASSWORD('newpwd');

Alternatively, use UPDATE and FLUSH PRIVILEGES:

mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd')
-> WHERE Host = 'some_host' AND User = 'some_user';
mysql> FLUSH PRIVILEGES;

Substitute the password you want to use for ``newpwd'' in the preceding examples. MySQL cannot tell you what the original password was, so you'll need to pick a new one.

Tell the server to use the older password hashing algorithm:

Start mysqld with the --old-passwords option.

Assign an old-format password to each account that has had its password updated to the longer 4.1 format. You can identify these accounts with the following query:

mysql> SELECT Host, User, Password FROM mysql.user
-> WHERE LENGTH(Password) > 16;

For each account record displayed by the query, use the Host and User values and assign a password using the OLD_PASSWORD() function and either SET PASSWORD or UPDATE, as described earlier.

Note: In PHP, the mysql extension does not support the new authentication protocol in MySQL 4.1.1 and higher. This is true regardless of the PHP version being used. If you wish to use the mysql extension with MySQL 4.1 or newer, you will need to follow one of the options discussed above for configuring MySQL to work with old clients. The mysqli extension (stands for "MySQL, Improved"; new in PHP 5) is compatible with the improved password hashing employed in MySQL 4.1 and higher, and no special configuration of MySQL need be done in order to use this newer MySQL client library for PHP. For more information about the mysqli extension, see http://php.net/mysqli.

For additional background on password hashing and authentication, see Section 5.6.9, “Password Hashing in MySQL 4.1”.

Previous / Next / Up / Table of Contents
User Comments
Posted by Dan Beatty on February 2 2005 3:28pm [Delete] [Edit]

After hours of searching, it appears (in spite of all of the information that suggests this is an upgrade
issue) that it really is a PHP support issue. I'm using PHP 4.3.9, so maybe PHP 5.0 has addressed
this, but I haven't had time to wade into that.

So I settled for using the old 16-byte password encryption.

In my.ini file in the mySQL directory (e.g., C:\Program Files\MySQL\my.ini), add the following :

#Use old password encryption method
old_passwords

Save and close the file. Where you add these lines really doesn?t seem to matter, but most of what
I read said to put them in the [mysqld] section.

If you use phpAdmin there are further issues. See mglatts's post on 7 Jan 2005 for discussion of those at
http://forums.mysql.com/read.php?11,640 ... #msg-10611 <http://forums.mysql.com/read.php?11,6400,10611>.



Posted by Bob Stein on March 8 2005 9:57pm [Delete] [Edit]

I had this error from PHP mysql_connect(host, user, password). I thought it was a red herring for a long time because a gibberish password would give it too. But no, it really appears to be an issue with higher security passwords. Further confusing the issue, different users can have different potency passwords. What works via mysql command-line might not work via PHP. Find out which flavor of password you've got with:

SHOW GRANTS;

You'll see 32 hexadecimal digits in the scrambled password on a user that's victimized by the error message. You can reduce this to 16 digits -- and make the error go away -- by reassigning a low-tech password to the user account, using the instructions above (the OLD_PASSWORD() function). As Dan says, PHP 4 appears to be compatible only with the older password scheme.


Posted by [name withheld] on March 29 2005 6:51pm [Delete] [Edit]

Also, if you've already set the password, watch carefully, because it will match but not update the user record if you're trying to set it using these commands to the same password. you have to first change it to a temporary password, then use the old_password command to set your password in.


Add your own comment.