Mariadb Crashed ,Error InnoDB: Assertion failure in thread
rajnish...@gmail.com
I am using mariadb Version 10.0.16-MariaDB-log MariaDB Server ,Sudden I found I am unable to login into my Database server ,When I logged in into server and found mariadb is not running , When I go through Error log below error message I found there.
7fc5b33f7700 InnoDB: Assertion failure in thread 140487092565760 in file fsp0fsp.cc line 1896
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
150813 15:35:10 [ERROR] mysqld got signal 6 ;
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 http://kb.askmonty.org/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.0.16-MariaDB-log
key_buffer_size=268435456
read_buffer_size=1048576
max_used_connections=88
max_threads=153
thread_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 578634 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 0x48000
Fatal signal 11 while backtracing
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb73d3b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x726518]
/lib64/libpthread.so.0[0x3f7bc0f710]
/lib64/libc.so.6(gsignal+0x35)[0x3f7b832925]
/lib64/libc.so.6(abort+0x175)[0x3f7b834105]
/usr/sbin/mysqld[0x532318]
/usr/sbin/mysqld[0x9f617f]
/usr/sbin/mysqld[0x96e24a]
/usr/sbin/mysqld[0x9da109]
/usr/sbin/mysqld[0x9ddc6d]
/usr/sbin/mysqld[0x9def97]
/lib64/libpthread.so.0[0x3f7bc079d1]
/lib64/libc.so.6(clone+0x6d)[0x3f7b8e8b6d]
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.
150813 15:49:37 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
150813 15:49:38 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
150813 15:49:38 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150813 15:49:38 [Note] InnoDB: The InnoDB memory heap is disabled
150813 15:49:38 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150813 15:49:38 [Note] InnoDB: Memory barrier is not used
150813 15:49:38 [Note] InnoDB: Compressed tables use zlib 1.2.3
150813 15:49:38 [Note] InnoDB: Using Linux native AIO
150813 15:49:38 [Note] InnoDB: Using CPU crc32 instructions
150813 15:49:38 [Note] InnoDB: Initializing buffer pool, size = 128.0M
150813 15:49:38 [Note] InnoDB: Completed initialization of buffer pool
150813 15:49:38 [Note] InnoDB: Highest supported file format is Barracuda.
150813 15:49:38 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2315314209
150813 15:49:38 [Note] InnoDB: Database was not shutdown normally!
150813 15:49:38 [Note] InnoDB: Starting crash recovery.
150813 15:49:38 [Note] InnoDB: Reading tablespace information from the .ibd files...
150813 15:49:46 [Note] InnoDB: Restoring possible half-written data pages
150813 15:49:46 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2315319647
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 1 row operations to undo
InnoDB: Trx id counter is 13580544
150813 15:49:47 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 31832031, file name ./Mariadb-binlog.000006
InnoDB: Starting in background the rollback of uncommitted transactions
150813 15:49:49 [Note] InnoDB: 128 rollback segment(s) are active.
2015-08-13 15:49:49 7f2c007ff700 InnoDB: Rolling back trx with id 13580247, 1 rows to undo
150813 15:49:49 [Note] InnoDB: Waiting for purge to start
150813 15:49:49 [Note] InnoDB: Rollback of trx with id 13580247 completed
2015-08-13 15:49:49 7f2c007ff700 InnoDB: Rollback of non-prepared transactions completed
150813 15:49:52 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.22-71.0 started; log sequence number 2315319647
150813 15:50:08 [Note] Plugin 'FEEDBACK' is disabled.
150813 15:50:08 [Note] Recovering after a crash using Mariadb-binlog
150813 15:50:29 [Note] Starting crash recovery...
150813 15:50:31 [Note] Crash recovery finished.
150813 15:50:31 [Note] Server socket created on IP: '::'.
150813 15:50:37 [Note] Event Scheduler: Loaded 0 events
150813 15:50:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.16-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
Strange thing when I tried to start mariadb it falling after few minutes I again start it started and till now it is running fine.
I try to search the root cause for the same but not found any convincing result.
I am little worried if mariadb crashing like this time it is really a big pain for us to use it in production env.