MySQL database does not start in XAMPP Manager-osx

Question

I downloaded XAMPP about a month ago and it worked fine. Today I installed voice recognition software and then restarted the computer. Since then, MySQL has not started in my manager-osx application. This does not throw me in the application log. Here is what he says:

Stopping all servers... Stopping Apache Web Server... /Applications/XAMPP/xamppfiles/apache2/scripts/ctl.sh : httpd stopped Stopping ProFTPD... Checking syntax of configuration file /Applications/XAMPP/xamppfiles/proftpd/scripts/ctl.sh : proftpd stopped Restarting all servers... Starting MySQL Database... Starting Apache Web Server... /Applications/XAMPP/xamppfiles/apache2/scripts/ctl.sh : httpd started Starting ProFTPD... Checking syntax of configuration file /Applications/XAMPP/xamppfiles/proftpd/scripts/ctl.sh : proftpd started 

Both my ProFTPD and my Apache Web Server work. MySQL is not. When I switch to phpmyadmin, it causes this error message.

 #2002 - No such file or directory The server is not responding (or the local server socket is not correctly configured). 

Please help me. I have no idea what to do.

UPDATE:

Having visited the Internet a bit, I found a similar problem with a user with MAMP, another user recommended killing the mysql process, whatever that means. Could this be a problem for my problem?

UPDATE 2:

I found the answer to my problem, but I can not answer yet. So here is the answer:

1) Open a terminal and enter

 sudo su 

and then enter your password

2) Then enter

 ps aux | grep mysql 

(just copy and paste this)

3) You will need to get the mysql process id. There should be a number near the top, something like 739 or 8827

4) Kill the process using

 kill -9 {process id} 

it should look something like this: kill -9 739

5) Restart MySQL in manager-osx

Answer 1

This should work:
sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start

Answer 2

Minimum guidance

sudo killall mysqld

2. manager-osx> start mysql

---

If this did not work ...

sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start

Google error ...

---

Examples:

Mistake:

ERROR! The server quit without updating PID file (/Applications/XAMPP/xamppfiles/var/mysql/<computername>.local.pid)

My decision:

In /Applications/XAMPP/xamppfiles/etc/my.cnf change user = <uid> that <uid> is the uid from the id command.

 $ id uid=... $ vim /Applications/XAMPP/xamppfiles/etc/my.cnf ... 

Answer 3

If these commands do not work for you:

 sudo killall mysqld sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start 

Try the following:

For XAMPP 7.1.1-0, I changed the port number from 3306 to 3307.

• Click Manage Servers
• Choose MySQL Database
• Click "Customize" on the right.
• Change the port number to 3307
• Click OK
• Close the control panel and restart it.

You feel good now.

Answer 4

check the error log on your / Applications / XAMPP / xamppfiles / var / mysql / with the file name, for example your_machine_name.local.err, if you find something like: "Trying to open a previously opened tablespace. Previous tablespace ... uses space ID "

the following works for me:

edit file:

/Applications/XAMPP/xamppfiles/etc/my.cnf

find the [mysqld] section, add one line:

innodb_force_recovery = 1

then run

sudo / Applications / XAMPP / bin / mysql.server start

everything is fine.

and then the last step:

edit my.cnf and delete the line you just added:

innodb_force_recovery = 1

and restart mysql again. Otherwise, all your tables will be read only

Answer 5

I tried all of these methods with no luck (including, of course, rebooting), but when I

 sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start 

I just get:

 Starting MySQL . ERROR! 

Not the most useful information!

Answer 6

The following worked for me: change the read-only permission for "everyone" to the file /Applications/XAMPP/xamppfiles/etc/my.cnf . Then start MySQL from the XAMPP manager.

Answer 7

At first, I was unable to kill the mysql daemon with the commands hosted here. So I remembered the time of my Linux and did the following:

I tracked running processes by running top in one terminal window. Then I killed mysqld via sudo killall mysqld (insert PID ;-)) into another and restarted via sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start .

