ilan
Verified User
We have been working fine for a very long time, but just now something happened and now the MySQL Management on DA doesn't work. With every user including the admin, we receive the same error message:
Error connecting to MySQL: Client does not support authentication protocol requested by server; consider upgrading MySQL client
Our server has mysql 4.1.21 and php 5.2.5 compiled for client API version 4.1.21 (many posts mention a difference on the php client as a source for the problem, but apparently that's not our case) and we have DA ver 1.37.0, on a RH 7.3 server.
The strange thing is that php does communicate fine with mysql, all our clients' sites are up and running, and phpmyadmin lets us connect to all databases with no fuss, so apparently there's no problem with new/old passwords (all our passwords are under the new schema, which was also mentioned in some posts).
We are also able to connect to the database using the credentials at:
/usr/local/directadmin/conf/mysql.conf so that's also ruled out.
There are no error messages in the mysqld.log, /usr/local/directadmin/error.log and messages.log , and we haven't upgraded software lately.
The last thing we did before we noticed the error is that we ran the script change_database_username.php to change the username of one of our clients which didn't rename all the databases and that's how we discovered the problem with DA (when we tried to enter the administration to create the databases manually).
Any ideas?
Ilan
Error connecting to MySQL: Client does not support authentication protocol requested by server; consider upgrading MySQL client
Our server has mysql 4.1.21 and php 5.2.5 compiled for client API version 4.1.21 (many posts mention a difference on the php client as a source for the problem, but apparently that's not our case) and we have DA ver 1.37.0, on a RH 7.3 server.
The strange thing is that php does communicate fine with mysql, all our clients' sites are up and running, and phpmyadmin lets us connect to all databases with no fuss, so apparently there's no problem with new/old passwords (all our passwords are under the new schema, which was also mentioned in some posts).
We are also able to connect to the database using the credentials at:
/usr/local/directadmin/conf/mysql.conf so that's also ruled out.
There are no error messages in the mysqld.log, /usr/local/directadmin/error.log and messages.log , and we haven't upgraded software lately.
The last thing we did before we noticed the error is that we ran the script change_database_username.php to change the username of one of our clients which didn't rename all the databases and that's how we discovered the problem with DA (when we tried to enter the administration to create the databases manually).
Any ideas?
Ilan