Bug #90911 MySQL Instance sudden restart
Submitted: 17 May 2018 10:20 Modified: 30 Sep 2018 3:18
Reporter: w yj Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Information schema Severity:S1 (Critical)
Version:5.7.19 OS:CentOS (2.6.32-642.6.2.el6.x86_64)
Assigned to: CPU Architecture:Any

[17 May 2018 10:20] w yj
Description:
Show full processlist monitoring is performed every minute in my environment.

This morning it was suddenly restarted.

00:43:02 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.
key_buffer_size=209715200
read_buffer_size=1048576
max_used_connections=10
max_threads=3000
thread_count=15
connection_count=4
 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27892831 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2abc4c0be8b0
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 = 2abc4803fe28 thread_stack 0x40000
/apps/svr/mysql57/bin/mysqld(my_print_stacktrace+0x35)[0xf45e05]
/apps/svr/mysql57/bin/mysqld(handle_fatal_signal+0x4a4)[0x7cd464]
/lib64/libpthread.so.0[0x382b00f7e0]
/lib64/libc.so.6(memcpy+0x3a1)[0x382ac89a51]
/apps/svr/mysql57/bin/mysqld(strmake_root+0x39)[0xf3e7f9]
/apps/svr/mysql57/bin/mysqld(_ZN17List_process_listclEP3THD+0x345)[0xd71db5]
/apps/svr/mysql57/bin/mysqld(_ZN18Global_THD_manager19do_for_all_thd_copyEP11Do_THD_Impl+0x25d)[0x7cbf0d]
/apps/svr/mysql57/bin/mysqld(_Z21mysqld_list_processesP3THDPKcb+0xfc8)[0xd69ef8]
/apps/svr/mysql57/bin/mysqld(_Z21mysql_execute_commandP3THDb+0xb29)[0xd13949]
/apps/svr/mysql57/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3a5)[0xd18245]
/apps/svr/mysql57/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11af)[0xd1945f]
/apps/svr/mysql57/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1a324]
/apps/svr/mysql57/bin/mysqld(handle_connection+0x29c)[0xdea0fc]
/apps/svr/mysql57/bin/mysqld(pfs_spawn_thread+0x174)[0xfbdbf4]
/lib64/libpthread.so.0[0x382b007aa1]
/lib64/libc.so.6(clone+0x6d)[0x382ace8bcd]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2abc4c12e8a0): is an invalid pointer
Connection ID (thread ID): 12408003
Status: NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
i don’t know
[17 May 2018 10:31] w yj
This is a slave,  concurrent replication.
[24 May 2018 3:21] Bogdan Kecman
Hi,
Yes, we are aware of this problem. Current SHOW PROCESSLIST implementation has issues with multi-thread-execution. We are working on replacing the show processlist implementation but I can't give you a timeline for that.

As a workaround you can use:
SELECT * FROM performance_schema.threads;

or to get more similar data:
SELECT 
  THREAD_ID AS Id, 
  PROCESSLIST_USER AS User, 
  PROCESSLIST_HOST AS Host, 
  PROCESSLIST_DB AS db, 
  PROCESSLIST_COMMAND AS Command, 
  PROCESSLIST_TIME AS Time, 
  PROCESSLIST_STATE AS State, 
  PROCESSLIST_INFO AS Info  
FROM performance_schema.threads 
WHERE 
  PROCESSLIST_USER IS NOT NULL;

kind regards
Bogdan
[30 Sep 2018 3:18] w yj
i try the following SQL,but it still crash

select * from information_schema.PROCESSLIST  where info is not null;

00:41:11 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.

key_buffer_size=209715200
read_buffer_size=1048576
max_used_connections=9
max_threads=3000
thread_count=14
connection_count=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 27892831 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2b39d00008c0
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 = 2b39cd075e28 thread_stack 0x40000
/apps/svr/mysql57/bin/mysqld(my_print_stacktrace+0x35)[0xf45e05]
/apps/svr/mysql57/bin/mysqld(handle_fatal_signal+0x4a4)[0x7cd464]
/lib64/libpthread.so.0[0x382b00f7e0]
/lib64/libc.so.6(memcpy+0xd2)[0x382ac89782]
/apps/svr/mysql57/bin/mysqld(_ZN6String6appendEPKcm+0x9a)[0xde8c7a]
/apps/svr/mysql57/bin/mysqld(thd_security_context+0x1df)[0xcd524f]
/apps/svr/mysql57/bin/mysqld(_Z24innobase_mysql_print_thdP8_IO_FILEP3THDj+0x25)[0x1030015]
/apps/svr/mysql57/bin/mysqld(_Z34lock_trx_print_wait_and_mvcc_stateP8_IO_FILEPK5trx_t+0x43)[0x1083df3]
/apps/svr/mysql57/bin/mysqld(_Z32lock_print_info_all_transactionsP8_IO_FILE+0x1bd)[0x108617d]
/apps/svr/mysql57/bin/mysqld(_Z25srv_printf_innodb_monitorP8_IO_FILEmPmS1_+0x1fd)[0x114ee9d]
/apps/svr/mysql57/bin/mysqld[0x1045921]
/apps/svr/mysql57/bin/mysqld(_Z14ha_show_statusP3THDP10handlerton12ha_stat_type+0x3ff)[0x81cf3f]
/apps/svr/mysql57/bin/mysqld(_Z21mysql_execute_commandP3THDb+0xcb1)[0xd13ad1]
/apps/svr/mysql57/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3a5)[0xd18245]
/apps/svr/mysql57/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11af)[0xd1945f]
/apps/svr/mysql57/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1a324]
/apps/svr/mysql57/bin/mysqld(handle_connection+0x29c)[0xdea0fc]
/apps/svr/mysql57/bin/mysqld(pfs_spawn_thread+0x174)[0xfbdbf4]
/lib64/libpthread.so.0[0x382b007aa1]
/lib64/libc.so.6(clone+0x6d)[0x382ace8bcd]

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.