Comments - mariadb-connector-c 3.3.2 on macOS doesn't connect to remote MariaDB sever
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Just to add that I'm seeing the same thing on 2 Macs:
sqlalchemy.exc.OperationalError: (mariadb.OperationalError) Can't connect to server on '192.168.50.214' (60)
This is after brew upgrade MariaDB-connector-c to 3.3.2 and now there's no going back.
I am experiencing the same issue when attempting to connect in a shell/notebook environment (macOS Monterey 12.5.1).
However, my application can connect in a container using Python 3.9 base image--which uses Debian 11? https://pythonspeed.com/articles/base-image-python-docker-images/
So this is an OS based issue?
When I looked on the SO yesterday I couldn't come to much of a conclusion.
Looking at the OSX error for 60 corresponds to ETIMEDOUT.
Do both servers have a equal access to the remote server they are connecting to?
I looked though the code differences and nothing particularly struck me as connection related.
Can you truss the python program on both servers to maybe compare the system calls and put then in a bug report (CONC project).
If you see something at the OS layer returning the 60/ETIMEDOUT use a debugger, set the system call as a breakpoint, and when the error is returned, gain a full backtrace.
All fixed here -> https://github.com/mariadb-corporation/mariadb-connector-c/commit/4f715e8fb1757a9c3b432471dbbc36787da6030c
Reported to brew to update the keg (is that the right term?) -> https://github.com/Homebrew/brew/issues/13846
I think someone from mariadb needs to make the request. The issue was closed with a link to how to update the keg.