Answer 8

• close XAMPP control
• sudo killall mysqld
• sudo / Applications / XAMPP / xamppfiles / bin / mysql.server start

Answer 9

it happened to me. and

 sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start 

not working for me.

therefore, reinstall xampp and then fix it.

Attention:

reinstall xampp, do not delete mysql data, no need to worry about it.

Answer 10

There was a lot of answer, but I think I found what causes it, at least for me. It looks like if you put your computer to sleep (or it falls asleep by itself), when it opens again, it tries to open the mysql process again. At some point, I looked at my activity monitor, and I had 5 instances that killed everyone and then started mysql.

Answer 11

 sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start 

It worked for me.

Answer 12

try these two lines from the terminal

• sudo killall mysqld
• sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start

Answer 13

This may be caused by software that you installed, or it may be any other software that uses the same port 3306. This port 3306 is used by Mysql in XAMPP. A similar problem that I encountered in Apache. I ran skype and tried to run XAMPP, but skype uses the same port as Apache, so it did not work. Then I exit Skype, then the port was free and Apache started. Therefore, you should look for software in your laptop that is blocking or is busy on this port. Free this port by closing the software, and then run XAMPP and it will work.

Answer 14

I did the following: In the XAMPP control panel, I edited the my.ini file of the MySql configuration and changed the port from 3306 to 3307, and it worked, I hope this helps!

Edit: After saving the changes, make sure the service is disconnected, and then restart the service. I had the same problem when I installed MySQL, it is just a port.

Answer 15

I had success with the easy kill of all active mysql processes in the Monitor Activity tool:

1) close XAMPP control

2) open monitor activity

3) select a filter for all processes (the default is My processes)

4) search: mysql

5) force terminate all mysql

6) restart XAMPP management and start apache again

Enjoy

Answer 16

I ran into this problem just now. I checked the log file and found that it was caused by the server not shutting down correctly. So I found http://rivenlinux.info/how-to-recover-innodb-corruption-for-mysql/ and added the simple configuration "innodb_force_recovery = 1" to [mysqld] in my.cnf. Then the problem was resolved.

The log file is located at / Applications / XAMPP / xamppfiles / var / mysql and it is called accroding for your server name. Just link this XXX-MacBook-Pro.local.err

Answer 17

All the answers given above regarding the change of the port number are the best way to solve this problem in this situation, since you need your voice recognition software to coexist with MAMP. However, you should remember that changing this port number will affect all subsequent connections to MySQL (for example, terminal, php code, phpmyadmin, etc.). Therefore, it would be advisable to change the port on which voice recognition software runs. Hope this was helpful.

:)

Answer 18

if you get this error

 .............ERROR! The server quit without updating PID file 

Try

Go to / Applications / XAMPP / xamppfiles / var / mysql /

if there is no file named Your_Username.local.pid

Your_Username should replace with your Mac Username

Create a file with this name

Then try

 sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start 

its worked for me

Answer 19

This problem had the same problem: all I did was provide read-only permissions for ALL users (including the system) and all the items included in the following folders:

 /Applications/XAMPP/xamppfiles/etc /Applications/XAMPP/xamppfiles/sbin 

and restart XAMPP management and restart mysql server or

 sudo /Applications/XAMPP/xamppfiles/bin/mysql.server start 

Answer 20

Perhaps your voice recognition software has a mysql installer, and when you installed this software, it also installed mysql and added it to the service, and this mysql service starts after your system starts up. So now you have two mysql servers (one of the voice recognition software, and the second one is XAMPP), so the reason for killing the previous process (mysql service) solved your problem. But this is not a permanent solution, you must repeat it every time you start your car. So it is better to find out that the mysql server (service) and change its port is not. OR change the settings so that the mysql service does not start when your computer starts up (but maybe your voice recognition software will not work properly)

Hope this helps you.

Greetings

Answer 21

