Comment 8 for bug 798371

Revision history for this message
Dave Drager (ddrager) wrote :

Hello,

Looks like this bug might still be present in latest versions. At least it looks like it is the same bug. Just received the same message/crash on the latest version of Percona-Server, using Percona repositories:

Percona-Server-shared-55-5.5.28-rel29.2.360.rhel6.x86_64
Percona-Server-client-55-5.5.28-rel29.2.360.rhel6.x86_64
Percona-Server-server-55-5.5.28-rel29.2.360.rhel6.x86_64

[root@xxx mysql]# mysqladmin version
mysqladmin Ver 8.42 Distrib 5.5.28, for Linux on x86_64
Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Server version 5.5.28-29.2-log
Protocol version 10
Connection Localhost via UNIX socket
UNIX socket /var/lib/mysql/mysql.sock
Uptime: 21 min 46 sec

Threads: 2 Questions: 65 Slow queries: 0 Opens: 34 Flush tables: 1 Open tables: 27 Queries per second avg: 0.049

** I do have innodb_lazy_drop_table enabled. **

Log follows:

InnoDB: Error: Waited for 570 secs for hash index ref_count (516) to drop to 0.
index: "threadid" table: "forum/threadviews"
InnoDB: Error: Waited for 575 secs for hash index ref_count (516) to drop to 0.
index: "threadid" table: "forum/threadviews"
...
InnoDB: Error: Waited for 590 secs for hash index ref_count (516) to drop to 0.
index: "threadid" table: "forum/threadviews"
InnoDB: Error: Waited for 595 secs for hash index ref_count (516) to drop to 0.
index: "threadid" table: "forum/threadviews"
InnoDB: Error: Waited for 600 secs for hash index ref_count (516) to drop to 0.
index: "threadid" table: "forum/threadviews"
121219 6:42:38 InnoDB: Assertion failure in thread 139966688274176 in file dict0dict.c line 1883
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.
12:42:38 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=6291456000
read_buffer_size=262144
max_used_connections=17
max_threads=1100
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6720683 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x31ad0080
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 = 7f4c88bc1e58 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7ab8b5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6874b4]
/lib64/libpthread.so.0[0x3fa360f500]
/lib64/libc.so.6(gsignal+0x35)[0x3fa32328a5]
/lib64/libc.so.6(abort+0x175)[0x3fa3234085]
/usr/sbin/mysqld[0x8c694e]
/usr/sbin/mysqld[0x8c9f58]
/usr/sbin/mysqld[0x8431ad]
/usr/sbin/mysqld[0x829e49]
/usr/sbin/mysqld(_Z15ha_delete_tableP3THDP10handlertonPKcS4_S4_b+0xae)[0x68cd3e]
/usr/sbin/mysqld(_Z23mysql_rm_table_no_locksP3THDP10TABLE_LISTbbbb+0x804)[0x5eb704]
/usr/sbin/mysqld(_Z11mysql_rm_dbP3THDPcbb+0x89f)[0x56dc0f]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x28a4)[0x58bd84]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x58e0e3]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x15cd)[0x58f75d]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xd7)[0x629c27]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x629d61]
/lib64/libpthread.so.0[0x3fa3607851]
/lib64/libc.so.6(clone+0x6d)[0x3fa32e811d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f4c200049b0): is an invalid pointer
Connection ID (thread ID): 110
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
121219 06:42:38 mysqld_safe Number of processes running now: 0
121219 06:42:38 mysqld_safe mysqld restarted
121219 6:42:39 [Note] Plugin 'FEDERATED' is disabled.
121219 6:42:39 [Warning] option 'innodb-autoextend-increment': unsigned value 209715200 adjusted to 1000
121219 6:42:39 InnoDB: The InnoDB memory heap is disabled
121219 6:42:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121219 6:42:39 InnoDB: Compressed tables use zlib 1.2.3
121219 6:42:39 InnoDB: Using Linux native AIO
121219 6:42:39 InnoDB: Initializing buffer pool, size = 27.3G
121219 6:42:41 InnoDB: Completed initialization of buffer pool
121219 6:42:41 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 247318183283
121219 6:42:41 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 247318183523
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 5 row operations to undo
InnoDB: Trx id counter is 12FA600
121219 6:42:41 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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: Last MySQL binlog file position 0 618692895, file name ./mysql-bin.000177
121219 6:42:43 InnoDB: Rolling back trx with id 12FA423, 5 rows to undo
InnoDB: Dropping table with id 370 in recovery if it exists
InnoDB: Error: trying to load index GEN_CLUST_INDEX for table forum/threadviews
InnoDB: but the index tree has been freed!

InnoDB: Rolling back of trx id 12FA423 completed
121219 6:42:43 InnoDB: Restoring buffer pool pages from ib_lru_dump
121219 6:42:43 InnoDB: Waiting for the background threads to start
121219 6:42:44 Percona XtraDB (http://www.percona.com) 1.1.8-rel29.2 started; log sequence number 247318183523