Bug #107291 | Access denied when connecting over socket | ||
---|---|---|---|
Submitted: | 13 May 15:43 | Modified: | 24 Jun 7:04 |
Reporter: | Michal Kralik | Email Updates: | |
Status: | Open | Impact on me: | |
Category: | MySQL Router | Severity: | S2 (Serious) |
Version: | 8.0.29 | OS: | CentOS (7) |
Assigned to: | CPU Architecture: | x86 | |
Tags: | access denied, socket |
[13 May 15:43]
Michal Kralik
[20 May 13:42]
MySQL Verification Team
Hi Mr. Kralik, Can you please give us the reasons why are you trying to connect our client CLI to the read-only socket of the router. You have to use options that would change nothing at all, which is not how our CLI works by default. Next, please check the privileges of that user that is attempting this connection .... Last, but not least, describe to us how is router connected to the cluster and are all replicas configured for read and write operations.
[21 Jun 1:00]
Bugs System
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".
[24 Jun 7:04]
Michal Kralik
Sorry, for some reason I did not receive email notification for your follow up. We use MySQL router to connect to an InnoDB Cluster. We'd like to use a socket to connect to MySQL router instead of TCP connections. The user has proper privileges since you can connect through TCP with the same user. I don't understand your question regarding "connect our CLI to the read-only socket of router". In the example I demonstrate connection with "mysql" cli to the router either via socket or TCP where the socket connection does not work but TCP does. I does not seem this is expected. My understanding of the read-only socket of MySQL Router is that it connects you to a read-only replica of the InnoDB Cluster. Router is connected to the cluster as described in the MySQL Router config I attached. It uses TCP connections. Let me know what debugging information you'd need here. One replica is R/W and the other is R/O - as described in the output from MySQL replica config.