MISTAKE! MySQL manager or server PID file could not be found! QNAP

I had a problem when MySQL does not start on my QNAP NAS.

I found this first, not being able to log in via phpMyAdmin - I received an error:

#2002 Cannot log in to the MySQL server 

Then I tried to start mysql, as I assume this is a common problem with this, but it just gave a general error.

I went through the diagnostics of the mysql.sock file and everything, changing its permissions, but nothing works.

I rebooted my NAS many times.

In the end, I tried restarting mysql. In doing so, I get:

 ERROR! MySQL manager or server PID file could not be found! 

I cannot find anything specific for QNAP or any general type of troubleshooting for this. Everything I find seems to be related to OSX.

+53
mysql pid qnap
Jul 02 '13 at 11:50
source share
15 answers

I ended up understanding this myself.

Looking for my magazines, I went into

 cd /usr/local/mysql/var 

There I found a file named [MyNAS] .pid (replace [MyNAS] with the name of your NAS.

Then I did the following to delete the file

 rm -rf /usr/local/mysql/var/[MyNAS].pid 

Then I restarted mysql

 [/usr/local/mysql/var] # /etc/init.d/mysqld.sh restart /mnt/ext/opt/mysql /mnt/ext/opt/mysql Try to shutting down MySQL ERROR! MySQL manager or server PID file could not be found! /mnt/ext/opt/mysql Starting MySQL. SUCCESS! 

I tested everything and it all works like a charm again!

+14
Jul 02 '13 at 21:41
source share

After a big search, I was able to fix the "PID file not found" error on my machine. I am on OS X 10.9.3 and installed mysql via Homebrew.

First I found my PID file here:

 /usr/local/var/mysql/{username}.pid 

Then I found the my.cnf file here:

 /usr/local/Cellar/mysql/5.6.19/my.cnf 

Finally, I added this line to the end of my.cnf:

 pid-file = /usr/local/var/mysql/{username}.pid 

Hope this works for someone else and saves you a headache! Remember to replace {username} with your machine name (jeffs-air-2 in my case).

+68
Jul 09 '14 at 23:31
source share

I tried all the above, but did not see the results, until I got a hint from here: https://superuser.com/questions/159486/how-to-kill-process-in-mac-os-x-and-not-have- it-restart-on-its-own

In the end, I switched to the activity monitor on my Mac, forcibly quit the PID and ran the command:

 sudo /usr/local/mysql/support-files/mysql.server restart 

The magic was done !!!

+33
Sep 28 '13 at 13:53 on
source share

If you installed MySQL using brew, the best way to go would be with homebrew

 brew services restart mysql 

after running this command, all problems generated during the upgrade will be fixed.

+21
Oct. 31 '16 at 19:18
source share

Run the commands below and it will work.

Go to the terminal and type

 sudo chown -RL root:mysql /usr/local/mysql sudo chown -RL mysql:mysql /usr/local/mysql/data sudo /usr/local/mysql/support-files/mysql.server start 
+5
Apr 08 '17 at 6:48
source share

Just start mysqld (do not run as root) from your terminal. Your mysql server will restart and reset everything as shown in the figure below:

enter image description here

And use this command:

 mysql -u root -h 127.0.0.1 
+4
Aug 09 '16 at 17:28
source share

I had the same problem. Turns out I added the wrong variables to my.cnf. As soon as I deleted them and restarted mysql, it did not start without problems.

+1
Aug 09 '14 at 6:04 on
source share

Make sure your server is full first, this is a common reason (it is not possible to create a PID file because you do not have space). Run this to check your disk usage.

 df -h 

If you get something like this, you are full.

 Filesystem Size Used Avail Use% Mounted on /dev/vda1 40G 40G 6.3M 100% / 

In this case, you need to start looking for what to remove in order to free up space, or add an additional disk to your server.

+1
Sep 29 '17 at 12:37 on
source share

MISTAKE! MySQL server PID file not found!

This may be due to problems with disk space, use of an inode disk or damage to innodb, which can lead to an error.

The problem was the pid file, and the solution was:

  • SSH login to the server as root

  • Create directory / var / run / mysql

mkdir / var / run / mysql

3) Create a file named as mysqld.pid

tap mysqld.pid

  1. Change its ownership and group to mysql: mysql

    chown mysql: mysql mysqld.pid

  2. Restart MySQL service

Done!

+1
Oct 16 '17 at 5:35
source share

I have the same problem. I found the file {username} .local.err instead of {username} .local.pid inside / usr / local / mysql, then I change the name * .err to * .pid and it works fine. Starting MySQL SUCCESS!

My OS El Capitan 10.11.5

0
Jun 10 '16 at 3:59
source share

I know this is an old post, but I ran into ERROR! MySQL server PID file could not be found! ERROR! MySQL server PID file could not be found! ERROR! MySQL server PID file could not be found! when trying to start MySQL after updating my.cnf file. I did the following to solve the problem:

  1. Removed my experimental upgrade to my.cnf

  2. .net.err files are .net.pid and .net.err .

 delete /usr/local/var/mysql/**<YourUserName>**-MBP.airstreamcomm.net.* 
  1. It is guaranteed that all MySQL processes are stopped.
 ps -ax | grep mysql kill **<process id>** 
  1. Launched the MySQL server as usual.
 mysql.server start 
0
Aug 24 '18 at 18:26
source share

First find the mysql service PID

 ps aux | grep mysql 

Then you have to kill the process

  sudo kill <pid> 

After you start the MySQL service again

 mysql.server start 
0
Sep 24 '18 at 6:38
source share

After setting up PHPMyAdmin, I ran into the same problem,

Something. Like this

  • Then I just stopped the MYSQL server, going into the system settings, and then started it again, and it worked.
0
Jun 11 '19 at 6:40
source share

screenshot

If you use MySQL Workbench, mysql.server stop/restart/start will not work.

You will need to enter the working environment and click "turn off the server." See image attached.

-2
May 22 '18 at 17:15
source share

I managed to solve this problem on OS X by disabling the existing mysql.server that was running:

 mysql.server stop 

Start:

 mysql.server start 

From there, I could start mysql.server restart without throwing the ERROR.

-four
Apr 11 '16 at 17:37
source share



All Articles