TablePlus
MySQL service on port 3306 not actually starting
I'm having a bizarre problem with a MySQL 8.0.33 service. If I use port 3306 when I click Start it appears to start, but I cannot connect. If I run netstat -nap tcp | grep -i "listen" I do not see port 3306 in use by anything.
I tried creating a new MySQL 8.0.33 service also using port 3306. When I click Start on that one I would expect an error about port 3306 already being in use, but it appears to start it successfully. So now the UI is showing 2 services running on port 3306 (screenshot below), but neither are actually running.
If I change the port to 3307 on either service then I can connect just fine and all my data is there. It seems to only be port 3306 having this problem. I've tried updating DBngin to the latest version (7.9 build 79) and restarting it multiple times, but that changes nothing.
This is on a Macbook Pro M3 running Sonoma 14.2.1
Hi @thomasruns, I think port 3306 is currently being used by another process. Could you please try to restart macOS and see how it goes?
I already confirmed port 3306 is not in use by anything else using both netstat and lsof. But even if that were true, DBngin should not allow me to start a service on that port, but it does (or claims to).
Yeah, I know it’s weird, but there’s nothing special—it’s just a simple startup command with the port as a parameter. So I’m not sure why it happens. Sometimes macOS acts weird until I restart it.
Ok I'll give that a try when I'm not in the middle of work. For now at least changing to 3307 got me back up and going. Hopefully that works for anyone else who hits the same issue and stumbles on this post.
I'm having the same problem on Windows. dbngin indicates that the service is started, but I can't access it. I tried downloading the new binaries, but it didn't work. This only happens with the MySQL service.
I'm having the same problem on Windows. dbngin indicates that the service is started, but I can't access it. I tried downloading the new binaries, but it didn't work. This only happens with the MySQL service.
Same issue in windows for mysql
For me ( windows) mysql quick solution is Edit the connection then change port from 3306 to anything save , start server then stop server and again change the port to 3306.
or leave it to any other port.
For me ( windows) mysql quick solution is Edit the connection then change port from 3306 to anything save , start server then stop server and again change the port to 3306.
or leave it to any other port.
work for me thank su
