Bug #60432 | Modifying mysql.user table can deny users from logging in | ||
---|---|---|---|
Submitted: | 11 Mar 2011 14:56 | Modified: | 12 Mar 2011 13:58 |
Reporter: | Jacek Osiecki | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Pluggable Authentication | Severity: | S3 (Non-critical) |
Version: | 5.5.9 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysql user table plugin |
[11 Mar 2011 14:56]
Jacek Osiecki
[12 Mar 2011 13:58]
Valeriy Kravchuk
Verified just as described on Windows XP. It would be nice for server NOT to reply on column orders and always refer columns by name (and to prevent alteration of tables in MySQL database in cases like this).
[11 Apr 2012 12:23]
S R
How can this be resolved if no one, even root, can log on to mysql? I have stopped and restarted the service; rebooted the server to no avail... ********** No user can log in now. To repair it, one has to delete the additional column: **********
[11 Apr 2012 12:31]
Peter Laursen
Did you try to start the server with --skip-grant-tables option? ie: 1) navigate ("cd ...") to the server/bin folder/directory 2) start the server by executing "mysqld --skip-grant-tables" (if server is running as a service then first stop the service) 3) now connect from a client and 'normalize' the user table Refer: http://dev.mysql.com/doc/refman/5.5/en/server-options.html#option_mysqld_skip-grant-tables Peter (not a MySQL person)