Client authentication error -- suddenly

Howdy, folks,

I'm running MySQL 4.1.7 on a Red Hat 9 box, and this morning,
abruptly, I started receiving this error (specifics replaced for
security purposes):

DBI connect('DATABASE:IP','USER',...) failed: Client does not support
authentication protocol requested by server; consider upgrading MySQL
client at [script path]

I had 2.9003 installed and installed 2.9005_3 in case that was the
problem. I had DBI 1.40 installed and upgraded to 1.45, as well. I
cannot seem to get this to work.

I checked the MySQL documentation and tried to switch to "old
passwords" to see if that helped. No luck.

I can't figure out why this suddenly happened at 6 am with me being
the only person with access to the databases and the Web server, and
not making any changes.

I had just stopped a large MySQL select operation that had been
running for 12 hours. But it was running on another instance of MySQL
-- I have two instances at different ports with different paths
running.

Any help is very very welcome, as my system is currently down.

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org

Re: Client authentication error -- suddenly

Sounds like you mysql server verion got upgraded / you are running
different server versions on different ports (and different data
hopefully!).

MySQL server 4+ requires clients of 4+ (as far as I know).

Upgrade your client or downgrade your server.

P.S. After killing a job, 'check table' can be usefull :)

Dan.

On Mon, 8 Nov 2004, Glenn Fleishman wrote:

>Howdy, folks,
>
>I'm running MySQL 4.1.7 on a Red Hat 9 box, and this morning,
>abruptly, I started receiving this error (specifics replaced for
>security purposes):
>
>DBI connect('DATABASE:IP','USER',...) failed: Client does not support
>authentication protocol requested by server; consider upgrading MySQL
>client at [script path]
>
>I had 2.9003 installed and installed 2.9005_3 in case that was the
>problem. I had DBI 1.40 installed and upgraded to 1.45, as well. I
>cannot seem to get this to work.
>
>I checked the MySQL documentation and tried to switch to "old
>passwords" to see if that helped. No luck.
>
>I can't figure out why this suddenly happened at 6 am with me being
>the only person with access to the databases and the Web server, and
>not making any changes.
>
>I had just stopped a large MySQL select operation that had been
>running for 12 hours. But it was running on another instance of MySQL
>-- I have two instances at different ports with different paths
>running.
>
>Any help is very very welcome, as my system is currently down.
>
>


--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules@m .gmane.org

Re: Client authentication error -- suddenly

>Sounds like you mysql server verion got upgraded / you are running
>different server versions on different ports (and different data
>hopefully!).
>
>MySQL server 4+ requires clients of 4+ (as far as I know).
>
>Upgrade your client or downgrade your server.
>
>P.S. After killing a job, 'check table' can be usefull :)

No, I'm running the same server I was before this happened. I run my own
servers.

I have had 4.1.7 running as both instances. i can confirm this via
phpMyAdmin that the version numbers are the same.

I'm still baffled. It looks like my second instance is the one having
problems, and that's the one on which I killed a massive SELECT
operation. It may not be the perl interface at all, but I can access
that database through command-line MySQL and through PHP. Perl is the
only part that's failing, and not on my first instance of MySQL.

It's very weird. I rebooted both the Web server and MySQL servers just
to be on the safe side, and the same problem is happening.
--
Glenn Fleishman
seattle, washington
work and home: glennf.com
wireless data news: wifinetnews.com

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=3Dgcdmp-msql-mysql-modules @m.gmane.org

Re: Client authentication error -- suddenly

Just to let everyone know that I solved this problem.

It was a very odd one. My servers have been running 4.1.0 or later since
last year. I have had zero problems with linkages against MySQL
libraries in that time. When it failed this morning, only one of my two
server instances stopped accepting clients. PHP and mysql client
continued to work from the same host.=20

Very strange.

I did do a full 4.1.7 install of MySQL on the Web host, including
relinking libraries and includes (/usr/lib/mysql and /usr/lib/include).
I then recompiled DBD 2.9005_3 against the new libraries and installed,
and all is well.

But I'm baffled as to why this worked without a hitch with no changes
for these last many moons, and then just because (I assume) of a single
large SELECT operation, the library issue reared its head.

Very odd, no answers here, but everything works again.
--
Glenn Fleishman
seattle, washington
work and home: glennf.com
wireless data news: wifinetnews.com

--
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe: http://lists.mysql.com/perl?unsub=3Dgcdmp-msql-mysql-modules @m.gmane.org