Windows 2008

Does anything change of you connect explicitly to host 127.0.0.1?

I'll try that but what does the client normally connect to when you just
type 'mysql'? Also why would it have a hard time resolving an entry that is
in the system's hosts file sometimes but not other times?

On Thu, Dec 19, 2019, 10:40 AM Vladislav Vaintroub (Jira) <jira@mariadb.org>

According to the source code, it connects to "localhost". And it uses getaddrinfo() to enumerate out the IP addresses of the host. getaddrinfo() can return multiple addresses, and I believe there is no guarantee it always will be either IPv4 or IPv6 loopback address for "localhost", it probably depends on etc/hosts , and DNS server config. client will try to connect using address that getaddrinfo returns, in order in which it returns entries, until it succeeds.

I do not think that there is any guarantee in which order getaddrinfo() returns its entries (since you asked about the order)

And if client is using an IP address, which is not loopback, the server won't figure out loopback either.

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1042 (HY000): Can't get hostname for your address

On Fri, Dec 20, 2019 at 2:05 AM Vladislav Vaintroub (Jira) <jira@mariadb.org>

Here is an example of it working and not working:

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1042 (HY000): Can't get hostname for your address

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost'
(using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1042 (HY000): Can't get hostname for your address

Keep in mind this is a Windows 2008 server and not Linux/Unix.

I am trying to get this to work so that I can replicate this to a new
server since 2008 is EOS next month.

Yes, I noticed Windows 2008, I'm aware it is EOLed in Jan 2020.

According to the code I'm reading, this specific error is thrown, if either getpeername() or getnameinfo() would fail. My feeling is that getpeername() misbehaves, because setsockopt(SO_UPDATE_ACCEPT_CONTEXT) introduced in this commit https://github.com/MariaDB/server/commit/8f329e8d37e08c28d4e39d5c87ea22300285d9cd could have some subtle bug in Windows 2008, under some specific unknown circumstances . Now sure how that helps. Why connecting from PHP would do a better job, I've not even slightest idea.
Do remote connection work? Not "localhost"?

I don't know if this helps or makes things more confusing but I noticed:

It only fails the first time you try it after some amount of time.. see:

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1042 (HY000): Can't get hostname for your address

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

-wait a little while-

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1042 (HY000): Can't get hostname for your address

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

E:\MariaDB 10.4\bin>mysql -h127.0.0.1
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

It seems like the remote application servers are able to connect to it consistently but I can't really trust it because it's acting really strange.

Also the log on the server looks like this when it is failing:

2019-12-20 10:50:14 15 [Warning] Aborted connection 15 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (This connection closed normally without authentication)
2019-12-20 10:50:49 21 [Warning] Aborted connection 21 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (This connection closed normally without authentication)

Also MySQL 5.5 always works, I haven't tried 5.6 yet, 5.7 doesn't work on Windows 2008 so I can't try that.

Interesting. "wait a little while", specifically.
maybe you can try thread_handling=one-thread-per-connection in my.ini, and see if anything changes. After a little while, which I think like 1 minute for Win2008, a an idle thread from Windows' own threadpool would terminate, and perhaps this strange effect has to do something with that.

Also noticed: when it works the server logs localhost but otherwise it logs connecting host for the hostname.

2019-12-20 11:01:35 12 [Warning] Aborted connection 12 to db: 'unconnected' user: 'Administrator' host: 'localhost' (This connection closed normally)
2019-12-20 11:02:38 13 [Warning] Aborted connection 13 to db: 'unconnected' user: 'unauthenticated' host: 'connecting host' (This connection closed normally without authentication)

I am wondering if maybe it just isn't waiting long enough for whatever thread in Windows needs to start up to provide the answer but then for subsequent tries the thing Windows needs to provide is already running. Sorry I sound like a fool I don't really know about the innerworkings of these things.

Well, according to documentation, the code that is currently there should work fine, and not depend on any threads. Also, we did not have complaints about 10.4 so far, but I also presume Windows 2008 now would be exotic environment ,perhaps nobody was trying to run on it this far.

I sort of hand-wave and blame Windows 2008 bugs for that, failing to see bugs in our code.

Well, it seems like:

thread_handling=one-thread-per-connection does change the operation.

10:53
E:\MariaDB 10.4\bin>mysql
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

11:33
E:\MariaDB 10.4\bin>mysql
ERROR 1045 (28000): Access denied for user 'Administrator'@'localhost' (using pa
ssword: NO)

The only noticed downside is that it takes longer to kick back the authentication failure.

I only installed 10.4 because I thought that it was officially supported, if not what version of Maria is supported on Windows 2008?

thanks.

Are there any terrible consequences in running thread_handling=one-thread-per-connection ?? in production?

I hope you do not run it for long time in production. Windows 2008 has 3 weeks more to live, both our and OS vendor's policy say that.

thread_handling=one-thread-per-connection , all non-Windows has this default. MySQL has this default.

What I was asking is it safe to run it like that for a week or so while I
migrate the DB to a different host? I know I cant run 2008 without updates.

On Fri, Dec 20, 2019, 3:35 PM Vladislav Vaintroub (Jira) <jira@mariadb.org>

I'd guess thread_handling=one-thread-per-connection as a workaround will be fine. Most Linux installations just run that. Unless your workload consists of many thousands concurrent connections, this will work.