← Back to team overview

maria-discuss team mailing list archive

InnoDB: Assertion failure in thread 139652707100416 in file buf0buf.c line 4172

 

Hi

after chnage to MariaDB i faced tonight that the third time
on one of our dbmail-replication-slaves while that never
happened with MySQL over years :-(

140221  3:19:50  InnoDB: Assertion failure in thread 139652707100416 in file buf0buf.c line 4172
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
140221  3:19:50 [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: 5.5.35-MariaDB
key_buffer_size=10485760
read_buffer_size=131072
max_used_connections=1
max_threads=502
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 211932 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
/usr/libexec/mysqld(my_print_stacktrace+0x2e)[0x7f037fbde42e]
/usr/libexec/mysqld(handle_fatal_signal+0x505)[0x7f037f847a25]
/lib64/libpthread.so.0(+0xef90)[0x7f037d686f90]
/lib64/libc.so.6(gsignal+0x39)[0x7f037d2ec9e9]
/lib64/libc.so.6(abort+0x148)[0x7f037d2ee0f8]
/usr/libexec/mysqld(+0x63f008)[0x7f037fa03008]
/usr/libexec/mysqld(+0x676218)[0x7f037fa3a218]
/usr/libexec/mysqld(+0x5f8048)[0x7f037f9bc048]
/lib64/libpthread.so.0(+0x7c53)[0x7f037d67fc53]
/lib64/libc.so.6(clone+0x6d)[0x7f037d3acdbd]
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.
140221  3:19:52 InnoDB: The InnoDB memory heap is disabled
140221  3:19:52 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140221  3:19:52 InnoDB: Compressed tables use zlib 1.2.7
140221  3:19:52 InnoDB: Using Linux native AIO
140221  3:19:52 InnoDB: Initializing buffer pool, size = 64.0M
140221  3:19:52 InnoDB: Completed initialization of buffer pool
140221  3:19:52 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 153930874326
140221  3:19:52  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 153931613156
140221  3:19:53  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 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: In a MySQL replication slave the last master binlog file
InnoDB: position 75471956, file name bin.000375
InnoDB: and relay log file
InnoDB: position 75472234, file name ./mysql-relay-bin.001426
InnoDB: Last MySQL binlog file position 0 1179902, file name /data/mysql/mysql_dbmail/bin.000224
140221  3:19:53  InnoDB: Waiting for the background threads to start
140221  3:19:54 Percona XtraDB (http://www.percona.com) 5.5.35-MariaDB-33.0 started; log sequence number 153931613156
140221  3:19:54 [Note] Plugin 'FEDERATED' is disabled.
140221  3:19:54 [Note] Plugin 'FEEDBACK' is disabled.
140221  3:19:54 [Note] Server socket created on IP: '0.0.0.0'.
140221  3:19:55 [Note] Slave SQL thread initialized, starting replication in log 'bin.000375' at position 75471956,
relay log './mysql-relay-bin.001426' position: 75472234
140221  3:19:55 [Note] Slave I/O thread: connected to master 'replication@******:3307',replication started in log
'bin.000376' at position 245
140221  3:19:55 [Note] Event Scheduler: Loaded 0 events
140221  3:19:55 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.35-MariaDB'  socket: '/var/lib/mysql/mysqld_dbmail.sock'  port: 3307

Attachment: signature.asc
Description: OpenPGP digital signature