0008225: Upgrade of .NET MySql Connector to v 6.9.9 doesn't handle unix sockets in ConnectionString

Notes
(0032231) UbitUmarov (administrator) 2017-08-01 05:34	.NET MySql Connector to v 6.9.9 is the most recent version that still supports servers 5.0 https://dev.mysql.com/doc/connector-net/en/connector-net-versions.html [^] and from bug report you show, is not clear 6.10 did fix it. at this point, you can use another version, either the one provided in 0.8.2 or one from: https://dev.mysql.com/downloads/connector/net/ [^]

(0032232) colosi (reporter) 2017-08-01 11:53	I switched to using a tcp port on localhost, so this is working for me now; but I wanted it documented in case anyone else runs into it. Now that I've found workaround and you've mentioned another, I'll lower the priority. Hopefully, at some point, they'll release a new version where this is fixed and we can upgrade then. Nothing to do until then.

(0036536) Gwyneth Llewelyn (reporter) 2020-06-09 10:07	Still not fixed? There are good reasons for using a Unix socket as opposed to a TCP socket as a 'workaround' — namely, a certain degree of security (the MySQL server is not exposed to the public Internet 'by mistake'). Here are my findings, basically replicating what @colosi reported: http://opensimulator.org/wiki/Talk:Database_Settings [^] This is the _first_ MySQL connection implementation that I've found that does _not_ support connection through a Unix socket! (formerly, I used a different MySQL configuration, which did require TCP sockets for remote sync'ing, so I wasn't aware of this issue until today)

(0036628) Ferd Frederix (reporter) 2020-07-19 22:04	Not sure this helps, but if you use localhost as the address, the mysql driver on Linux behaves differently. It will use sockets automatically. https://dev.mysql.com/doc/refman/8.0/en/connecting.html [^] "On Unix, MySQL programs treat the host name localhost specially, in a way that is likely different from what you expect compared to other network-based programs: the client connects using a Unix socket file. The --socket option or the MYSQL_UNIX_PORT environment variable may be used to specify the socket name." "The --protocol option enables you to use a particular transport protocol even when other options normally result in use of a different protocol. That is, --protocol specifies the transport protocol explicitly and overrides the preceding rules, even for localhost."

(0037444) Gwyneth Llewelyn (reporter) 2021-01-03 04:56	@Ferd, I'm aware of this expected behaviour, which allegedly works 'straight out of the box' since it's supposedly dealt with at the MySQL protocol level. I've long since used 'localhost' pretty much everywhere, but I seem to have a few spurious connections coming from ROBUST... I see that this requires a bit more detective work on my side! I suspect that there are some 127.0.0.1 defaults which I have not explicitly overridden.

Issue History
Date Modified	Username	Field	Change
2017-07-31 17:07	colosi	New Issue
2017-07-31 17:47	colosi	Git Revision or version number	=> 52d4cf692caf4907e22089733fea080a081e3233
2017-07-31 17:47	colosi	Priority	low => normal
2017-08-01 05:34	UbitUmarov	Note Added: 0032231
2017-08-01 11:53	colosi	Note Added: 0032232
2017-08-01 11:54	colosi	Priority	normal => none
2017-08-01 11:54	colosi	Resolution	open => not fixable
2020-06-09 10:07	Gwyneth Llewelyn	Note Added: 0036536
2020-07-19 22:04	Ferd Frederix	Note Added: 0036628
2021-01-03 04:56	Gwyneth Llewelyn	Note Added: 0037444

Relationships