[MDEV-24293] All remote connections seen as Localhost by the database Created: 2020-11-26 Updated: 2020-12-04 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Platform Windows |
| Affects Version/s: | 10.5.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | John Cox | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Environment: |
VPC on AWS, All in the Same subnet, Windows 2019 server. Server 1 Server 2 |
||
| Description |
|
I have determined that MariaDB is seeing all DB logons as being local. MySQL workbench and HeidiSQL will not connect to the DB from server 2 to the DB. |
| Comments |
| Comment by Vladislav Vaintroub [ 2020-11-26 ] | ||||||||||||||||||||||||||||||||||||||||||
|
this is not a very specific description. here is an example of 2 root users, 1 connecting locally, and one remotely. pay attention to the column "host"
As you see, one user is from localhost, another one (current) , is from workpc
As you see, it is a remote connection, correctly identified, no localhost here | ||||||||||||||||||||||||||||||||||||||||||
| Comment by John Cox [ 2020-12-04 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Here is an explanation shown similar to what you presented. MariaDB [(none)]> show processlist;
---
--- MariaDB 10.5.4 on windows server 2019 running in AWS User ID 79 is logged on from server1, as host localhost Through experimentation I have found that I must have an account setup as 'test01'@'localhost' and one for the remote system 'test01'@'server2IP'. Test01 has never been setup to login from localhost but it does login, most likely because I setup the wildcard '%' as host, but I understand that '%' does not work for localhost;
-------
------- Trying to connect to localhost on the DB server this is the results. Trying to connect to the DB from server2 this is the rusults.
-------
------- C:\Users\Argoadmin>mysql -u test03 -p -P3312 -h 172.31.13.200 | ||||||||||||||||||||||||||||||||||||||||||
| Comment by John Cox [ 2020-12-04 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Here is an explanation shown similar to what you presented. MariaDB [(none)]> show processlist; MariaDB 10.5.4 on windows server 2019 running in AWS User ID 79 is logged on from server1, as host localhost Through experimentation I have found that I must have an account setup as 'test01'@'localhost' and one for the remote system 'test01'@'server2IP'. Test01 has never been setup to login from localhost but it does login, most likely because I setup the wildcard '%' as host, but I understand that '%' does not work for localhost; Trying to connect to localhost on the DB server this is the results. Trying to connect to the DB from server2 this is the rusults. C:\Users\Argoadmin>mysql -u test03 -p -P3312 -h 172.31.13.200 ---- Vladislav Vaintroub edited comment on MDEV-24293 at 11/26/20 11:55 PM: this is not a very specific description. here is an example of 2 root users, 1 connecting locally, and one remotely. pay attention to the column "host"
As you see, one user is from localhost, another one (current) , is from workpc
As you see, it is a remote connection, correctly identified, no localhost here was (Author: wlad): here is an example of 2 root users, 1 connecting locally, and one remotely. pay attention to the column "host"
As you see, one user is from localhost, another one (current) , is from workpc
As you see, it is a remote connection, correctly identified, no localhost here – | ||||||||||||||||||||||||||||||||||||||||||
| Comment by Vladislav Vaintroub [ 2020-12-04 ] | ||||||||||||||||||||||||||||||||||||||||||
|
Apparently, the lack of ":port" after localhost in this output
means, that you connect using named pipe. it is possible to connect remotely with named pipe, although I would not know what it would be good for. named pipe connection are always "localhost", when it comes to authentication, even if you could connect remotely. |