You are not logged in.
Pages: 1
Topic closed
I recently performed an upgrade, rebooted and now mysql isnt starting.
The key error seems to be "[ERROR] Can't init tc log"
Though Im not sure how to fix it.... any tips?
journalctl -f SYSLOG_IDENTIFIER=mysqld
-----------------------------------------------------------------------------------
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] /usr/bin/mysqld (mysqld 10.1.9-MariaDB) starting as process 7903 ...
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: The InnoDB memory heap is disabled
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Memory barrier is not used
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Compressed tables use zlib 1.2.8
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Using Linux native AIO
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Using CPU crc32 instructions
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Completed initialization of buffer pool
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Highest supported file format is Barracuda.
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: 128 rollback segment(s) are active.
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Waiting for purge to start
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 2545546
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690472605440 [Note] InnoDB: Dumping buffer pool(s) not yet started
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] Plugin 'FEEDBACK' is disabled.
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [Note] Recovering after a crash using tc.log
Dec 18 14:08:52 risky.theanthillsocial.co.uk mysqld[7903]: 2015-12-18 14:08:52 139690886637440 [ERROR] Can't init tc log
Dec 18 14:07:21 risky.theanthillsocial.co.uk mysqld[7240]: 2015-12-18 14:07:21 140576698533760 [ERROR] Aborting
Last edited by anthillsocial (2015-12-18 14:15:47)
Offline
Offline
I just ran into this error, "Can't init tc log", running MariaDB.
mysql --version
mysql Ver 15.1 Distrib 10.1.10-MariaDB, for Linux (x86_64) using readline 5.1
I ended up deleting the tc.log file in /var/lib/mysql. When I started mysql again, it created a new tc.log and started up.
Some background on my problem. I had let the partition with /var on it get full. After a reboot mysql wouldn't start, and tc.log was 0B. I cleared up some space but until I deleted tc.log, mysql wouldn't start.
Offline
Solved my issue clean, Thanks!
I ended up deleting the tc.log file in /var/lib/mysql. When I started mysql again, it created a new tc.log and started up.
Offline
This solution of deleting tc.log solved my problem on Debian 9 stable too.
Thank you very much!
Offline
Glad to hear, closing this 3 year old thread though.
Closing.
Offline
Pages: 1
Topic closed