Home > database > The mysql database INNODB cannot be started to do ask ace to solve
The mysql database INNODB cannot be started to do ask ace to solve
Time:10-11
The 200528 06:06:01 2020-05-27 17:17:41 mysqld_safe mysqld from pid file/alidata/server/mysql/data/izwz90q83mb4gjptvvinbrz pid ended 200528 17:18:19 mysqld_safe Starting mysqld daemon with databases from/alidata/server/mysql/data The 2020-05-28 17:18:19 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Do use - explicit_defaults_for_timestamp server option (see documentation for more details). The 1448 17:18:19 2020-05-28 [Note] the Plugin 'FEDERATED is disabled. The 2020-05-28 17:18:19 1448 [Note] InnoDB: Using atomics to ref count buffer pool pages The 2020-05-28 17:18:19 1448 InnoDB [Note] : The InnoDB heap memory is disabled The 2020-05-28 17:18:19 1448 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-05-28 17:18:19 1448 InnoDB [Note] : the Memory barrier is not 2 The 2020-05-28 17:18:19 1448 [Note] InnoDB: Compressed tables use zlib 1.2.3 The 2020-05-28 17:18:19 1448 [Note] InnoDB: Using Linux native AIO The 2020-05-28 17:18:19 1448 [Note] InnoDB: Using CPU crc32 instructions The 2020-05-28 17:18:19 1448 [Note] InnoDB: Initializing buffer pool, size=128.0 M The 2020-05-28 17:18:19 InnoDB [Note] : 1448 Completed initialization of buffer pool The 2020-05-28 17:18:19 1448 [Note] InnoDB: Highest supported file format is Barracuda. 17:18:20 InnoDB [Note] : 1448 2020-05-28 128 the rollback segment (s) are active. The 2020-05-28 17:18:20 1448 [Note] InnoDB: Waiting for purge to start The 2020-05-28 17:18:20 1448 [Note] InnoDB: 5.6.21 started; The log sequence number 532176076 09:18:20 UTC - mysqld got signal 11; This could be because you hit a bug. It is also possible that This binary Or one of the libraries it was linked against is corrupt, improperly built, Or misconfigured. This error can also be under caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help Diagnose the problem, but since we have already crashed, Something is definitely wrong and this may fail.
CodePudding user response:
1. Look at the configuration whether there is a mistake? 2. What is the use of installed? Where is the installation path? The corresponding version of the library information check the correct?
Under normal circumstances is the result of the configuration errors