How to stop mysqld
MysqlMacosMysql Problem Overview
To find out the start command for mysqld (using a mac) I can do:
ps aux|grep mysql
I get the following output, which allows me to start mysql server.
/usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=...
How would I find the necessary command to stop mysql from the command line?
Mysql Solutions
Solution 1 - Mysql
Try:
/usr/local/mysql/bin/mysqladmin -u root -p shutdown
Or:
sudo mysqld stop
Or:
sudo /usr/local/mysql/bin/mysqld stop
Or:
sudo mysql.server stop
If you install the Launchctl in OSX you can try:
MacPorts
sudo launchctl unload -w /Library/LaunchDaemons/org.macports.mysql.plist
sudo launchctl load -w /Library/LaunchDaemons/org.macports.mysql.plist
Note: this is persistent after reboot.
Homebrew
launchctl unload -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
Binary installer
sudo /Library/StartupItems/MySQLCOM/MySQLCOM stop
sudo /Library/StartupItems/MySQLCOM/MySQLCOM start
sudo /Library/StartupItems/MySQLCOM/MySQLCOM restart
I found that in: https://stackoverflow.com/a/102094/58768
Solution 2 - Mysql
There is an alternative way of just killing the daemon process by calling
kill -TERM PID
where PID
is the value stored in the file mysqld.pid
or the mysqld process id which can be obtained by issuing the command ps -a | grep mysqld
.
Solution 3 - Mysql
I did it with next command:
sudo killall mysqld
Solution 4 - Mysql
Solution 5 - Mysql
For Windows, you can run this command directly if mysql/bin is in your path.
mysqladmin -u root -p shutdown
Solution 6 - Mysql
Worked for me on mac
a) Stop the process
sudo launchctl list | grep -i mysql
If the result shows anything like: "xxx.xxx.mysqlxxx"
sudo launchctl remove xxx.xxx.mysqlxxx
> Example:
> sudo launchctl remove org.macports.mysql56-server
b) Disable to autostart the process
sudo launchctl unload -wF /Library/LaunchDaemons/xxx.xxx.mysqlxxx.plist
> Example:
> sudo launchctl unload -wF /Library/LaunchDaemons/org.macports.mysql56-server.plist
- Finally reboot your mac
Note: In some cases if you tried "a)" first, you need to reboot again before try b).
Solution 7 - Mysql
On OSX 10.8 and on, the control for MySQL is available from the System Configs. Open System Preferences, click on Mysql (usually on the very bottom) and start/stop the service from that pane. https://dev.mysql.com/doc/refman/5.6/en/osx-installation-launchd.html
The plist file is now under /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
Solution 8 - Mysql
for Binary installer use this:
to stop:
sudo /Library/StartupItems/MySQLCOM/MySQLCOM stop
to start:
sudo /Library/StartupItems/MySQLCOM/MySQLCOM start
to restart:
sudo /Library/StartupItems/MySQLCOM/MySQLCOM restart
Solution 9 - Mysql
When mysql was installed with Homebrew, it automatically restarts when killed. You need to use the following command:
brew services stop mysql
PS: If you installed a specific version, it will be [email protected]
Solution 10 - Mysql
Kill is definitly the wrong way! The PID will stay, Replicationsjobs will be killed etc. etc.
STOP MySQL Server > /sbin/service mysql stop
START MySQL Server > /sbin/service mysql start
RESTART MySQL Server > /sbin/service mysql restart
Perhaps sudo will be needed if you have not enough rights
Solution 11 - Mysql
Try killing mysqld four times in a row. It's the only thing that worked for me...
root@ubuntu:/etc/init# killall -KILL mysqld
root@ubuntu:/etc/init# killall -KILL mysqld
root@ubuntu:/etc/init# killall -KILL mysqld
root@ubuntu:/etc/init# killall -KILL mysqld
mysqld: no process found
Just keep killing it over and over until you see "mysqld: no process found".
Solution 12 - Mysql
What worked for me on CentOS 6.4 was running service mysqld stop
as the root user.
I found my answer on nixCraft.
Solution 13 - Mysql
/etc/init.d/mysql stop
service mysql stop
killall -KILL mysql mysqld_safe mysqld
When you see the following information, you success
mysql: no process found
mysqld_safe: no process found
mysqld: no process found
I use this to solve the installation problem of MySQL 5.6 in Ubuntu 15.10 using this link.
During this installation, I encounter the problem saying:
"mysqld_safe A mysqld process already exists"
Just completely stop the mysqld, mysqld_safe, mysql solves the problem.
Solution 14 - Mysql
If my mysql keeps restarting
sudo rm -rf /usr/local/var/mysql/dev.work.err
mysql.server stop
worked for me.
Solution 15 - Mysql
To stop autostart of mysql on boot, the following worked for me with mysql 8.0.12
installed using Homebrew in macOS Mojave 10.14.1
:
rm -rf ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
Solution 16 - Mysql
To stop MariaDB and MySQL server instance:
sudo mysqladmin shutdown
To start MariaDB and MySQL server instance:
mysqld &
To change data ownership for MariaDB and MySQL server instance:
sudo chown -R 755 /usr/local/mariadb/data
Solution 17 - Mysql
- Just go to task manager.
- Then in process, search mysqld.
- right click on mysqld then click on stop.
- with this process you can stop it without using commands.
Solution 18 - Mysql
first try this
sudo service apache2 stop
if not, then
sudo mysql stop
if not, then
sudo stop mysql
if not, then
sudo mysqladmin shutdown
I have been there, and I do with many tips, at the end of using tips that I follow will lead me to solved. So if you not solve in this issue, you just do other tips, till your issue get solved. Hopefully it's will help you. Thanks
Solution 19 - Mysql
For mysql 5.7 downloaded from binary file onto MacOS:
sudo launchctl load -F /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
sudo launchctl unload -F /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
Solution 20 - Mysql
Following worked for me on my macbook pro:
> brew services stop mysql
Incase if you want to stop all brew services:
> brew services stop --all
Solution 21 - Mysql
For MAMP
- Stop servers (but you may notice MySQL stays on)
- Remove or rename
/Applications/MAMP/tmp/mysql/
which holds themysql.pid
andmysql.sock.lock
files - When you go back to Mamp, you'll see MySQL is now off. You can "Start Servers" again.