I’m running into an issue with IndigoStack where MySQL does not shut down properly when I quit or stop the stack. When I try to restart the stack, I get this error:
“MySQL server service” service is configured to use port 3306, but it is already in use by a process outside of Indigo.
When I check running processes, I see that mysqld is still running even after quitting IndigoStack:
ps aux | grep mysqld
Killing the process manually with kill -9 [pid] clears the port conflict and allows the stack to start again — but this isn’t sustainable long-term.
What I’ve already confirmed:
• The my.cnf file includes a proper pid-file line:
pid-file=/Users/michaelb/.indigo/stacks/11B119/mysql_A4AB/run/mysql.pid
• The run/ directory sometimes doesn’t exist on startup, which seems to prevent the PID file from being written.
• I’ve manually created the run/ folder and PID file to work around it — but the core issue remains: MySQL doesn’t shut down when IndigoStack stops the stack.
Thanks — happy to provide logs or more info if it helps.
—Michael B.