MySQL Startup error issue highlights

When you start MySQL, you may encounter a variety of problems, but you will not find the error log at this time, just display on the screen:

Starting MySQL. error! Manager of Pid-file quit without updating file.

So let's take a look at how to solve these problems.

In the absence of an error log, it is difficult to troubleshoot errors, so we can use another way to generate an error message:

/usr/local/mysql/bin/mysqld or/usr/local/mysql/bin/mysqld_safe

This shows that a. rr file is generated in the data directory, which contains the error message we encountered.

So what are the errors, the author classified a few days in the experiment encountered, and share with you:

1,/usr/local/mysql/bin/mysqld:file './mysql-bin.index ' not Found (errcode:13)

About this error, is actually the authority of the problem, we know that MySQL is not convenient directly with the root user to start (of course, such as

If you want to use it, but it's not safe, but not here, so we need to create a user named MySQL and then put

The owner and group of the installation directory and data directory are all changed to MySQL, which resolves the error above. But note that if the

Dynamic process is not smooth, and encountered other errors, the permissions of these two directories may change, so we may have to

Times to modify permissions.

2, mysqld:table ' mysql.plugin ' doesn ' t exist

If this error occurs in the log, it means that we need to reinitialize the database, and if the database is not initialized, it will not

can generate daemons.

Initialize Database command:

/usr/local/mysql/scripts/mysql_install_db--user=mysql Basedir=/usr/local/mysql Datadir=/data/mysql

Note that the path to the installation directory and the data directory must be added to the initialization here, because the error message is that the boot

The built-in database cannot be found, and the specified database directory is initialized again to resolve the problem.

3, error:1136 Column count doesn ' t match value count at row 1

This is because the number of columns in the SQL statement that is written is inconsistent with the number of subsequent values, such as when we insert a data operation: INSERT into table name

(field1,field2,field3) VALUES (' A ', ' B ') are preceded by three columns, and there are only two values behind it.

Error.

However, this error and the start of the MySQL service does not seem to affect, if the reinstallation after the boot, this error, the original

The installation information is not removed cleanly.

4, [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.

[ERROR]/usr/local/mysql/bin/mysqld:unknown variable ' performance_schema=0 '

If this error is encountered, the installation of MySQL is not supported, or there is no InnoDB engine, but the configuration file/etc/my.cnf is

Using InnoDB to work, there is an error.

Workaround:

A. Change the configuration file to remove the configuration information related to InnoDB

B. Dynamically loading the InnoDB engine:

First modify the configuration file so that MySQL can start normally, delete the Ibdata1,ib_datafile0,ib_datafile1 file under the data directory,

Log in to MySQL after starting the service and use the command INSTALL PLUGIN InnoDB SONAME ' ha_innodb_plugin.so '; This

You can load the InnoDB engine successfully (be sure to delete the files from the data directory first, or the load InnoDB will go wrong).

5, '--skip-locking ' is deprecated and would be removed in a future release. Use '--

skip-external-locking ' instead.

With this error, we changed the skip-locking field in the config file/etc/my.cnf to the Skip-external-locking field.

can be resolved.

This article is from "The Miracle Teenager" blog, please be sure to keep this source http://raffaelexr.blog.51cto.com/8555551/1769375

MySQL Startup error issue highlights