You seem to have found work by killing the process, but make sure you check the free space on your MySQL partition. If your logs or db files consume all the disk space, mysqld does not start.

Answer 22

Restarting the computer or using the kill commands above solves the problem. AS, to prevent it, I discovered that this happens anytime my computer has slept. The port is obviously saved, and then after waking up mysql tries to connect to this port, but cannot. This may be your problem.

Answer 23

I am running XAMPP 5.6.3-0 for OS X Yosemite 10.10.2 and have run into the same issue twice, the first time with Mavericks. With a bunch of different solutions to the MySQL Database problem, not starting with the Manager application, I wanted to confirm that it worked for me. The workaround that always worked and caused MySQL to start was to open a terminal and use: sudo / Applications / XAMPP / xamppfiles / bin / mysql.server start I had the Manager application open and running ProFTPD and Apache, and then ran the sudo command.

Another suggestion at will, which worked, was to find the /Applications/XAMPP/xamppfiles/etc/my.cnf file and change the read-only permissions for "all".

Another problem I came across is another problem with many solutions - the problem after it all started and then entering localhost which brings me to the xampp splash screen and then nothing. The only thing that worked for me, at least to access the phpMyAdmin page, was to enter localhost / phpmyadmin

I hope this helps others by reading a bunch of threads for an answer.

Regards, Erik

Answer 24

Try this, sudo service mysql stop will stop any other mysql services and then restart xampp

Answer 25

Just click the “Managed Servers” tab in XAMPP MANAGER, select “MySQL Database”, click “Settings” on the right side.

Change the port from 3306 to 3307 and it will work.

Answer 26

This problem had the same problem: all I did was grant read-only permissions to all users and all items included in the following folders:

 /Applications/XAMPP/xamppfiles/etc /Applications/XAMPP/xamppfiles/sbin 

Answer 27

Well, sometimes in the mysql message on the terminal only the ERROR! message is displayed ERROR! . Then just reinstall (overwrite) XAMPP, then it can be solved.

Answer 28

I have the same problem and this error occurs in hostname.err in the directory / Applications / XAMPP / xamppfiles / var / mysql

2016-09-06 15:32:45 140735322399488 [Note] The 'FEEDBACK' plugin is disabled. 2016-09-06 15:32:45 140735322399488 [Note] Heuristic crash recovery mode 2016-09-06 15:32:45 140735322399488 [Note] Please restart mysqld without --tc-heuristic-recover 2016-09-06 15: 32:45 140735322399488 [ERROR] Unable to start tc log 2016-09-06 15:32:45 140735322399488 [ERROR] Cancel

2016-09-06 15:32:48 20004 mysqld_safe mysqld from the pid file /Applications/XAMPP/xamppfiles/var/mysql/hostname.pid has ended

Then I uninstalled tc.log and it works fine after rebooting mysql via manager-osx

Answer 29

This may be due to the fact that another instance of mysqd is already running in your mac-book-pro (MacOs-10). It is almost impossible to kill / pkill mysqld or .... I have tried this way many times, but to no avail. Finally, the following worked for me:

 launchctl unload -w /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist 

wait a few minutes and check

 ps -ef|grep mysqld 

It must be gone!

Answer 30

on

MacOs High Sierra

if mysql does not start working with manager- oxen and tried a direct command, i.e.

sudo/Applications/XAMPP/bin/mysql.server start

also than go to the editing path

/ Applications / XAMPP / xamppfiles / etc. /

find file:

my.cnf

edit this

in the [mysqld] section, add the following line:

 innodb_force_recovery = 1 

after that save and run or can be done from manager- osx

 sudo /Applications/XAMPP/bin/mysql.server start 

this should start mysql.

after its launch you need to edit again

my.cnf

file and delete the line just added

 innodb_force_recovery = 1 

stop and restart mysql again. on command

 sudo /Applications/XAMPP/bin/mysql.server start 

or manager- osx

this will work fine.