Mysql error manager of pid file quit without updating file
Thanks Manivannan S DISCLAIMER: This email message and all attachments are confidential and may contain information that is privileged, confidential or exempt from disclosure under applicable law.
If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited.
If you have received this email in error, please notify us immediately by return email or to [email protected] and destroy the original message.
Hi, In 64-bit Linux(Centos/Red Hat) machine when I am trying to start the My SQL service by using service mysql start command , I am getting the following error Ø Starting My SQL.
Manager of pid-file quit without updating file [FAILED] If I try to stop the My SQL service I am getting this error Ø My SQL manager or server PID file could not be found!
[FAILED] When I try to start My SQL service from /etc/init.d/mysql start Ø ERROR 2002 (HY000): Can't connect to local My SQL server through socket '/var/lib/mysql/mysql.sock' (111) I have installed My SQL-client-5.1.52-1.glibc23.x86_64My SQL-server-5.1.52-1.glibc23.x86_64In my Linux machine.
Does anyone know how to solve this issue in My SQL?
Nevada3:mysql kb1$ cd /usr/local/var/mysql/ Nevada3:mysql kb1$ ls -lsa total 221296 0 drwxr-xr-x 19 kb1 admin 646 9 Dec . 32 -rw-r----- 1 kb1 admin 15184 9 Dec Nevada3.8 -rw-r----- 1 kb1 admin 56 9 Dec 8 -rw------- 1 kb1 admin 1676 9 Dec 8 -rw-r--r-- 1 kb1 admin 1071 9 Dec 8 -rw-r--r-- 1 kb1 admin 1079 9 Dec 8 -rw------- 1 kb1 admin 1680 9 Dec 8 -rw-r----- 1 kb1 admin 303 9 Dec ib_buffer_pool 98304 -rw-r----- 1 kb1 admin 50331648 9 Dec ib_logfile0 98304 -rw-r----- 1 kb1 admin 50331648 9 Dec ib_logfile1 24576 -rw-r----- 1 kb1 admin 12582912 9 Dec ibdata1 0 drwxr-x--- 77 kb1 admin 2618 9 Dec mysql 0 drwxr-x--- 90 kb1 admin 3060 9 Dec performance_schema 8 -rw------- 1 kb1 admin 1680 9 Dec private_8 -rw-r--r-- 1 kb1 admin 452 9 Dec public_8 -rw-r--r-- 1 kb1 admin 1079 9 Dec 8 -rw------- 1 kb1 admin 1676 9 Dec 0 drwxr-x--- 108 kb1 admin 3672 9 Dec sys Nevada3:mysql kb1$ Nevada3:mysql kb1$ tail Nevada3.2015-12-09T.576656Z 0 [Note] Inno DB: Shutdown completed; log sequence number 2471965 2015-12-09T.577321Z 0 [Note] Inno DB: Removed temporary tablespace data file: "ibtmp1" 2015-12-09T.577335Z 0 [Note] Shutting down plugin 'MEMORY' 2015-12-09T.577341Z 0 [Note] Shutting down plugin 'CSV' 2015-12-09T.577346Z 0 [Note] Shutting down plugin 'sha256_password' 2015-12-09T.577350Z 0 [Note] Shutting down plugin 'mysql_native_password' 2015-12-09T.577470Z 0 [Note] Shutting down plugin 'binlog' 2015-12-09T.577946Z 0 [Note] /usr/local/Cellar/mysql/5.7.9/bin/mysqld: Shutdown complete 151209 mysqld_safe mysqld from pid file /usr/local/var/mysql/Nevada3.ended These steps worked for me.
From my understanding, this occurs because mysql server is running durning the update, eventually causes an error creating the error file, preventing the start upon successful update.I think stoping mysql immediately before the updating will prevent this issue in the future.You would of course have to restart mysql after the update, but would not need to find and delete the file.BACKGROUND: I installed Percona Server on a fresh Centos 6.4 minimal. Prior to this, I have never installed My SQL (though I'm not sure if Centos 6.4 minimal came with My SQL? ) Anyway, here are the commands I used: Everything seems installed properly. 1) How come, unlike My SQL, did it not prompt me for creation of root password? 2) When I tried starting Percona My SQL with the command "/etc/init.d/mysql start", it gave me the error: Starting My SQL (Percona Server). The server quit without updating PID file (/var/lib/mysql/mail.pid) Of course, here I used in place of my real domain name.