MySQL Bugs: #55270: Can perform all of Workbench Tutorial except cannot access Command Line Client

Bug #55270	Can perform all of Workbench Tutorial except cannot access Command Line Client
Submitted:	14 Jul 2010 20:18	Modified:	16 Aug 2010 4:41
Reporter:	David Rogers	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S2 (Serious)
Version:	5.1.48-win32,Workbench -gpl-5.2.25-win32	OS:	Windows (Vista Ultimate)
Assigned to:		CPU Architecture:	Any
Tags:	password

Description:
WHAT I DID:
Installed mysql-essential-5.1.48-win32 and mysql-workbench-gpl-5.2.25-win32, apparently successfully.  Runs as Windows service.  Can successfully do all of the Getting Started Tutorial, chapter 4 in MySQL Workbench documentation, except where it requests me to go to the MySQL Command Line Client (step 22 of section 4.1 and step 8 of section 2).  All the rest of the tutorial I ran successfully.

But when I enter as the password either the word root or the word David1 (the password I gave it in the wizard for the configuration of the MySQL Server 5.1 Instance) in the Command Line Client it does not accept, quickly stating "Access denied ... localhost" and then the screen disappears.

WHAT I EXPECTED TO HAPPEN:  Acception of the password by MySQL Command Line Client.

WHAT HAPPENED:
MySQL Command Line Client did not accept password.

I tried this many times.  I will send a test matrix of what I did for 2 attempts.  I also will send the make (configuration) file.

How to repeat:
Follow my test matrix, especially test number 2 (which I think is more accurate, but both apparently result in the same thing).

Suggested fix:
Is it a GRANT or PERMIT problem?  Does the GRANT go in the my.ini file and, if so, where?  Something in bowels of Windows (registry)?
A bug?  I have done something out of sequence? (I suspect the last.)

Tests that I ran

Attachment: Test Matrix for MySQL Installation.docx (application/vnd.openxmlformats-officedocument.wordprocessingml.document, text), 28.39 KiB.

configuration file built via mysql-essential-5.1.48-win32

Attachment: my.ini (application/octet-stream, text), 8.74 KiB.

I put the GRANT statement in file C:\Program Files\MySQL\MySQL Server 5.1\my.ini   Tested it this AM.  – did not like it, so deleted the line.  The configuration file I forwarded does not include that line - that was the ONLY change made to my.ini.

Please, send the exact command line you had used, like this:

mysql -uroot -pDavid1 test

Valeriy Kravchuk requested "Please, send the exact command line you had used, like this:
mysql -uroot -pDavid1 test"

Veleriy:
Test 1:  In the Command Prompt, which  - when it comes up - has heading "Administrator:  Command Prompt" its first line is “Microsoft Windows [Version 6.0.6002]”, second line is “Copyright …”, and third line is “C:\Users|David>”.  Then I put in "mysql -u root -p David1 test" and it responds with many, many lines, first one being "mysql Ver 14.14 Distrib 5.1.48, for Win32 <ia32>".  Its last line is the prompt “C:\Users|David>”.  I assume success.

Test 2:  If I call up the Command Prompt, which - when it comes up has heading - "Administrator:  Command Prompt" I put in "mysql -u root -p David1" it responds with "Enter password:"; I enter "David1" and it returns "ERROR 1045 <28000>: Access denied for user 'junk!'@'localhost' <using password: YES>".  The foregoing 'junk!" is my way of expressing odd characters.  Then next line is prompt "C:\Users|David>" waiting for me.

Test 3:  If I call up the MySQL Command Line Client (which has as header "C:\Program Files\MySql\MySQL Server 5.1\bin\mysql.exe", it immediately asks "Enter password:".  When I enter "David1" it flashes an error line that begins "Error 1045 ...", probably like the above ERROR 1045.

NOTE:  ALL THE FOLLOWING TESTS WERE DONE IN THE Command Prompt, which - when it comes up has heading - "Administrator:  Command Prompt".

Test 4:  A friend suggested that I enter “mysql –u root –h 127.0.0.1 -p”.  So, I called up the Command Prompt and I entered “mysql –u root –h 127.0.0.1 –p”.  It gave the same results as in Test 1 above.  (success). So I tried “mysql –u root –h 127.0.0.1”; same results as in Test 1 above.

Test 5:  I called up the Command Prompt and I gave it “mysql test” – it responds with ERROR 1045 and prompt “C:\Users\David>”.

Test 6:  I called up the Command Prompt and I gave it “mysql -p David1 test” (without the “-u root”) and it responds as in Test 1 above (success).  I note that the socket it lists is “mysql”.

Test 7:  Called up the Command Prompt, entered “mysql –p David1 MySQL”.  It also yielded same results as in Test 1 above.

Test 8:  Called up the Command Prompt, entered “’mysql –p David1 junk”.  It also yielded same results as in Test 1 above.

Test 9:  Called up the Command Prompt, entered “mysql --help”.  It also yielded same results as in Test 1 above.

CONCLUSION:  There are not enough constraints on the command line monitor in the Command Prompt.  (Or is it meant to be this way?)  Also, something is wrong with the MySQL Command Line Client, for it will not accept a password.

Normal result of mysql command line execution is "mysql>" command prompt, like this (sorry, not on Windows at the moment, but it does not matter):

valeriy-kravchuks-macbook-pro:5.1 openxs$ bin/mysql -uroot test
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 5.1.49-debug Source distribution

Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v2 license

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> 

Had you tried NOT to put space between option, -u or -p, and username/password? Like this:

mysql -uroot -pDavid1 test

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".