search

TablePlus / DBngin

DB Engine
https://dbngin.com
1.08k stars 19 forks source link

DBngin tries to create MySQL socket in wrong location #141

Closed Synchro closed 8 months ago

Synchro commented 8 months ago

Please fill out the detail below, it helps me investigate the bug:

  1. Driver (Ex: PostgreSQL 10.0): MySQL 8.0.33

  2. DBngin build number: 7.0 (70)

  3. macOS version: Sonoma 14.4

  4. The steps to reproduce this issue:

The MySQL indicator turns green, but the service is not available. The error log fills up with this sequence:

2024-03-25T14:56:30.073888Z 0 [ERROR] [MY-010273] [Server] Could not create unix socket lock file /tmp.mysql.sock.lock.
2024-03-25T14:56:30.073896Z 0 [ERROR] [MY-010268] [Server] Unable to setup unix socket lock file.
2024-03-25T14:56:30.073901Z 0 [ERROR] [MY-010119] [Server] Aborting

As far as I can see, the location it's trying to create the socket lock file in is just wrong - nothing should be trying to write directly into /, yet I see that this path is hard-coded into the plist file:

                <string>--socket=/tmp.mysql.sock</string>

I tried altering this to /tmp/mysql.sock, however, it was apparently ignored, and after a short while, the file reverted back to the original config.

How can I make it work?

Synchro commented 8 months ago

I solved this by deleting all traces of DBngin and reinstalling. This allowed me to specify a better socket path, and that worked ok.