Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial

Alex Cory
7,069 PointsMySQL won't stop running
I've tried to stop the process but it keeps giving me this error:
Executing '/usr/local/mysql/support-files/mysql.server stop' 2013-12-23 21:08:29 - Stop server: ERROR! MySQL server PID file could not 2013-12-23 21:08:29 - Stop server: be found!
Here's a screenshot. http://imageshack.us/a/img69/5515/dr1k.png
7 Answers

James Barnett
39,199 PointsTerminate the process

Alex Cory
7,069 PointsI tried all of those and it still hasn't stopped running... unfortunately. I tried double checking with both the system preferences view as well as the mySQL workbench view. The system preferences says it's running. No response when I click stop. When I go to the workbench it says off and without me clicking start it just turns on. I do have MAMP installed. Not sure if this is messing with it.

James Barnett
39,199 PointsIf system preferences says it's running then you need to kill it.

Alex Cory
7,069 PointsOkay so here are the results. Still hasn't stopped.. ugh..
Results from kill-program: http://imageshack.us/a/img856/8566/88c9.png
Top view after kill-program: http://imageshack.us/a/img18/5397/9pgx.png

James Barnett
39,199 PointsTry killall -9 mysqld

Alex Cory
7,069 PointsThe result was:
No matching processes belonging to you were found

James Barnett
39,199 PointsDid you run it with sudo
?

Alex Cory
7,069 PointsYessir

Alex Cory
7,069 PointsI totally figured it out! Wow I feel like an idiot. I went back and tried everything you suggested a second time and realized that when I used the activity monitor I didn't Force Quit MySQL I simply quit it, which did nothing. This worked like a charm. Thanks for all your awesome help!