Connect to MySQL failed: Found EOF after Auth, expecting OK

[GoogleCodeExporter]

What steps will reproduce the problem?
1. yum updated Mythdora 10.21 backend upgraded to .22
2. yum updated updated XBMC on Aspire REVO (ION GPU and Atom CPU) Live 
version 9.11 with install bugfix
3. MythTv Frontend is working off backend and MySQL is opened up to network
4. MythBox is configured correctly AFAIK and then "click on test" on 
MythBox setup

What is the expected output? What do you see instead?
Error text reads "Connect to MySQL failed: Found EOF after Auth, expecting 
OK. Usi" I think this last word is using...

What version of the product are you using? On what operating system?
see above

Please provide any additional information below.
see above

Original issue reported on code.google.com by lairdr...@gmail.com on 28 Jan 2010 at 6:21

[GoogleCodeExporter]

Looks like you're using "old style" passwords. See
https://bugs.launchpad.net/myconnpy/+bug/380528

See Q15 in the MythBox FAQ for the fix. I'll add the error string myconnpy is
returning to the FAQ for future reference.

Original comment by semir.pa...@gmail.com on 29 Jan 2010 at 6:53

• Changed state: Done

[GoogleCodeExporter]

Will try this over the weekend; thanks for the prompt reply and thanks for this 
impressive software!  Laird

Original comment by lairdr...@gmail.com on 29 Jan 2010 at 12:47

[GoogleCodeExporter]

Your suggestion worked a treat; I changed the old_password=1 to 0 in 
/etc/my.cnf and 
then cleared and recreated passwords for mythtv.  Thanks.  Great program; 
another 
few problems but catching up on old Dr Who episodes 1st. 

Original comment by lairdr...@gmail.com on 3 Feb 2010 at 4:29

[GoogleCodeExporter]

Hi -- I'm having the same problem. I check "my.cnf" and it contains the 
following lines:

[mysqld]
old_passwords = false # inserted by debconf
# Activate the above for connections from hosts running Debian Woody/Sarge!

I checked the mysql database and the password column is 41 bytes wide and "mysql
--version" returns:  "mysql  Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) 
using
readline 5.2"

Putting this all together, I suspect my password is properly encoded, but maybe 
I am
missing something here? Any help would be greatly appreciated!

Marc

Original comment by marc.aro...@gmail.com on 5 Feb 2010 at 5:08

[GoogleCodeExporter]

The string "old_password" is singular (vs plural in your comment). I don't know 
if the 
my.cnf field supports both singular and plural versions of the name/value pair 
but it 
is worth a try.

Original comment by semir.pa...@gmail.com on 5 Feb 2010 at 7:22

[GoogleCodeExporter]

I just checked my my.conf and I had changed the test from old_passwords=1 to 
...=0

I then went into mysql as root

>mysql -u root -p mythconverg

 and then added a new password (12345) and then flushed privileges.  It all seemed 
to work just fine:

>UPDATE mysql.user SET Password=PASSWORD('12345') WHERE User='mythtv';
>FLUSH PRIVILEGES;

Original comment by lairdr...@gmail.com on 5 Feb 2010 at 3:33

[GoogleCodeExporter]

I looked webmin to look at the list of mysql users and it became clear that the
password was indeed encrypted the old way. Since I'm not sure if there are other
elements on my myth distribution (Knoppmyth R5.5) that depend on the old 
encryption
strength I decided to create a username and password. I am now able to get in 
and
things basically work, but I am facing a different problem relating to the 
default
player. I will open a new issue for this.

Original comment by marc.aro...@gmail.com on 5 Feb 2010 at 4:31