sql_cache.cc:1209: void Query_cache::end_of_result(THD*): Assertion `thd->get_stmt_da()->is_eof()' failed | abort (sig=6) at Query_cache::end_of_result

Bug #1234446 reported by Roel Van de Paar on 2013-10-02
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL Server
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
Won't Fix

Bug Description

Thread 11 (LWP 2631):
#0 0x000000363720c69c in pthread_kill () from /lib64/libpthread.so.0
#1 0x00000000006f14bd in handle_fatal_signal (sig=6) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/signal_handler.cc:254
#2 <signal handler called>
#3 0x0000003636e328a5 in raise () from /lib64/libc.so.6
#4 0x0000003636e34085 in abort () from /lib64/libc.so.6
#5 0x0000003636e2ba1e in __assert_fail_base () from /lib64/libc.so.6
#6 0x0000003636e2bae0 in __assert_fail () from /lib64/libc.so.6
#7 0x000000000073a5cc in Query_cache::end_of_result (this=0x156ab80 <query_cache>, thd=0x1a8fb210) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/sql_cache.cc:1209
#8 0x0000000000781006 in dispatch_command (command=<optimized out>, thd=0x1a8fb210, packet=<optimized out>, packet_length=<optimized out>) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/sql_parse.cc:1852
#9 0x0000000000782605 in do_command (thd=0x1a8fb210) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/sql_parse.cc:1051
#10 0x00000000008206b7 in threadpool_process_request (thd=0x1a8fb210) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/threadpool_common.cc:313
#11 0x0000000000823040 in handle_event (connection=0x1b2586a0) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/threadpool_unix.cc:1466
#12 0x0000000000823108 in worker_main (param=0x158fe00 <all_groups+1024>) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/threadpool_unix.cc:1519
#13 0x00000000009ec57a in pfs_spawn_thread (arg=0x1acee7b0) at /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/storage/perfschema/pfs.cc:1858
#14 0x0000003637207851 in start_thread () from /lib64/libpthread.so.0
#15 0x0000003636ee890d in clone () from /lib64/libc.so.6

2013-10-03T06:57:44 [2607] Query: SET GLOBAL INNODB_MAX_CHANGED_PAGES = 0
mysqld: /bzr/5.6-QA_val/Percona-Server-5.6.13-rc60.5/sql/sql_cache.cc:1209: void Query_cache::end_of_result(THD*): Assertion `thd->get_stmt_da()->is_eof()' failed.
20:57:44 UTC - mysqld got signal 6 ;
Some pointers may be invalid and cause the dump to abort.
Query (24f37710): SET GLOBAL 2013-10-03T06:57:44 [2586] Query: FLUSH TABLE `table10_innodb_compressed`
Connection ID (thread ID): 26

Note that the "SET GLOBAL 2013-10-03T06:57:44 [2586] Query: FLUSH TABLE `table10_innodb_compressed`" bit is "inserted" into the error log at the time of printing the query. I think it should be read like this:

This statement was executing: SET GLOBAL INNODB_MAX_CHANGED_PAGES = 0
This statement was about to execute: FLUSH TABLE `table10_innodb_compressed` (or it may have just started?)

Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :

Seen this bug when trying to reproduce bug 1168265. Bugs seem completely unrelated.

Roel Van de Paar (roel11) wrote :

Adding 2nd occurence

Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
Roel Van de Paar (roel11) wrote :
tags: removed: 56qual
Roel Van de Paar (roel11) wrote :

Laurynas reviewed: likely upstream, not 56qual

Ramesh Sivaraman (rameshvs02) wrote :

This bug is also reported in 5.5

Ramesh Sivaraman (rameshvs02) wrote :

PS 5.5 gdb out file

Ramesh Sivaraman (rameshvs02) wrote :
Ramesh Sivaraman (rameshvs02) wrote :

PS 5.5 gdb FULL out file

Roel Van de Paar (roel11) wrote :

Seen in TokuDB RC as well.

Roel Van de Paar (roel11) wrote :

Seen in upstream 5.6.20 - logging bug there

no longer affects: percona-server/5.1
no longer affects: percona-server/5.5
no longer affects: percona-server/5.6
tags: added: upstream
SK (soumya-kandula) wrote :

Any update on this? We are running Percona 5.6.24 and hit this bug today.

mysqld--dbname: /pathtodir/ndn-percona56-5.6.24/sql/sql_cache.cc:1209: void Query_cache::end_of_result(THD*): Assertion `thd->get_stmt_da()->is_eof()' failed.
07:00:01 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/

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2511099 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x5577b40
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 = 2bb05089e78 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 41577817
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.
151208 23:00:01 mysqld_safe Number of processes running now: 0
151208 23:00:01 mysqld_safe mysqld restarted

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-730

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.