Mysql启动失败已解决 悬赏5积分

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: The InnoDB memory heap is disabled

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Compressed tables use zlib 1.2.3.4

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Using SSE crc32 instructions

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Completed initialization of buffer pool

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Highest supported file format is Barracuda.

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: 128 rollback segment(s) are active.

2019-09-30 10:22:30 140685867878208 [Note] InnoDB: Waiting for purge to start

2019-09-30 10:22:31 140685867878208 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1601085

2019-09-30 10:22:31 140685336372992 [Note] InnoDB: Dumping buffer pool(s) not yet started

2019-09-30 10:22:31 140685867878208 [Note] Plugin 'FEEDBACK' is disabled.

2019-09-30 10:22:31 140685867878208 [Note] Recovering after a crash using tc.log

2019-09-30 10:22:31 140685867878208 [ERROR] Can't init tc log

2019-09-30 10:22:31 140685867878208 [ERROR] Aborting