Can't start any database if home directory is on external volume

[runforrestrun]

Can't start any database if home directory is on external volume

[manuelbua]

I've a similar problem: the MySql data directory i choose is on a removable drive and manually running the plist file show an input/output error:

launchctl load com.tinyapp.DBngin.mysqld..
Load failed: 5: Input/output error

Inspecting the plist file and manually executing the invocation command in a terminal works just fine (running with sudo as the --user option requires it):

sudo /Users/Shared/DBngin/mysql/8.0.33/bin/mysqld --disable-log-bin --socket=/tmp/mysql_3306.sock --user=_mysql --port=3306 --basedir=/Users/Shared/DBngin/mysql/8.0.33 --datadir=/Volumes/extdata/dev/db/mysql/8.0.33 --plugin-dir=/Users/Shared/DBngin/mysql/8.0.33/lib/plugin --log-error=/Volumes/extdata/dev/db/mysql/8.0.33/mysqld.local.err --pid-file=/Volumes/extdata/dev/db/mysql/8.0.33/mysql.pid

I wonder if this problem is related to launchctl?

[runforrestrun]

@manuelbua any clue how to debug this?

[manuelbua]

I'm unable to debug the launchctl call as it doesn't really log anything anywhere.
Other than running the command inside the plist and seeing that it works fine, i'm not sure if launchctl is expecting something i don't know.

I'm in the middle of the process of setting up a new machine for development work and i tried a few things without success. I read that launchctl may refuse to execute/load plist files if they are located in an unsafe place, but mysqld lies on the OS partition in /Users/Shared/DBngin and only the data directory for MySql is on a drive whose ownership is ignored.

I'm also unsure on what to do: since i'm going to use the disk as an internal one (it's an M.2 disk placed in a MacMini dock), unchecking the "Ignore ownership on this volume" seems a sensible option for my use-case, but i would really love to know how to solve this without modifying that volume option.

Any devs around that may be able to point us in the right direction?

[runforrestrun]

I also had this problem with an installation of mysql 5.7 with brew.
brew services start mysql never worked
I always had to start the server manually by using mysql.server start

This smells like the same issue. I hope that DBngin can somehow execute it differently.