Re: Client authentication error -- suddenly

Glenn Fleishman <[email protected]>
Newsgroups gmane.comp.db.mysql.perl
Message-ID <r02010400-1036-19F3202C31A111D9808E000A95AF2414@[192.168.123.5]>
>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/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.