Bug 122158
Summary: | MySQL privileges adjustments from java fail | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Jacob Martin <jmartin> | ||||
Component: | mysql | Assignee: | Tom Lane <tgl> | ||||
Status: | CLOSED WONTFIX | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 3.0 | CC: | hhorak | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-10-19 19:27:01 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Jacob Martin
2004-05-01 03:20:26 UTC
Created attachment 99852 [details]
java source file for demostrating GRANT privileges bug in Mysql on AMD64
I felt bad about not giving you good reproducibility. Try the attached java
file after you have created a new mysql database on AMD64 and set the root
mysql user's password as "new". Don't forget to run mysql_install_db
You'll need java and the Connector/J binaries (3.0.11) to try it out. Other
versions of Connector/J display the same problem. Don't forget to compile the
java file :).
Run it, and watch it hang up mysql good once it gets to the GRANT USAGE
statement. You won't be able to kill the connection it makes and you won't be
able to connect to mysql afterwards.
I was happily surprised to see that this was all it took to reproduce.
Correction. I just tried it again, and I had to run the Test.class java program twice to get the hang-up. This is very weird!! Even more information: After killing and restarting mysql (without installing the default database), and running: ======================= use mysql; REPAIR table users; ======================= We get the following in the log: ======================= 040501 12:35:01 Warning: Found 5 of 4 rows when repairing './mysql/user' ======================= (Sorry about slow response to this...) I would say this is definitely a problem to pass to MySQL AB, if you didn't already. I would suggest though that it may be fixed in mysql 4.1, which is what we are currently shipping. Have you tried it with newer mysql releases? How about on non-AMD64 hardware? Can you trigger the failure if you don't use java (perhaps just by typing the same commands into the mysql tool)? Since we aren't supporting Connector/J in RHEL3, it'll be difficult for me to do much with this problem unless it can be reproduced without that. Sorry, it has been so long that I had forgotten about this! I hope I gave you good reproducibility though. Actually, I need to thank you because this bug forced me to use another operating system. I'm sorry that Redhat couldn't provide immediate support, we needed this for a development system that couldn't be caught up waiting for a year. When I switched to Gentoo, the problem seemed to go completely away. Good luck with the bug, I no longer have the redhat environment to test or report bugs from. This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |