主页 / dba / 问题 / 71181
Accepted
tcoker
Asked: 2014-07-11 08:08:43 +0800 CST

Percona Server 5.6.19 中的段错误

  • 772

试图弄清楚这里出了什么问题。任何意见，将不胜感激。此服务器正在 CentOS 6.5 上运行新安装的 Percona Server 5.6.19

16:05:46 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://bugs.percona.com/

key_buffer_size=1073741824
read_buffer_size=1048576
max_used_connections=188
max_threads=2002
thread_count=177
connection_count=176
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7228203 K  bytes  of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x17e85e60
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 = 7f7c813f8d40 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8bb80c]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x6504b9]
/lib64/libpthread.so.0[0x3af3a0f710]
/usr/sbin/mysqld(_ZN10ha_archive10unpack_rowEP11azio_streamPh+0xf5)[0xadb385]
/usr/sbin/mysqld(_ZN10ha_archive8rnd_nextEPh+0x7a)[0xadb8ba]
/usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x5d)[0x597c5d]
/usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x20)[0x7f5780]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x101)[0x6adbf1]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x2b8)[0x6ace68]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x275)[0x6f56b5]
/usr/sbin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x165)[0x6f5f15]
/usr/sbin/mysqld[0x559ee0]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1cec)[0x6cfe3c]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5c8)[0x6d5078]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xfa7)[0x6d6807]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x162)[0x6a4882]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6a4970]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0xb0dc13]
/lib64/libpthread.so.0[0x3af3a079d1]
/lib64/libc.so.6(clone+0x6d)[0x3af36e8b5d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f7c380009a0): is an invalid pointer
Connection ID (thread ID): 71
Status: NOT_KILLED
mysql-5.6 percona-server

2 个回答

  1. Best Answer

    在存档引擎上进行全表扫描时，似乎捕获了一个无效指针。我建议您在Percona Server bug tracker上发布跟踪。即使您不是客户，开发人员也非常友好。他们将能够告诉您这是 Percona 特定问题还是上游问题（如果他们更改了存档存储引擎上的任何内容）。

    我自己使用 Archive 引擎的经验是，虽然它对于某些工作负载来说是一个很好的理论引擎，但它目前大部分都没有维护并且没有准备好用于生产，并且存在令人震惊的错误。Percona 不推荐它，如果您担心稳定性，InnoDB compressed 或 TokuDB 可能会更好（无论您运行的是 PS 还是 stock MySQL）。

    • 0

  2. 我已经从源代码顺利运行 percona-server-5.6.19-67.0.tar.gz。我没有繁重的工作量 - 只是想测试一下。你不说你在做什么 - 如果你愿意，我可以尝试运行它。

    您是否安装了旧安装的 MySQL？你跳了几个版本？您的问题可能与此有关。

    • 0

相关问题