[MDEV-6440] Innodb assertion failure mysqld got signal 6 Created: 2014-07-12  Updated: 2014-07-29  Resolved: 2014-07-29

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.38
Fix Version/s: 5.5.39

Type: Bug Priority: Major
Reporter: bulepage Assignee: Jan Lindström (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: crash
Environment:

Ubuntu 12.04.4
Linux xxx 3.2.0-60-generic #91-Ubuntu SMP Wed Feb 19 03:54:44 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
mysqld Ver 5.5.38-MariaDB-1~precise-log for debian-linux-gnu on x86_64 (mariadb.org binary distribution)


Attachments: HTML File c1     HTML File c2    

 Description   

On slave server we get signal 6.
core file uploaded to ftp.askmonty.org name mariadb-bug-Assertion_failure_20140712.tgz

InnoDB: Assertion failure in thread 140183668254464 in file srv0srv.c line 2976
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.
140712  8:23:13 [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.38-MariaDB-1~precise-log
key_buffer_size=3221225470
read_buffer_size=8388608
max_used_connections=4
max_threads=501
thread_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20077322 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 0xc8000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xa7499b]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6ccf88]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f847a7e8cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f8478fbe425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7f8478fc1b8b]
/usr/sbin/mysqld[0x840b98]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f847a7e0e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f847907c3fd]
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.
Writing a core file
140712 08:24:44 mysqld_safe Number of processes running now: 0
140712 08:24:44 mysqld_safe mysqld restarted



 Comments   
Comment by Elena Stepanova [ 2014-07-14 ]

Looks like yet another long semaphore wait problem.

Comment by Jan Lindström (Inactive) [ 2014-07-22 ]

Yes and log files do not help as many of the function names are missing, can you use innobase-use-stacktrace=1 ?

Comment by bulepage [ 2014-07-23 ]

I enable innodb_use_stacktrace=1 but since the error does not occur.

Comment by Jan Lindström (Inactive) [ 2014-07-23 ]

Can you repeat it any way at the moment ?

Comment by bulepage [ 2014-07-23 ]

Sorry but we can't repeat it.

Generated at Thu Feb 08 07:11:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.