[MDEV-3596] LP:983322 - 'Access denied for user debian-sys-maint@localhost' MariaDB 5.5 Ubuntu 10.04 Created: 2012-04-16 Updated: 2012-10-04 Resolved: 2012-10-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jonathan Bailon Segura (Inactive) | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | Launchpad | ||
| Attachments: |
|
| Description |
Procesando disparadores para libc-bin ... ERROR 1045 (28000): Access denied for user 'debian-sys-maint'@'localhost' (using password: YES) xxx@ubuntu:~$ mysql -u root -p This software comes with ABSOLUTELY NO WARRANTY. This is free software, Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> GRANT ALL PRIVILEGES ON . TO 'debian-sys-maint'@'localhost' IDENTIFIED BY 'wVx0bRaK7VfZ5dQx' WITH GRANT OPTION; |
| Comments |
| Comment by Elena Stepanova [ 2012-04-17 ] |
|
Re: 'Access denied for user debian-sys-maint@localhost' MariaDB 5.5 Ubuntu 10.04 Is it a fresh installation, or did you upgrade from a previous version? If you upgraded, what was the previous version? Could you please provide the part of your syslog (related to mysql) where you ran installation/upgrade, started the server and up to the point when you got the last error? Thanks. |
| Comment by Jonathan Bailon Segura (Inactive) [ 2012-04-18 ] |
|
Re: 'Access denied for user debian-sys-maint@localhost' MariaDB 5.5 Ubuntu 10.04 Apr 18 08:40:37 ubuntu mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql |
| Comment by Jonathan Bailon Segura (Inactive) [ 2012-04-18 ] |
|
Re: 'Access denied for user debian-sys-maint@localhost' MariaDB 5.5 Ubuntu 10.04 |
| Comment by Elena Stepanova [ 2012-05-03 ] |
|
Re: 'Access denied for user debian-sys-maint@localhost' MariaDB 5.5 Ubuntu 10.04 According to the log you provided, you already had a problem with the instance before you upgraded to 5.5, most likely it started when you were upgrading from 5.0 to 5.1, or from an old version of 5.1 to a newer one. The following record [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MariaDB 50161, now running 50523. Please use mysql_upgrade to fix this error. says that your mysql.db has 20 columns. It's 5.0 format, or possibly an early 5.1; but the same record says that the database was created with 50161 (=5.1.61). 'MariaDB' is irrelevant here, it might mean either MariaDB or MySQL. In either case, 5.1.61 has 22 columns in mysql.db, so it could not create it. What could happen, for example, is that you were upgrading from 5.0 or an old 5.1 to 5.1.61, and the server was upgraded and started, mysqlcheck was executed, but mysql_upgrade failed. Possibly it failed due to the very same reason, the access problem for the system user. Now, when you are upgrading to 5.5, you still need to have system tables fixed, since they are in the old format. However, mysql_upgrade still fails, due to the access problem for the system user. When you are trying to grant permissions to it, you are working with tables which are in the wrong format, which is why your GRANT statement fails. The solution would be to run mysql_upgrade manually, under root. After you do it, you will be able to run the GRANT statement properly, and then your system user will have its access back. Please let us know if it worked for you (or if you found another solution for the problem). |
| Comment by Rasmus Johansson (Inactive) [ 2012-05-03 ] |
|
Launchpad bug id: 983322 |