Shulou(Shulou.com)06/01 Report--

The following mainly brings you the main common problems of mysql startup errors. I hope these contents can bring you practical use, which is also the main purpose of this article when I edit mysql startup errors. All right, don't talk too much nonsense, let's just read the following.

You may encounter a variety of problems when starting mysql, but you can't find the error log at this time, just display it on the screen:

Starting MySQL. ERROR! Manager of pid-file quit without updating file.

So let's see 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 error messages:

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

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

So what are the mistakes? the author classifies the mistakes encountered in the experiment in the past few days and shares them with you:

1. / usr/local/mysql/bin/mysqld: File'. / mysql-bin.index' not found (Errcode: 13)

With regard to this error, it is actually a question of permissions. We know that it is not convenient for mysql to be started directly with root users (of course, such as

It's fine if you have to use it, but it's not safe, so we need to create a user named mysql, and then set the

The master and group of the installation directory and data directory are all changed to mysql, which solves the above error. But be careful, if it's on

The operation process is still not smooth. If you encounter all kinds of other errors, the permissions of these two directories may be changed again, so we may have to

Modify permissions for the second time.

2. Mysqld: Table 'mysql.plugin' doesn't exist

If there is such an error in the log, it means that we need to reinitialize the database. If the database is not initialized, we 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 when initializing here, because such an error indicates that when starting

The built-in database cannot be found, and this problem can be solved by initializing it again after specifying the database directory.

3 、 ERROR: 1136 Column count doesn't match value count at row 1

This is because the number of columns in the written SQL statement is not consistent with the number of subsequent values, such as our insert data operation: insert into table name

(field1,field2,field3) values ('axiomadecombinb') so that there are three columns in front and only two values in the back, so this will appear.

Mistake.

However, this error does not seem to affect starting the mysql service. If it fails to start after reinstallation, if this error occurs, it indicates that the original

The installation information was not deleted cleanly.

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

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

If you encounter this error, the installed mysql does not support or does not have an innodb engine, but the configuration file / etc/my.cnf is

Using innodb to work, there is an error.

Solution:

A. Change the configuration file and delete the configuration information related to innodb

B. Dynamically load innodb engine:

First modify the configuration file so that mysql can start normally and delete the ibdata1,ib_datafile0,ib_datafile1 file in the data directory

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

You can load the innodb engine successfully (be sure to delete the files in the data directory first, or there will be an error loading innodb).

5.-- skip-locking' is deprecated and will be removed in a future release. Please use'--

Skip-external-locking' instead.

When we encounter this error, we change the skip-locking field in the configuration file / etc/my.cnf to the skip-external-locking field, namely

It's solvable.

For the above major common questions about mysql startup errors, do you think it is very helpful? If you need to know more, please continue to follow our industry information. I'm sure you'll like it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.