mysqld crash "InnoDB: Failing assertion: new_index"
Bug #613471 reported by
wojtek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Hello,
Our production server crashed today without warning.
It is a shared database, so it's very difficult to debug which query or condition caused the crash.
Recovery went ok, no further crashes.
Server version: 5.1.47-rel11.2-log (Percona Server (GPL), 11.2 )
Regards,
Byte Tech Team
Attached
mysql-error.log + munin graphs
Changed in percona-server: | |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
milestone: | none → 5.1-13.0 |
Changed in percona-server: | |
status: | New → Won't Fix |
To post a comment you must log in.
here is the error log:
100804 14:54:10 [Warning] Invalid (old?) table or database name '#sql2-419b-8d01c6' bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.1/en/ forcing- recovery. html
100804 14:54:12 InnoDB: Assertion failure in thread 140058760623888 in file dict/dict0dict.c line 4854
InnoDB: Failing assertion: new_index
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
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://
InnoDB: about forcing recovery.
100804 14:54:12 - 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.
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.
key_buffer_ size=268435456 size=131072 connections= 317 connected= 33 size)*max_ threads = 1902241 K
read_buffer_
max_used_
max_threads=750
threads_
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x7f61c246bb00 mysqld( my_print_ stacktrace+ 0x29) [0x8ce629] mysqld( handle_ segfault+ 0x3db) [0x5c306b] .so.0(+ 0xef60) [0x7f665417df60] so.6(gsignal+ 0x35) [0x7f6652423175] so.6(abort+ 0x180) [0x7f6652425f80] mysqld( mysql_alter_ table(THD* , char*, char*, st_ha_create_ information* , TABLE_LIST*, Alter_info*, unsigned int, st_order*, bool)+0x28e2) [0x6d5572] mysqld( mysql_execute_ command( THD*)+0xcc0) [0x5d60b0] mysqld( mysql_parse( THD*, char const*, unsigned int, char const**)+0x4af) [0x5dacbf] mysqld( dispatch_ command( enum_server_ command, THD*, char*, unsigned int)+0xd99) [0x5dba69] mysqld( do_command( THD*)+0x12a) [0x5dc38a] mysqld( handle_ one_connection+ 0x34e) [0x5ce87e] .so.0(+ 0x68ba) [0x7f66541758ba] so.6(clone+ 0x6d) [0x7f66524c001d] id=9241040 NOT_KILLED dev.mysql. com/doc/ mysql/en/ crashing. html contains
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 = 0x7f61f8acae88 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
/lib/libc.
/usr/sbin/mysqld() [0x83c1b3]
/usr/sbin/mysqld() [0x7c0d37]
/usr/sbin/mysqld() [0x777f1e]
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7f61f59a1db0 is an invalid pointer
thd->thread_
thd->killed=
The manual page at http://
information that should help you find out what is causing the crash.
100804 14:54:14 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.4
100804 14:54:15 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan prog...