Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Case Analysis of failure to start mysql Database

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

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

This article mainly introduces you to start the mysql database failure case analysis, the contents of the article are carefully selected and edited by the author, start the mysql database failure case analysis has a certain pertinence, for everyone's reference significance is still relatively great, the following with the author to understand the next topic content.

1. Reason

Due to the failure of the company's CVM, the database failed to start due to abnormal downtime.

Error message

[root@15-144dmp] # / etc/init.d/mysqld start

Starting MySQL. ERROR! The server quit without updating PID file (/ opt/mysql/data/15-144.pid).

2. View the mysql log

180625 16:08:17 mysqld_safe Starting mysqld daemon with databases from / opt/mysql/data

2018-06-25 16:08:18 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use-explicit_defaults_for_timestamp server option (see documentation for more details).

2018-06-25 16:08:18 0 [Note] / opt/mysql/bin/mysqld (mysqld 5.6.33) starting as process 22431.

2018-06-25 16:08:18 22431 [Note] Plugin 'FEDERATED' is disabled.

2018-06-25 16:08:18 22431 [Note] InnoDB: Using atomics to ref count buffer pool pages

2018-06-25 16:08:18 22431 [Note] InnoDB: The InnoDB memory heap is disabled

2018-06-25 16:08:18 22431 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2018-06-25 16:08:18 22431 [Note] InnoDB: Memory barrier is not used

2018-06-25 16:08:18 22431 [Note] InnoDB: Compressed tables use zlib 1.2.3

2018-06-25 16:08:18 22431 [Note] InnoDB: Using Linux native AIO

2018-06-25 16:08:18 22431 [Note] InnoDB: Using CPU crc32 instructions

2018-06-25 16:08:18 22431 [Note] InnoDB: Initializing buffer pool, size = 128.0m

2018-06-25 16:08:18 22431 [Note] InnoDB: Completed initialization of buffer pool

2018-06-25 16:08:18 22431 [Note] InnoDB: Highest supported file format is Barracuda.

2018-06-25 16:08:18 22431 [Note] InnoDB: Log scan progressed past the checkpoint lsn 281721748253

2018-06-25 16:08:18 22431 [Note] InnoDB: Database was not shutdown normally!

2018-06-25 16:08:18 22431 [Note] InnoDB: Starting crash recovery.

2018-06-25 16:08:18 22431 [Note] InnoDB: Reading tablespace information from the .ibd files...

2018-06-25 16:08:18 22431 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace zabbix/items_applications uses space ID: 994 at filepath:. / zabbix/items_applications.ibd. Cannot open tablespace dmp/app_model_reuse which uses space ID: 994 at filepath:. / dmp/app_model_reuse.ibd

2018-06-25 16:08:18 7fc2adb7f740 InnoDB: Operating system error number 2 in a file operation.

InnoDB: The error means the system cannot find the path specified.

InnoDB: If you are installing InnoDB, remember that you must create

InnoDB: directories yourself, InnoDB does not create them.

InnoDB: Error: could not open single-table tablespace file. / dmp/app_model_reuse.ibd

InnoDB: We do not continue the crash recovery, because the table may become

InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.

InnoDB: To fix the problem and start mysqld:

InnoDB: 1) If there is a permission problem in the file and mysqld cannot

InnoDB: open the file, you should modify the permissions.

InnoDB: 2) If the table is not needed, or you can restore it from a backup

InnoDB: then you can remove the .ibd file, and InnoDB will do a normal

InnoDB: crash recovery and ignore that table.

InnoDB: 3) If the file system or the disk is broken, and you cannot remove

InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf

InnoDB: and force InnoDB to continue crash recovery here.

180625 16:08:18 mysqld_safe mysqld from pid file / opt/mysql/data/15-144.pid ended

3. Solution

Add configuration / etc/my.cnf

Innodb_force_recovery = 1

File resolution

After reading the above analysis of the failure to start the mysql database, many readers must have some understanding. If you need to get more industry knowledge and information, you can continue to follow our industry information column.

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.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report