[已解决] percona server 5.7.26.29 mysqld got signal 11

587 3 2022-12-9 12:00

percona server 5.7.26.29  mysqld got signal 11

mysql crash 并且一直重启
具体err日志信息如下，问题发生时间点是2022-12-06 下午14:36分

06:36:53 UTC - mysqld got signal 11 ;
This couldyy 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

key_buffer_size=67108864
read_buffer_size=2097152
max_used_connections=478
max_threads=100001
thread_count=159
connection_count=158
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 614486807 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x6f44ca0
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 = 7f51b1ad9c40 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf1444b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0xd4e981]
/lib64/libpthread.so.0(+0xf6d0)[0x7f5f58a496d0]
/usr/sbin/mysqld(_ZN10Item_fieldC1EP3THDP23Name_resolution_contextP5Field+0x25)[0x7c5d65]
/usr/sbin/mysqld(_ZN20Field_iterator_table11create_itemEP3THD+0x4b)[0xd0c1db]
/usr/sbin/mysqld(_Z13insert_fieldsP3THDP23Name_resolution_contextPKcS4_P13List_iteratorI4ItemEb+0x4c5)[0xc14d95]
/usr/sbin/mysqld(_ZN13st_select_lex10setup_wildEP3THD+0x1b8)[0xca3ca8]
/usr/sbin/mysqld(_ZN13st_select_lex7prepareEP3THD+0x3cb)[0xca8a5b]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x2b9)[0xcad219]
/usr/sbin/mysqld[0x76afc6]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x463a)[0xc6f00a]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_stateb+0x455)[0xc72335]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xb27)[0xc72f47]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x1df)[0xc749ef]
/usr/sbin/mysqld(_Z26threadpool_process_requestP3THD+0xcf)[0xd1e13f]
/usr/sbin/mysqld[0xd2de0e]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xf2c6b4]
/lib64/libpthread.so.0(+0x7e25)[0x7f5f58a41e25]
/lib64/libc.so.6(clone+0x6d)[0x7f5f56c11bad]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (618e220): SELECT * FROM access_device_auth_ability WHERE device_model IN  (  'DS-K5671-ZU-QR' )
Connection ID (thread ID): 5602337
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.
2022-12-06T06:36:58.422898Z 0 [Warning] Could not increase number of max_open_files to more than 5000 (request: 204800)
2022-12-06T06:36:58.423137Z 0 [Warning] Changed limits: table_open_cache: 1745 (requested 8192)
2022-12-06T14:36:58.543558+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-12-06T14:36:58.543573+08:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 06:37:49 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

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

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf1444b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0xd4e981]
/lib64/libpthread.so.0(+0xf6d0)[0x7f882e9246d0]
/usr/sbin/mysqld(_Z23page_cur_insert_rec_lowPhP12dict_index_tPKhPmP5mtr_t+0x2fb)[0x1045cab]
/usr/sbin/mysqld(_Z25page_cur_parse_insert_recmPKhS0_P11buf_block_tP12dict_index_tP5mtr_t+0x675)[0x1048655]
/usr/sbin/mysqld[0x101ef47]
/usr/sbin/mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0xa25)[0x101fbe5]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x883)[0x11a08a3]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x23e)[0x1219ace]
/usr/sbin/mysqld(io_handler_thread+0xc0)[0x10fcb20]
/lib64/libpthread.so.0(+0x7e25)[0x7f882e91ce25]
/lib64/libc.so.6(clone+0x6d)[0x7f882caecbad]
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.
2022-12-06T06:37:54.401481Z 0 [Warning] Could not increase number of max_open_files to more than 5000 (request: 204800)
2022-12-06T06:37:54.401660Z 0 [Warning] Changed limits: table_open_cache: 1745 (requested 8192)
2022-12-06T14:37:54.523503+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-12-06T14:37:54.523518+08:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 06:38:37 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

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

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf1444b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0xd4e981]
/lib64/libpthread.so.0(+0xf6d0)[0x7f47e1ce96d0]
/usr/sbin/mysqld(_Z23page_cur_insert_rec_lowPhP12dict_index_tPKhPmP5mtr_t+0x2fb)[0x1045cab]
/usr/sbin/mysqld(_Z25page_cur_parse_insert_recmPKhS0_P11buf_block_tP12dict_index_tP5mtr_t+0x675)[0x1048655]
/usr/sbin/mysqld[0x101ef47]
/usr/sbin/mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0xa25)[0x101fbe5]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x883)[0x11a08a3]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x23e)[0x1219ace]
/usr/sbin/mysqld(io_handler_thread+0xc0)[0x10fcb20]
/lib64/libpthread.so.0(+0x7e25)[0x7f47e1ce1e25]
/lib64/libc.so.6(clone+0x6d)[0x7f47dfeb1bad]
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.
2022-12-06T06:38:43.151071Z 0 [Warning] Could not increase number of max_open_files to more than 5000 (request: 204800)
2022-12-06T06:38:43.151263Z 0 [Warning] Changed limits: table_open_cache: 1745 (requested 8192)
2022-12-06T14:38:43.273511+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2022-12-06T14:38:43.273524+08:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 06:39:26 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at https://bugs.percona.com/

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

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf1444b]
/usr/sbin/mysqld(handle_fatal_signal+0x471)[0xd4e981]
/lib64/libpthread.so.0(+0xf6d0)[0x7fb377cb36d0]
/usr/sbin/mysqld(_Z23page_cur_insert_rec_lowPhP12dict_index_tPKhPmP5mtr_t+0x2fb)[0x1045cab]
/usr/sbin/mysqld(_Z25page_cur_parse_insert_recmPKhS0_P11buf_block_tP12dict_index_tP5mtr_t+0x675)[0x1048655]
/usr/sbin/mysqld[0x101ef47]
/usr/sbin/mysqld(_Z22recv_recover_page_funcmP11buf_block_t+0xa25)[0x101fbe5]
/usr/sbin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x883)[0x11a08a3]
/usr/sbin/mysqld(_Z12fil_aio_waitm+0x23e)[0x1219ace]
/usr/sbin/mysqld(io_handler_thread+0xc0)[0x10fcb20]
/lib64/libpthread.so.0(+0x7e25)[0x7fb377cabe25]
/lib64/libc.so.6(clone+0x6d)[0x7fb375e7bbad]
You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information

附加信息
  1 这个percona是使用docker启动的
  2 针对crash前查询的sql的表中进行innodbchecksum ibd文件发现没有page损坏
  3 宿主机操作系统 message中检查过没有报错

全部回复(3)

只看楼主