[A版技术问答]新人求助~mysql 启动不了

2016-09-18 10:10:38 8364 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-09-18 10:10:38 8364 [Note] InnoDB: The InnoDB memory heap is disabled
2016-09-18 10:10:38 8364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-09-18 10:10:38 8364 [Note] InnoDB: Memory barrier is not used
2016-09-18 10:10:38 8364 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-09-18 10:10:38 8364 [Note] InnoDB: Not using CPU crc32 instructions
2016-09-18 10:10:38 8364 [Note] InnoDB: Initializing buffer pool, size = 64.0M
2016-09-18 10:10:38 8364 [Note] InnoDB: Completed initialization of buffer pool
2016-09-18 10:10:38 8364 [Note] InnoDB: Highest supported file format is Barracuda.
2016-09-18 10:10:39 8364 [Note] InnoDB: 128 rollback segment(s) are active.
2016-09-18 10:10:39 8364 [Note] InnoDB: Waiting for purge to start
2016-09-18 10:10:39 8364 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 883543007
2016-09-18 10:10:39 6024 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-09-18 10:10:39 8364 [Note] Plugin 'FEEDBACK' is disabled.
2016-09-18 10:10:39 8364 [Note] Recovering after a crash using tc.log
2016-09-18 10:10:39 8364 [ERROR] Bad magic header in tc log
2016-09-18 10:10:39 8364 [ERROR] Crash recovery failed. Either correct the problem (if it's, for example, out of memory error) and restart, or delete tc log and start mysqld with --tc-heuristic-recover={commit|rollback}
2016-09-18 10:10:39 8364 [ERROR] Can't init tc log
2016-09-18 10:10:39 8364 [ERROR] Aborting




如上，各大神 帮忙怎么解决？

端口被占用了？检测下去

先upupw面板输入4检测下3306端口是否被占用，再排除下是否手动修改过my.ini配置，如有修改请改回默认的，从错误日志来看是tc.log文件无法初始化，先删除tc.log再启动。