Crash in update_global_table_stats
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Incomplete
|
Undecided
|
Unassigned | ||
5.5 |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Percona server 5.5.28-rel29.1-log crashes each time on startup with following stack trace:
130513 11:44:20 mysqld_safe Starting mysqld daemon with databases from /home/mysqladm/
130513 11:44:20 [Warning] Changed limits: max_open_files: 1024 max_connections: 100 table_cache: 457
130513 11:44:20 [Note] Plugin 'FEDERATED' is disabled.
130513 11:44:20 InnoDB: The InnoDB memory heap is disabled
130513 11:44:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130513 11:44:20 InnoDB: Compressed tables use zlib 1.2.3
130513 11:44:20 InnoDB: Using Linux native AIO
130513 11:44:20 InnoDB: Initializing buffer pool, size = 2.0G
130513 11:44:21 InnoDB: Completed initialization of buffer pool
130513 11:44:21 InnoDB: highest supported file format is Barracuda.
[mysqladm@
150525 01:36:55 mysqld_safe Starting mysqld daemon with databases from /home/mysqladm/
150525 1:36:55 [Warning] Changed limits: max_open_files: 1024 max_connections: 100 table_cache: 457
150525 1:36:55 [Note] Plugin 'FEDERATED' is disabled.
06:36:55 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fff6e1811e0
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 = 7fff6e1842f0 thread_stack 0x40000
/home/mysqladm/
/home/mysqladm/
/lib64/
/home/mysqladm/
/home/mysqladm/
/home/mysqladm/
/home/mysqladm/
/home/mysqladm/
/home/mysqladm/
/home/mysqladm/
/home/mysqladm/
/lib64/
/home/mysqladm/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
150525 01:36:55 mysqld_safe mysqld from pid file /home/mysqladm/
Server cannot start, crash started to happen after normal shutdown and following restart of virtual machine where mysqld was running
Workaround: disable userstat
I cannot repeat this yet.
tags: | added: i54655 |
There may be a connection with bug 1417382.
Whilst now the testcase from bug 1417382 produces different results, originally it must have resulted in a (error log) _ZN7handler25up date_global_ table_statsEv stack trace, as this is how it was classified in our bug string search list:
ZN7handler25upd ate_global_ table_statsEv ## http:// bugs.mysql. com/bug. php?id= 75741 (LP PS#1417382)