Hello, I tried to install the new .deb client in two different distros. In all distros, I received errors in mySQL.
In Deepin, you can create a new server / site, but when we try to start this site, we can only see the default Apache page. Pop-ups notify me about mySQL errors.
In Kubuntu 19.04, I received that mySQL messages during site creation and Local always abort the process.
I wasn’t sure whether I should start a new thread or not but let’s start here. First, thank you for improving performance and providing an option for Linux. I had been using Local a while ago but had a multitude of issue, performance being one. I also moved to Linux around that time.
So, I installed the packages you’ve suggested but am seeing a different error (below). I checked and, as the error suggests, the file doesn’t exist. I am on Kubuntu 19.04. mysql is installed according to dkpg. Any assistance is appreciated. Thanks!
Thanks! It looks like it’s getting hung up on a port allocation issue:
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2019-09-13T17:30:45.986710Z 0 [ERROR] [MY-010262] [Server] Can't start server: Bind on TCP/IP port: Cannot assign requested address","timestamp":"2019-09-13T17:30:45.989Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2019-09-13T17:30:45.986721Z 0 [ERROR] [MY-010257] [Server] Do you already have another mysqld server running on port: 10003 ?","timestamp":"2019-09-13T17:30:45.990Z"}
@clay might this have anything to do with my issue re: mysqladmin not needing the parameters to create a database and actually choking when they were given?
That above error dialog seems to have similar wording to my CLI errors.
Thanks for pointing me in the right direction. It was a vpn client with a firewall running in the background. I disabled it and all is well. Thanks again for your help!
According to the VPN provider, their firewall “blocks all connectivity outside of the tunnel to ensure there is zero chance of any kind of leak, including but not limited to DNS leaks, IPv6 leaks, WebRTC leaks, etc.”. Based on that, I assume it was blocking everything. There is a LAN Bypass option but I’m not sure if I had it enabled. Maybe it’s just too aggressive.