A warning is displayed about the version of the client not matching the server version yet php mysql_get_client_info() and mysql_get_server_info() both return the same correct version.
Logged In: YES
seems to happen frequently, see
I can REPRODUCE when using:
$cfg['Servers'][$i]['extension'] = 'mysql';
$cfg['Servers'][$i]['controluser'] = 'pma';
$cfg['Servers'][$i]['controlpass'] = 'the-correct-pw-should-be-empty';
"Your PHP MySQL library version 5.0.51 differs from your MySQL server version 3.23.32. This may cause unpredictable behavior.
Open new phpMyAdmin window"
with $cfg['Servers'][$i]['extension'] = 'mysqli'; I get:
"Your PHP MySQL library version mysqlnd 5.0.1-beta - 070402 - $Revision: 321 $ differs from your MySQL server version 5.0.51. This may cause unpredictable behavior.
Connection for controluser as defined in your config.inc.php failed."
BUT my phpinfo() says:
mysql - Client API : version 5.0.51
mysqli - Client API library version : mysqlnd 5.0.1-beta - 070402 - $Revision: 321 $
php 5.2.5 on w2k (the other guys in the help forum were on linux).
in pma 3.0.0-dev in both cases (mysql and mysqli) I only get the correct warning:
"Connection for controluser as defined in your configuration failed."
Logged In: YES
Confirmed with 2.11.4, happens only with "mysql" extension. Moved to Bugs.
Fixed in subversion, thanks for reporting.
Logged In: YES
I don't think this is quite closed/fixed yet...
Please note the details in Help Forum thread:
There seem to be 2 separate issues going on at the same time in the proposed fixes; one having to do with controlusers, the other having to do with client & server mismatch. Jurgen's last post on that thread worked on the basis that the setup in question relied on a controluser either being empty or, as listed in the proposed fix by lem9, not being checked anymore in the mysql.dbi file (on line 84).
However, it seems the proposed fix belongs to another help-forum thread entirely, one started by "Martin".
Just to rule out possibilites, I tried it with controluser info uncommented and with very wrong entries, just to force it to choke on the controluser. When I look at PMA that way, it quite correctly complains about the controluser info being wrong... and still has the wrong mysql client version, and still thinks it can't use mysqli. I also tried it with a controluser /correctly/ set, ie, a user that does have appropriate access. PMA 2 used that user connection just fine, but still detected the wrong mysql client version and could not use mysqli. So, the issue remains unchanged if I try it with commented-out controluser info, with uncommmented & empty controluser info, with wrong info and with right info. Thus, whatever I do on controluser info has absolutely no bearing on the issue.
The bottom line is that PMA 2.11.4 is getting its mysql client version data from who-knows-where, for it certainly isn't from the same place that phpinfo() gets it. It surely isn't from the mysql_client_version() or mysqli_client_version() functions alone (both of which report correctly in hand-built php pages), and who knows where it's getting the idea that it can't use mysqli.
Now, the good news is that PMA-3-dev picks up everything just fine: the right mysql server version, client version, and happily uses mysqli. I'm using 3-dev for now.
Looking forward to seeing what actually changed in 2.11.5; hopefully it's more than what lem9 posted because when I tried that, it had absolutely no effect whatsoever.
Logged In: YES
just to clarify:
the MySQL server version is the one which is not detected right, if you have problems with the client version than open a new bug report.
phpMyAdmin uses mysqli, whether the version mismatch is reported or not. (phpMyAdmin does not think it can't use mysqli)
just checkout 2.11.5 from SVN and see if it works now or not. (reporting bugs after release is done is better than no reports - but reporting bugs before release is done helps much more)
kangus, can you confirm that this correcion fixes your problem?
kriscj, this fix is only intended for one issue (mysql extension and wrong control user/password). If PMA still has a problem loading mysqli on your machine, please open another bug report because it's difficult to follow different issues on the same tracker entry.