MySQL Crashed and not starting

babu 2016-10-01 22:07:16 UTC #1

Hi,

My dreamfactory server was running fine from last few months and now has stopped working, after reading almost all posts around that issue I've concluded that my MySQL crashed because of some bug, as indicated by the log file.

Please Help

2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Memory barrier is not used
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Using Linux native AIO
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Using SSE crc32 instructions
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Completed initialization of buffer pool
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Highest supported file format is Barracuda.
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: 128 rollback segment(s) are active.
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Waiting for purge to start
2016-10-01 21:55:38 140685172385728 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 6433343
2016-10-01 21:55:38 140685172385728 [Note] Plugin 'FEEDBACK' is disabled.
2016-10-01 21:55:38 140685172385728 [Note] Recovering after a crash using tc.log
2016-10-01 21:55:38 140685172385728 [ERROR] Can't init tc log
2016-10-01 21:55:38 140685172385728 [ERROR] Aborting

161001 21:55:40 mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/mysqld.pid ended
161001 21:56:50 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mysql/data
2016-10-01 21:56:50 140493392377792 [Note] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 10.1.13-MariaDB) starting as process 4784 ...
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: The InnoDB memory heap is disabled
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Memory barrier is not used
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Using Linux native AIO
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Using SSE crc32 instructions
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Completed initialization of buffer pool
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Highest supported file format is Barracuda.
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: 128 rollback segment(s) are active.
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Waiting for purge to start
2016-10-01 21:56:50 140493392377792 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 6433353
2016-10-01 21:56:51 140493392377792 [Note] Plugin 'FEEDBACK' is disabled.
2016-10-01 21:56:51 140493392377792 [Note] Recovering after a crash using tc.log
2016-10-01 21:56:51 140493392377792 [ERROR] Can't init tc log
2016-10-01 21:56:51 140493392377792 [ERROR] Aborting

161001 21:56:53 mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/mysqld.pid ended

babu 2016-10-01 22:09:14 UTC #2

Sorry I think I missed pasting the full log:

2016-10-01 19:33:11 140453126281984 [Note] /opt/bitnami/mysql/bin/mysqld.bin: Normal shutdown

2016-10-01 19:33:11 140453126281984 [Note] Event Scheduler: Purging the queue. 0 events
2016-10-01 19:33:11 140452548273920 [Note] InnoDB: FTS optimize thread exiting.
2016-10-01 19:33:11 140453126281984 [Note] InnoDB: Starting shutdown...
2016-10-01 19:33:12 140453126281984 [Note] InnoDB: Shutdown completed; log sequence number 6433167
161001 19:33:12 [ERROR] mysqld got signal 7 ;
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 caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.1.13-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=6
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467113 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48400
/opt/bitnami/mysql/bin/mysqld.bin(my_print_stacktrace+0x2e)[0xc011ce]
/opt/bitnami/mysql/bin/mysqld.bin(handle_fatal_signal+0x464)[0x7647a4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fbdca797340]
/opt/bitnami/mysql/bin/mysqld.bin(ZN11TCLOG_MMAP5closeEv+0x2a0)[0x835350]
/opt/bitnami/mysql/bin/mysqld.bin[0x51b0c7]
/opt/bitnami/mysql/bin/mysqld.bin[0x522b56]
/opt/bitnami/mysql/bin/mysqld.bin(kill_server_thread+0x10)[0x522f90]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7fbdca78f182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbdc966647d]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
161001 19:33:12 mysqld_safe Number of processes running now: 0
161001 19:33:12 mysqld_safe mysqld restarted
2016-10-01 19:33:13 140588102367168 [Note] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 10.1.13-MariaDB) starting as process 22885 ...
2016-10-01 19:33:13 140588102367168 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-10-01 19:33:13 140588102367168 [Note] InnoDB: The InnoDB memory heap is disabled
2016-10-01 19:33:13 140588102367168 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-10-01 19:33:13 140588102367168 [Note] InnoDB: Memory barrier is not used
2016-10-01 19:33:13 140588102367168 [Note] InnoDB: Compressed tables use zlib 1.2.3

babu 2016-10-01 22:34:00 UTC #3

Hi,

I found a QUICKFIX by deleting the tc.log file as indicated by https://community.bitnami.com/t/mariadb-mysql-error-on-hard-restart/42283

Thanks

jose 2016-10-04 15:47:56 UTC #4

Hello,

Thanks for letting us know! I'm glad you were able to fix your issue. If you have any other question, please don’t hesitate to ask.

Best regards,
Jose

Bitnami provides free all-in-one installers, virtual machines and cloud images for popular open source applications. Get them now!