MySQL Bugs: #28503: unable to log in after delete own access from remote

Bug #28503	unable to log in after delete own access from remote
Submitted:	17 May 2007 19:52	Modified:	18 Jun 2007 8:36
Reporter:	gil michlin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	5.0.24a-log	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	remove host, user administraton

Description:
when a remote host remove his privileges and applying the server stop responding

How to repeat:
having  computer A as a server with root access from outside IP X.X.X.X
and a computer B with that X.X.X.X IP is accessing via MySQLAdministrator 1.2.11
and then go to User Administration-> root and then remove the X.X.X.X HOST.
when you press apply the server is stop responding and there is no access
what so ever.

Suggested fix:
there is a workaround to solve the issue with password recovery procedure.

Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

Please read carefully about MySQL access priveledge system at http://dev.mysql.com/doc/refman/5.0/en/privilege-system.html

thank you very much for the quick response but it is a bug.
I am not saying that if i have user root with localhost,some IP if i delete
some IP i can not access from that IP, but I can not even access from localhost
it's seems like add on to bug 28391 where also removing host causes the same issue.

Thank you for the feedback.

>but I can not even access from localhost

Have you user@localhost inserted in MySQL grant tables with appropriate priveleges?

Please run MySQL server with option --skip-grant-tables, connect to it and provide output of query SELECT user, host FROM mysql.user;

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