| Bug #69312 | InnoDB: Assertion failure in thread 47585491499328 in file btr0pcur.c line 250 | ||
|---|---|---|---|
| Submitted: | 24 May 2013 13:40 | Modified: | 28 Apr 2015 12:10 |
| Reporter: | Ignacio Coterillo Coz | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.5.30 | OS: | Linux (RHEL 5.9) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | innodb | ||
[24 May 2013 13:40]
Ignacio Coterillo Coz
[24 May 2013 14:42]
MySQL Verification Team
Thank you for the bug report. If that happens again please try version 5.5.31. Thanks.
[26 May 2013 5:36]
MySQL Verification Team
the reason for asking to test 5.5.31 is we believe this is the same problem reported in http://bugs.mysql.com/bug.php?id=68051
[25 Jun 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".
[28 Apr 2015 11:19]
Robert Roth
I can confirm Shane Bester's hunch on this one being a duplicate of http://bugs.mysql.com/bug.php?id=68051. We've also had this on 5.5.30, on FreeBSD, with most of our tables being InnoDB, , and the crash was caused by killing a slow query started from the mysql console, which makes 68051 even more suspect. Relevant log: len 224; hex 78de2b6d18000000aab2f4591700000000bb29500b00000000000000000000000000000000000000000000000000000003000000000000000300000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000100000000000000b88b15102d0100000000000000000000010000000000000083445107000000007ed74472180000000200000000000000010000000000000000bb29500b000000020000000000000060e11177000000000200000000000000787ecf7d1800000078d74472180000001800000000000000; asc x +m Y )P - DQ ~ Dr )P ` w x~ } x Dr ; TRANSACTION 5E6F9BF97, ACTIVE 8 sec fetching rows, thread declared inside InnoDB 255 mysql tables in use 2, locked 0 MySQL thread id 4195463, OS thread handle 0x186fa5c800, query id 3598715788 localhost root preparing select 'POWEROFF', event_timestamp, resource_id, resourcepos_id, 1, meter_counter from resourcepos where resource_id=10745 and event_type='powerOnEvent' and resourcepos_id not in (select position_id from event_backlog where resource_id=10745) 150428 12:40:48 InnoDB: Assertion failure in thread 104952350720 in file btr0pcur.c line 250 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. 10:40:48 UTC - 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=12884901888 read_buffer_size=4194304 max_used_connections=303 max_threads=800 thread_count=38 connection_count=38 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17507012 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.
