On the DB server machine, i have MySQL 4.1.3beta running for testing upgrading, but MySQL 4.0.2 is also running (production).
I can connect locally on the DB server through various clients, and have permissions as needed. But when i try to connect via a web server, i get various connect errors based on the params i pass. The error that is telling me the most is:
DBI connect(...) failed: Client does not support authentication protocol requested by server; consider upgrading MySQL client at <script line XXX>
But, i upgraded the DBI to 1.43, and the MySQL DBD to 2.9004 on both the DB server and the webserver (DB client). What im thinking the problem is: the webserver is running MySQL for other apps, and the DBD is built based on that MySQL, which is pre 4.1 series, so it doesnt understand the new MySQL auth protocols. (Note the webserver is running Perl 5.6.1)
But, i didnt think that the DBD was built based on a MySQL server, because the rest of the webservers in the pool dont run MySQL, but i can still install the DBI and DBD. So im at a loss here. Can i tell the DBD to build based on the DB servers MySQL install, or does that question not even make sense?
Note: I absolutely cannot upgrade mysql or Perl on the webserver.
In reply to DBI/DBD mysql upgrade woes by shemp
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |