Bug #68951 Got this crash in 5.5.14
Submitted: 13 Apr 2013 20:21 Modified: 13 May 2013 20:45
Reporter: Greg Kemnitz Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.5.14-enterprise-commercial-advanced-lo OS:Solaris
Assigned to: CPU Architecture:Any
Tags: crash, delete, partition

[13 Apr 2013 20:21] Greg Kemnitz
Description:
In the past couple of days, two separate MySQL instances have crashed in exactly the same way.  The script doing the delete runs every night (and has until now run without incident for about a year on one server, although these are relatively new instances).  

"ga_ar_session_facts" is an InnoDB table partitioned on session_id with no other indexes, and about 50 columns.  "today_sessions" is a temporary memory table created by the script without any indexing.

130413  1:03:45 - mysqld got signal 11 ;
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=2147483648
read_buffer_size=2097152
max_used_connections=46
max_threads=1600
thread_count=37
connection_count=37
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 18498964 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x1c009a8
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...
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:my_print_stacktrace+0x27
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:handle_segfault+0x227
/lib/amd64/libc.so.1:0xdd6b6
/lib/amd64/libc.so.1:0xd1f82
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:0xd69625 [ Signal 11 (SEGV)]
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:0xd697dc
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:0x8b6a5f
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:0x8b6b1e
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cLha_innobaseKdelete_row6MpkC_i_+0x8f
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cHhandlerNha_delete_row6MpkC_i_+0x87
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cMha_partitionKdelete_row6MpkC_i_+0x75
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cHhandlerNha_delete_row6MpkC_i_+0x87
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cMmulti_deleteQdo_table_deletes6MpnFTABLE_b_i_+0x111
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cMmulti_deleteKdo_deletes6M_i_+0x7f
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cMmulti_deleteIsend_eof6M_b_+0x3d
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:0x517b44
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cEJOINEexec6M_v_+0x14cd
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cMmysql_select6FpnDTHD_pppnEItem_pnKTABLE_LIST_IrnEList4n0B___3IpnIst_order_9C39CXpnNselect_result_pnSst_select_le
x_unit_pnNst_select_lex__b_+0x5b6
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cVmysql_execute_command6FpnDTHD__i_+0x2f87
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cLmysql_parse6FpnDTHD_pcIpnMParser_state__v_+0x14f
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cQdispatch_command6FnTenum_server_command_pnDTHD_pcI_b_+0xd4d
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cKdo_command6FpnDTHD__b_+0xcb
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:__1cYdo_handle_one_connection6FpnDTHD__v_+0x132
/opt/mysql/mysql-advanced-5.5.14-solaris10-x86_64/bin/mysqld:handle_one_connection+0x51
/lib/amd64/libc.so.1:0xdd37b
/lib/amd64/libc.so.1:0xdd5b0
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.html
and follow instructions on how to resolve the stack trace.
Resolved stack trace is much more helpful in diagnosing the
problem, so please do resolve it
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (d4d41a58): delete f.*
  from ga_ar_session_facts f, today_sessions t
where f.session_id = t.session_id
Connection ID (thread ID): 8767
Status: NOT_KILLED
 
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.
130413 01:03:56 mysqld_safe mysqld restarted
130413  1:03:57 [Note] Plugin 'FEDERATED' is disabled.
130413  1:03:57 [Note] Plugin 'BLACKHOLE' is disabled.
130413  1:03:57 InnoDB: The InnoDB memory heap is disabled
130413  1:03:57 InnoDB: Mutexes and rw_locks use Solaris atomic functions
130413  1:03:57 InnoDB: Compressed tables use zlib 1.2.3
130413  1:03:57 InnoDB: Initializing buffer pool, size = 16.0G
130413  1:03:59 InnoDB: Completed initialization of buffer pool
130413  1:03:59 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 1011300445736
130413  1:03:59  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 1011304459212
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 11328 row operations to undo
InnoDB: Trx id counter is 538500
130413  1:04:10  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: Starting in background the rollback of uncommitted transactions
130413  1:04:18  InnoDB: Rolling back trx with id 53831C, 11328 rows to undo
 
InnoDB: Progress in percents: 1130413  1:04:18  InnoDB: Waiting for the background threads to start
2 3 4 5 6 7 8 9130413  1:04:19 InnoDB: 1.1.8 started; log sequence number 1011304459212
10 11 12130413  1:04:19 [Warning] 'proxies_priv' entry '@ root@dc1radb01' ignored in --skip-name-resolve mode.
13 14 15 16130413  1:04:20 [Note] Event Scheduler: Loaded 0 events
130413  1:04:20 [Note] /opt/mysql/current/bin/mysqld: ready for connections.
Version: '5.5.14-enterprise-commercial-advanced-log'  socket: '/opt/mysql-data/radb02/logs/mysqld.sock'  port: 3306  MySQL Enterprise Server - Advanced Edition (Commercial)
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 100
InnoDB: Rolling back of trx id 53831C completed
130413  1:04:24  InnoDB: Rollback of non-prepared transactions completed

How to repeat:
the query shown in the dump log below has triggered a server crash twice, although as mentioned, it has also run without incident on our production system for about a year.
[13 Apr 2013 20:45] MySQL Verification Team
Thank you for the bug report. Your server version is quite older please do a test with the lastest release 5.5.30. Thanks.
[14 May 2013 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".