2020/10/27: Difference between revisions
Jump to navigation
Jump to search
(Created page with "I've got a bit of a double-bind situation here... * Email retrieval on cloud5 (where it had been for some months) stopped working when I upgraded Ubuntu to 20.04. {{l/htyp|Dov...") |
No edit summary |
||
| Line 8: | Line 8: | ||
After looking extensively at configuration files, one relevant difference seems to be the GRANTS (<code>SHOW GRANTS FOR 'root'@'localhost';</code>): | After looking extensively at configuration files, one relevant difference seems to be the GRANTS (<code>SHOW GRANTS FOR 'root'@'localhost';</code>): | ||
<table><caption>cloud1</caption> | <table width=100%><caption>'''cloud1''' (working)</caption> | ||
<tr><td> | <tr><td> | ||
Grants for root@localhost | Grants for root@localhost | ||
| Line 22: | Line 22: | ||
</td></tr></table> | </td></tr></table> | ||
<table><caption>cloud5</caption> | <table><caption>'''cloud5''' (kind of not working)</caption> | ||
<tr><td> | <tr><td> | ||
Grants for root@localhost </td></tr> | Grants for root@localhost </td></tr> | ||
Revision as of 17:57, 27 October 2020
I've got a bit of a double-bind situation here...
- Email retrieval on cloud5 (where it had been for some months) stopped working when I upgraded Ubuntu to 20.04. Dovecot gives errors on IMAP and POP3. Postfix (SMTP) is still working, and we are able to access email via Roundcube, but not desktop or mobile clients.
- Meanwhile, Dovecot on the new cloud1 server is working -- but MySQL refuses to accept connections from MySQL Workbench, making it difficult to set up databases, which makes it difficult (though not impossible) to set up Roundcube there.
I'm focusing on fixing the MySQL issue, as that is a blocker on several issues.
One symptom: MySQL on cloud5 (which works properly) will only let me connect via CLI if I have a username and password. MySQL on cloud1 (not working for ssh tunnel connections) will let me connect from CLI with or without a username and with or without a password.
After looking extensively at configuration files, one relevant difference seems to be the GRANTS (SHOW GRANTS FOR 'root'@'localhost';):
|
Grants for root@localhost |
GRANT ALL PRIVILEGES ON *.* TO `root`@`localhost` IDENTIFIED VIA mysql_native_password USING 'invalid' OR unix_socket WITH GRANT OPTION
GRANT PROXY ON ''@'%' TO 'root'@'localhost' WITH GRANT OPTION
|
|
2 rows in set (0.000 sec) |
| Grants for root@localhost |
GRANT
SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, SHUTDOWN,
PROCESS, FILE, REFERENCES, INDEX, ALTER, SHOW DATABASES, SUPER,
CREATE TEMPORARY TABLES, LOCK TABLES, EXECUTE, REPLICATION SLAVE,
REPLICATION CLIENT, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE,
CREATE USER, EVENT, TRIGGER, CREATE TABLESPACE, CREATE ROLE, DROP ROLE
ON *.* TO `root`@`localhost` WITH GRANT OPTION
GRANT
APPLICATION_PASSWORD_ADMIN,
AUDIT_ADMIN,BACKUP_ADMIN,
BINLOG_ADMIN,
BINLOG_ENCRYPTION_ADMIN,
CLONE_ADMIN,
CONNECTION_ADMIN,
ENCRYPTION_KEY_ADMIN,
GROUP_REPLICATION_ADMIN,
INNODB_REDO_LOG_ARCHIVE,
INNODB_REDO_LOG_ENABLE,
PERSIST_RO_VARIABLES_ADMIN,
REPLICATION_APPLIER,
REPLICATION_SLAVE_ADMIN,
RESOURCE_GROUP_ADMIN,
RESOURCE_GROUP_USER,
ROLE_ADMIN,
SERVICE_CONNECTION_ADMIN,
SESSION_VARIABLES_ADMIN,
SET_USER_ID,
SHOW_ROUTINE,
SYSTEM_USER,
SYSTEM_VARIABLES_ADMIN,
TABLE_ENCRYPTION_ADMIN,
XA_RECOVER_ADMIN
ON *.* TO `root`@`localhost` WITH GRANT OPTION
GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION
|
|
3 rows in set (0.00 sec) |