MySQL service restart report MySQL server PID file could not being found!*pid ...

Source: Internet
Author: User

Today just want to express a feeling, at the same time this part of the lesson to write, so that we have an experience, very simple MySQL database setup, there are many installation tutorials on the Internet, do not say much.

I just put out the problems I encountered after installation, to remind myself to wake up, MySQL database after loading (is uninstall removed the previous MySQL reload), I directly started the MySQL service, service MySQL restart, found the following error.

[[Email protected] mysql]# service MySQL restart
MySQL server PID file could not being found! [FAILED]
Starting MySQL ... The server quit without updating PID file [Failed]ysql/localhost.localdomain.pid].
This is the first error, it is obvious and everyone think, certainly is the port or process occupy God horse, execute ps-ef|grep MySQL

[[email protected] mysql]# ps-ef |grep mysql
root       4084       1  1 14:06 pts/0    00:00:00/bin/sh/usr/local/mysql/bin/mysqld_safe--datadir =/data/mysql--pid-file=/data/mysql/localhost.localdomain.pid
mysql      4407    4084  6 14:06 pts/0    00:00:00/usr/local/mysql/bin/mysqld--basedir=/usr/local/mysql-- Datadir=/data/mysql--plugin-dir=/usr/local/mysql/lib/plugin--user=mysql--log-error=/data/mysql/ Localhost.localdomain.err--pid-file=/data/mysql/localhost.localdomain.pid--socket=/data/mysql/mysql.sock--port =3306
root       4437   2771  0 14:06 pts/0    00:00:00 grep mysql
discovery process is not clear, there is residue, very simple direct kill-9 4437 (process number) kill, then the service started normally

I want to configure the MySQL master-slave database, this piece of web also has a lot of references, when the configuration is completed directly restart the service, began to verify the master-slave relationship, then found from the library opened start slave, show slave status\g, found I/O process is no, Obviously I found it must be MY.CNF master-slave configuration file where out of the wrong, was also impatient, is estimated to be a key by mistake, but also self-righteous, not carefully check, then I reboot from the library, there is a back MySQL can not start

This is also like everyone else, online find scenarios and similar cases, kill process, turn off SELinux View Data directory permissions, etc.

Reset Data permissions: Chown mysql.mysql/data/mysql/, the problem still exists,

Open log experience is not enough, think the error is displayed in the recent time (this is my habit * * * wrong habits, do not want to learn)

Tail-30/data/mysql/localhost.localdomain.err (log file path depends on the situation),

160428 13:18:04 [Note] shutting down plugin ' MEMORY '
160428 13:18:04 [Note] shutting down plugin ' Mrg_myisam '
160428 13:18:04 [Note] shutting down plugin ' Mysql_old_password '
160428 13:18:04 [Note] shutting down plugin ' Mysql_native_password '
160428 13:18:04 [Note] shutting down plugin ' Binlog '
160428 13:18:04 [Note]/usr/local/mysql/bin/mysqld:shutdown complete

160428 13:18:04 mysqld_safe mysqld from PID File/data/mysql/localhost.localdomain.pid ended
160428 13:19:43 Mysqld_safe starting mysqld daemon with databases From/data/mysql
160428 13:19:43 innodb:the InnoDB memory heap is di sabled
160428 13:19:43 innodb:mutexes and rw_locks use GCC atomic builtins
160428 13:19:43 innodb:compressed table s use zlib 1.2.3
160428 13:19:43 INNODB:CPU supports CRC32 instructions
160428 13:19:43 innodb:initializing Buffer Pool, size = 128.0M
160428 13:19:43 innodb:completed initialization of buffer pool
160428 13:19:43 innodb:highest Supported file format is Barracuda.
160428 13:19:43 innodb:128 rollback segment (s) is active.
160428 13:19:43 innodb:waiting for the background threads to start
160428 13:19:44 innodb:1.2.4 started; log sequ ence number 1603097
160428 13:19:44 [ERROR]/usr/local/mysql/bin/mysqld:unknown variable ' lob-bin=mysql= Bin '
160428 13:19:44 [ERROR] aborting


160428 13:19:44 [Note] Binlog End
160428 13:19:44 [Note] shutting down plugin ' partition '
160428 13:19:44 [Note] shutting down plugin ' Performance_schema '
160428 13:19:44 [Note] shutting down plugin ' Innodb_sys_foreign_cols '
160428 13:19:44 [Note] shutting down plugin ' innodb_sys_foreign '
160428 13:19:44 [Note] shutting down plugin ' Innodb_sys_fields '

160428 13:19:44 [Note] shutting down plugin ' innodb_sys_columns '
160428 13:19:44 [Note] shutting down plugin ' innodb_sys_indexes '
160428 13:19:44 [Note] shutting down plugin ' innodb_sys_tablestats '
160428 13:19:44 [Note] shutting down plugin ' innodb_sys_tables '

Found/ETC/MY.CNF configuration file There is a place to write the wrong bold display, then very happy, directly corrected, and then restart the discovery of MySQL service is still not working, then I was embarrassed, a variety of search, which I found the log has a record is this

160428 13:18:04 mysqld_safe mysqld from PID File/data/mysql/localhost.localdomain.pid ended

Baidu, Google on the search, but most of the solution is nothing but I mentioned a few steps, in imperceptible, I have taken 2 hours, is ready to reload, suddenly the log to the front more than a few lines, then found an error, I rejoice half a day

160428 11:05:35 [ERROR]/usr/local/mysql/bin/mysqld:unknown variable ' replucate-ignore-db=mysql '
160428 11:05:35 [ERROR] Aborting
Found the word is wrong, it is 2 unfortunate ah, corrected, all normal start

This record only for the carelessness of oneself to wake up!!!!

Normal startup is as follows:

[Email protected] ~]#!se
Service MySQL Restart
Shutting down MySQL. [OK]
Starting MySQL. [OK]

Well, to this end to their own condemnation 650) this.width=650; "alt=" J_0008.gif "src=" Http://img.baidu.com/hi/jx2/j_0008.gif "/>

This article from the "Free Learning" blog, declined reprint!

MySQL service restart report MySQL server PID file could not being found!*pid ...

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.