[Koha] Help please

[Stephon McCray]

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?
Thanks,
Stephon McCray

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20051205/1d0fa1d1/attachment.html