Description:
mysql version
5.7.23-log MySQL Community Server (GPL)
here is error log output
00:53: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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=72
max_threads=1000
thread_count=35
connection_count=35
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 405567 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fc850141870
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 = 7fc894c91e28 thread_stack 0x40000
/usr/local/mysql57/bin/mysqld(my_print_stacktrace+0x35)[0xf4e5e5]
/usr/local/mysql57/bin/mysqld(handle_fatal_signal+0x4a4)[0x7d1b64]
/lib64/libpthread.so.0[0x3c4fa0f7e0]
/usr/local/mysql57/bin/mysqld(_Z18mysqld_show_createP3THDP10TABLE_LIST+0x9e7)[0xd73ad7]
/usr/local/mysql57/bin/mysqld(_Z21mysql_execute_commandP3THDb+0x168a)[0xd17dba]
/usr/local/mysql57/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x40d)[0xd1b97d]
/usr/local/mysql57/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x11a5)[0xd1cba5]
/usr/local/mysql57/bin/mysqld(_Z10do_commandP3THD+0x194)[0xd1da54]
/usr/local/mysql57/bin/mysqld(handle_connection+0x29c)[0xdef3fc]
/usr/local/mysql57/bin/mysqld(pfs_spawn_thread+0x174)[0xfc79a4]
/lib64/libpthread.so.0[0x3c4fa07aa1]
/lib64/libc.so.6(clone+0x6d)[0x3c4f6e8aad]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fc8501b1bd0): is an invalid pointer
Connection ID (thread ID): 2000035
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.
2019-04-19T09:02:44.012862+08:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-04-19T09:02:44.015795+08:00 0 [Warning] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2019-04-19T09:02:44.015838+08:00 0 [Note] /usr/local/mysql57/bin/mysqld (mysqld 5.7.23-log) starting as process 24557 ...
2019-04-19T09:02:44.053209+08:00 0 [ERROR] Error message file '/usr/local/mysql/share/english/errmsg.sys' had only 879 error messages,
but it should contain at least 1115 error messages.
Check that the above file is the right version for this program!
2019-04-19T09:02:44.247200+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2019-04-19T09:02:44.247304+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-04-19T09:02:44.247331+08:00 0 [Note] InnoDB: Uses event mutexes
2019-04-19T09:02:44.247350+08:00 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2019-04-19T09:02:44.247367+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-04-19T09:02:44.247384+08:00 0 [Note] InnoDB: Using Linux native AIO
2019-04-19T09:02:44.248586+08:00 0 [Note] InnoDB: Number of pools: 1
2019-04-19T09:02:44.248837+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2019-04-19T09:02:44.267997+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 4, chunk size = 128M
2019-04-19T09:02:44.525928+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2019-04-19T09:02:44.555680+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. 2019-04-19T08:53:26.114475+08:00 1979347 [Warning]
2019-04-19T08:53:26.114726+08:00 1979347 [Warning]
2019-04-19T08:53:26.115244+08:00 1979347 [Warning]
it seems that show create statement result in mysql server crash
How to repeat:
I can't repeate this situation
