MySQL Bugs: #3044: MySQL forgets privileges

Bug #3044	MySQL forgets privileges
Submitted:	2 Mar 2004 12:52	Modified:	26 May 2004 11:29
Reporter:	Bill Winett	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.1-alpha-standard	OS:	Windows (Windows)
Assigned to:		CPU Architecture:	Any

Description:
Periodically MySQL "forgets" account privileges.  For example, there may be an account for "example@localhost" that has select privilege on all tables in mydb.  Periodically example@localhost can no longer select from this table, even though the privileges are still in the mysql.user.  At this point I have re-granted the privileges (and then had to flush them - another bug?) at which time example@localhost could again access the database.

How to repeat:
I don't know what causes this to happen.  It seems to happen randomly, about once a week or every two weeks.

libmysqld does not work with privieleges.

If user@host , on normal server, can not access a table to which he / she has privileges, please send output from SHOW GRANTS for that user@host and the  full error message (with the command that caused the error message) , meaning both error number and text.

Just happened again.  The "show grants" command shows that the user doesn't have access to the tables:

mysql> show grants for 'x'@'y.com';
+--------------------------------------------------------------+
| Grants for x@y.com                                           |
+--------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'x'@'y.com' IDENTIFIED BY PASSWORD 'z' |
+--------------------------------------------------------------+
1 row in set (0.00 sec)

but that is the problem!  I've granted other privileges to this user.  In fact, I have to re-grant privileges to this user every couple of weeks!

Unfortunately, this is still not enough :(

To fix the bug we need a way to somehow repeat the incorect behaviour.
May be you can try to create a script that simulates the load in your application (only GRANT commands probably) and see if it reproduces the problem ?

Could this be a dupe of bug 2178 ?

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".