From f6d4395710e88c108882a1d94e89f813d8e3f452 Mon Sep 17 00:00:00 2001 From: "travis%sedsystems.ca" <> Date: Sat, 5 Feb 2005 12:31:46 +0000 Subject: Bug 258494 : checksetup fails with out-of-sync DBD::mysql modues - document fix and workaround Patch by Shane H. W. Travis r=justdave --- docs/xml/troubleshooting.xml | 27 ++++++++++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/xml/troubleshooting.xml b/docs/xml/troubleshooting.xml index 844f06c50..e3b54b6e8 100644 --- a/docs/xml/troubleshooting.xml +++ b/docs/xml/troubleshooting.xml @@ -1,5 +1,5 @@ - + Troubleshooting @@ -305,6 +305,31 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233. +
+ + checksetup.pl reports "Client does not support authentication protocol + requested by server..." + + + + This error is occurring because you are using the new password + encryption that comes with MySQL 4.1, while your + DBD::mysql module was compiled against an + older version of MySQL. If you recompile DBD::mysql + against the current MySQL libraries (or just obtain a newer version + of this module) then the error may go away. + + + + If that does not fix the problem, or if you cannot recompile the + existing module (e.g. you're running Windows) and/or don't want to + replace it (e.g. you want to keep using a packaged version), then a + workaround is available from the MySQL docs: + + + +
+