<html><P>MySQL server is running on the same machine that I'm trying to get KOHA to run on...is KOHA not going to run on MySQL 5.0? Do I need to install some other program in order for it to work?</P>
<P>Thanks,</P>
<P>Stephon McCray<BR><BR>>-----Original Message-----<BR>>From: Stephen Hedges [mailto:shedges@skemotah.com]<BR>>Sent: Wednesday, November 30, 2005 01:08 PM<BR>>To: 'Stephon McCray'<BR>>Cc: 'koha'<BR>>Subject: Re: [Koha] Help please<BR>><BR>>Here's the official word from MySQL:<BR>><BR>>"MySQL 5.0 uses an authentication protocol based on a password hashing<BR>>algorithm that is incompatible with that used by older (pre-4.1) clients.<BR>>If you upgrade the server from 4.1, attempts to connect to it with an<BR>>older client may fail with the following message:<BR>><BR>>shell> mysql<BR>>Client does not support authentication protocol requested<BR>>by server; consider upgrading MySQL client<BR>><BR>>To solve this problem, you should use one of the following approaches:<BR>><BR>> * Upgrade all client programs to use a 4.1.1 or newer client library.<BR>> * When connecting to the server with a pre-4.1 client program, use an<BR>>account that still has a pre-4.1-style password.<BR>> * Reset the password to pre-4.1 style for each user that needs to use<BR>>a pre-4.1 client program. This can be done using the SET PASSWORD<BR>>statement and the OLD_PASSWORD() function:<BR>><BR>>mysql> SET PASSWORD FOR<BR>> -> 'some_user'@'some_host' = OLD_PASSWORD('newpwd');<BR>><BR>> Alternatively, use UPDATE and FLUSH PRIVILEGES:<BR>><BR>>mysql> UPDATE mysql.user SET Password = OLD_PASSWORD('newpwd')<BR>> -> WHERE Host = 'some_host' AND User = 'some_user';<BR>>mysql> FLUSH PRIVILEGES;<BR>><BR>> Substitute the password you want to use for “newpwd” in the<BR>>preceding examples. MySQL cannot tell you what the original password<BR>>was, so you'll need to pick a new one.<BR>> * Tell the server to use the older password hashing algorithm:<BR>> 1. Start mysqld with the --old-passwords option.<BR>> 2. Assign an old-format password to each account that has had its<BR>>password updated to the longer 4.1 format. You can identify these<BR>>accounts with the following query:<BR>><BR>>mysql> SELECT Host, User, Password FROM mysql.user<BR>> -> WHERE LENGTH(Password) > 16;<BR>><BR>> For each account record displayed by the query, use the Host<BR>>and User values and assign a password using the OLD_PASSWORD()<BR>>function and either SET PASSWORD or UPDATE, as described<BR>>earlier."<BR>><BR>>HTH.<BR>><BR>>Stephen<BR>><BR>>Stephon McCray said:<BR>>> Could someone please help me to understand what's going on and how I can<BR>>> fix it.<BR>>><BR>>> Running a XP professional SP2 machine with MySQL 5 and Apache 2.0.55 and<BR>>> the latest version of Active Perl.<BR>>> [Tue Nov 29 17:41:58 2005] [error] [client 127.0.0.1] Premature end of<BR>>> script headers: mainpage.pl[Tue Nov 29 17:41:58 2005] [error] [client<BR>>> 127.0.0.1] DBI connect('blank224:localhost','koha',...) failed: Client<BR>>> does not support authentication protocol requested by server; consider<BR>>> upgrading MySQL client at c:/usr/koha224/intranet/modules/C4/Context.pm<BR>>> line 411[Tue Nov 29 17:41:58 2005] [error] [client 127.0.0.1] Can't call<BR>>> method "prepare" on an undefined value at<BR>>> c:/usr/koha224/intranet/modules/C4/Koha.pm line 326.Also:[Tue Nov 29<BR>>> 17:41:41 2005] [error] [client 127.0.0.1] Premature end of script headers:<BR>>> opac-main.pl[Tue Nov 29 17:41:41 2005] [error] [client 127.0.0.1] DBI<BR>>> connect('blank224:localhost','koha',...) failed: Client does not support<BR>>> authentication protocol requested by server; consider upgrading MySQL<BR>>> client at c:/usr/koha224/intranet/modules/C4/Context.pm line<BR>>> 411Thanks,Stephon McCrayIT DirectorWestern Academy Charter School<BR>>> _______________________________________________<BR>><BR>><BR>>-- <BR>>Stephen Hedges<BR>>Skemotah Solutions, USA<BR>>www.skemotah.com -- shedges@skemotah.com<BR>><BR>></P></html>