Apr 26 16:38:40 CentOS-Test mysqld: 2018-04-26 16:38:40 140100827948800 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 16:39:17 CentOS-Test mysqld: 180426 16:39:17 [ERROR] mysqld got signal 11 ;
Apr 26 16:39:17 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 16:39:17 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 16:39:17 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 16:39:17 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 16:39:17 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 16:39:17 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 16:39:17 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 16:39:17 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 16:39:17 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 16:39:17 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 16:39:17 CentOS-Test mysqld: max_used_connections=3
Apr 26 16:39:17 CentOS-Test mysqld: max_threads=153
Apr 26 16:39:17 CentOS-Test mysqld: thread_count=10
Apr 26 16:39:17 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 16:39:17 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 16:39:17 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 16:39:18 CentOS-Test mysqld: Thread pointer: 0x7f6828000e48
Apr 26 16:39:18 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 16:39:18 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 16:39:18 CentOS-Test mysqld: terribly wrong...
Apr 26 16:39:18 CentOS-Test mysqld: stack_bottom = 0x7f6bc4151d70 thread_stack 0x49000
Apr 26 16:39:18 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c115f21cce]
Apr 26 16:39:18 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x55c1159ad605]
Apr 26 16:39:19 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7f6be1d1f5e0]
Apr 26 16:39:19 CentOS-Test mysqld: Trying to get some variables.
Apr 26 16:39:19 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 16:39:19 CentOS-Test mysqld: Query (0x7f682801f570): insert into `bugTest`.`suppliers` (`supplierName`, `supplierCaps`, `supplierSentToday`) values ('TFLI Ltd', '{\"Thursday\":100,\"Friday\":50}', '0')
Apr 26 16:39:19 CentOS-Test mysqld: Connection ID (thread ID): 1841
Apr 26 16:39:19 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 16:39:19 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 16:39:20 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 16:39:20 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 16:39:20 CentOS-Test kernel: mysqld[27368]: segfault at 0 ip           (null) sp 00007f6bc414f538 error 14 in mysqld[55c11533a000+111d000]
Apr 26 16:39:20 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 16:39:20 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 16:39:20 CentOS-Test systemd: mariadb.service failed.
Apr 26 16:39:25 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 16:39:25 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 16:39:31 CentOS-Test mysqld: 2018-04-26 16:39:31 140168701298816 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 27408 ...
Apr 26 16:39:31 CentOS-Test mysqld: 2018-04-26 16:39:31 140168701298816 [ERROR] Plugin 'CONNECT' already installed
Apr 26 16:39:31 CentOS-Test mysqld: 2018-04-26 16:39:31 140168701298816 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Uses event mutexes
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Using Linux native AIO
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Number of pools: 1
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Using generic crc32 instructions
Apr 26 16:39:32 CentOS-Test mysqld: 2018-04-26 16:39:32 140168701298816 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 16:39:37 CentOS-Test mysqld: 2018-04-26 16:39:37 140168701298816 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 16:39:38 CentOS-Test mysqld: 2018-04-26 16:39:38 140154352133888 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 16:39:38 CentOS-Test mysqld: 2018-04-26 16:39:38 140168701298816 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 16:39:38 CentOS-Test mysqld: 2018-04-26 16:39:38 140168701298816 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52060672528
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: Waiting for purge to start
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] InnoDB: 5.7.21 started; log sequence number 52060672537
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140154572367616 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Recovering after a crash using tc.log
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Starting crash recovery...
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Crash recovery finished.
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Warning] Checking table:   './mysql/event'
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140154572367616 [Note] InnoDB: Buffer pool(s) load completed at 180426 16:39:39
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168205428480 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Reading of all Master_info entries succeded
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] Added new Master_info '' to hash table
Apr 26 16:39:39 CentOS-Test mysqld: 2018-04-26 16:39:39 140168701298816 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 16:39:39 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 16:39:40 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 16:39:47 CentOS-Test systemd: Created slice User Slice of rmhumphries.
Apr 26 16:39:47 CentOS-Test systemd: Starting User Slice of rmhumphries.
Apr 26 16:39:47 CentOS-Test systemd-logind: New session 31 of user rmhumphries.
Apr 26 16:39:47 CentOS-Test systemd: Started Session 31 of user rmhumphries.
Apr 26 16:39:47 CentOS-Test systemd: Starting Session 31 of user rmhumphries.
Apr 26 16:40:29 CentOS-Test su: (to root) rmhumphries on pts/0
Apr 26 16:58:48 CentOS-Test mysqld: 2018-04-26 16:58:48 140168204822272 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:00:30 CentOS-Test mysqld: 180426 17:00:30 [ERROR] mysqld got signal 11 ;
Apr 26 17:00:30 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:00:30 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:00:30 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:00:31 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:00:31 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:00:31 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:00:31 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:00:31 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:00:31 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:00:31 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:00:31 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:00:31 CentOS-Test mysqld: max_threads=153
Apr 26 17:00:31 CentOS-Test mysqld: thread_count=9
Apr 26 17:00:31 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:00:31 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:00:31 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:00:31 CentOS-Test mysqld: Thread pointer: 0x7f77d4000e48
Apr 26 17:00:31 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:00:31 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:00:31 CentOS-Test mysqld: terribly wrong...
Apr 26 17:00:31 CentOS-Test mysqld: stack_bottom = 0x7f7b740e9d70 thread_stack 0x49000
Apr 26 17:00:31 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55bf10adacce]
Apr 26 17:00:31 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x55bf10566605]
Apr 26 17:00:31 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7f7b916765e0]
Apr 26 17:00:32 CentOS-Test mysqld: /usr/sbin/mysqld(_Z14join_read_key2P3THDP13st_join_tableP5TABLEP12st_table_ref+0x21)[0x55bf10415e71]
Apr 26 17:00:32 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN25Expression_cache_tmptable11check_valueEPP4Item+0x2e)[0x55bf104dd89e]
Apr 26 17:00:32 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x55bf10393eb7]
Apr 26 17:00:33 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x55bf10393eb7]
Apr 26 17:00:33 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x55bf10393eb7]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_select.cc:19321(join_read_key2(THD*, st_join_table*, TABLE*, st_table_ref*))[0x55bf1047e658]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_expression_cache.cc:220(Expression_cache_tmptable::check_value(Item**))[0x55bf103910b0]
Apr 26 17:00:33 CentOS-Test mysqld: /usr/sbin/mysqld(_Z10setup_wildP3THDP10TABLE_LISTR4ListI4ItemEPS5_j+0x212)[0x55bf103916b2]
Apr 26 17:00:33 CentOS-Test mysqld: sql/item.h:3907(Item_args::walk_args(bool (Item::*)(void*), bool, void*))[0x55bf10419979]
Apr 26 17:00:33 CentOS-Test mysqld: sql/item.h:3907(Item_args::walk_args(bool (Item::*)(void*), bool, void*))[0x55bf10429e7c]
Apr 26 17:00:33 CentOS-Test mysqld: sql/table.cc:6576(TABLE::mark_virtual_col(Field*))[0x55bf1042a1e4]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_base.cc:7577(insert_fields(THD*, Name_resolution_context*, char const*, char const*, List_iterator<Item>*, bool))[0x55bf1030bbd9]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_select.cc:802(JOIN::prepare(TABLE_LIST*, unsigned int, Item*, unsigned int, st_order*, bool, st_order*, Item*, st_order*, st_select_lex*, st_select_lex_unit*))[0x55bf103d61ce]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_parse.cc:6469(execute_sqlcom_select(THD*, TABLE_LIST*))[0x55bf103d8b2e]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_parse.cc:3479(mysql_execute_command(THD*))[0x55bf103dbb33]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_parse.cc:1815(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x55bf103dc76b]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_parse.cc:1371(do_command(THD*))[0x55bf104a3d3a]
Apr 26 17:00:33 CentOS-Test mysqld: sql/sql_connect.cc:1335(do_handle_one_connection(CONNECT*))[0x55bf104a3e5d]
Apr 26 17:00:34 CentOS-Test mysqld: /lib64/libpthread.so.0(+0x7e25)[0x7f7b9166ee25]
Apr 26 17:00:34 CentOS-Test mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f7b8fc4634d]
Apr 26 17:00:34 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:00:34 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:00:34 CentOS-Test mysqld: Query (0x7f77d4013270): select * from `bugTest`.`suppliers2` limit 0, 1000
Apr 26 17:00:34 CentOS-Test mysqld: Connection ID (thread ID): 28
Apr 26 17:00:34 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:00:34 CentOS-Test kernel: traps: mysqld[27753] general protection ip:55bf10415e71 sp:7f7b740e6df0 error:0 in mysqld[55bf0fef3000+111d000]
Apr 26 17:00:34 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:00:34 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:00:34 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:00:35 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:00:35 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:00:35 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:00:40 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:00:40 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:00:45 CentOS-Test mysqld: 2018-04-26 17:00:45 139725701994624 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 27812 ...
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:45 139725701994624 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Uses event mutexes
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Using Linux native AIO
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Number of pools: 1
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:00:46 CentOS-Test mysqld: 2018-04-26 17:00:46 139725701994624 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:00:51 CentOS-Test mysqld: 2018-04-26 17:00:51 139725701994624 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:00:52 CentOS-Test mysqld: 2018-04-26 17:00:52 139711349737216 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:00:52 CentOS-Test mysqld: 2018-04-26 17:00:52 139725701994624 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:00:52 CentOS-Test mysqld: 2018-04-26 17:00:52 139725701994624 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52060740013
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: Waiting for purge to start
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] InnoDB: 5.7.21 started; log sequence number 52060740022
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139711586756352 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Recovering after a crash using tc.log
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Starting crash recovery...
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Crash recovery finished.
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Warning] Checking table:   './mysql/event'
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725554108160 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139711586756352 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:00:53
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Reading of all Master_info entries succeded
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] Added new Master_info '' to hash table
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725701994624 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:00:53 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:00:53 CentOS-Test mysqld: 2018-04-26 17:00:53 139725222475520 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:00:54 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:01:02 CentOS-Test systemd: Created slice User Slice of root.
Apr 26 17:01:02 CentOS-Test systemd: Starting User Slice of root.
Apr 26 17:01:02 CentOS-Test systemd: Started Session 32 of user root.
Apr 26 17:01:02 CentOS-Test systemd: Starting Session 32 of user root.
Apr 26 17:01:05 CentOS-Test systemd: Removed slice User Slice of root.
Apr 26 17:01:05 CentOS-Test systemd: Stopping User Slice of root.
Apr 26 17:07:18 CentOS-Test mysqld: 180426 17:07:18 [ERROR] mysqld got signal 11 ;
Apr 26 17:07:18 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:07:18 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:07:18 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:07:18 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:07:18 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:07:18 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:07:18 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:07:18 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:07:18 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:07:18 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:07:18 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:07:18 CentOS-Test mysqld: max_threads=153
Apr 26 17:07:18 CentOS-Test mysqld: thread_count=9
Apr 26 17:07:18 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:07:18 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:07:18 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:07:18 CentOS-Test mysqld: Thread pointer: 0x7f10c00009a8
Apr 26 17:07:18 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:07:18 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:07:18 CentOS-Test mysqld: terribly wrong...
Apr 26 17:07:18 CentOS-Test mysqld: stack_bottom = 0x7f1450406d70 thread_stack 0x49000
Apr 26 17:07:18 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56258202dcce]
Apr 26 17:07:18 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x562581ab9605]
Apr 26 17:07:19 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7f146c9675e0]
Apr 26 17:07:19 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:07:19 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:07:19 CentOS-Test kernel: mysqld[27849]: segfault at 0 ip           (null) sp 00007f1450404538 error 14 in mysqld[562581446000+111d000]
Apr 26 17:07:19 CentOS-Test mysqld: Query (0x7f10c0010350): insert into `bugTest`.`suppliers2` (`supplierName`, `supplierCaps`, `supplierSentToday`) values ('TFLI Ltd', '{\"Thursday\":100}', '0')
Apr 26 17:07:19 CentOS-Test mysqld: Connection ID (thread ID): 9
Apr 26 17:07:19 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:07:19 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:07:19 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:07:19 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:07:19 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:07:19 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:07:19 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:07:24 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:07:24 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 27980 ...
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Uses event mutexes
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Using Linux native AIO
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Number of pools: 1
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:07:29 CentOS-Test mysqld: 2018-04-26 17:07:29 139928621164672 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:07:36 CentOS-Test mysqld: 2018-04-26 17:07:36 139928621164672 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:07:37 CentOS-Test mysqld: 2018-04-26 17:07:37 139914269832960 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:07:37 CentOS-Test mysqld: 2018-04-26 17:07:37 139928621164672 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:07:37 CentOS-Test mysqld: 2018-04-26 17:07:37 139928621164672 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52060976312
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: Waiting for purge to start
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] InnoDB: 5.7.21 started; log sequence number 52060976321
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139914498782976 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Recovering after a crash using tc.log
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Starting crash recovery...
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Crash recovery finished.
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Warning] Checking table:   './mysql/event'
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928492193536 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Reading of all Master_info entries succeded
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] Added new Master_info '' to hash table
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139914498782976 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:07:38
Apr 26 17:07:38 CentOS-Test mysqld: 2018-04-26 17:07:38 139928621164672 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:07:38 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:07:39 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:10:55 CentOS-Test mysqld: 2018-04-26 17:10:55 139928491587328 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:11:39 CentOS-Test mysqld: 180426 17:11:39 [ERROR] mysqld got signal 11 ;
Apr 26 17:11:40 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:11:40 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:11:40 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:11:40 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:11:40 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:11:40 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:11:40 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:11:40 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:11:40 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:11:40 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:11:40 CentOS-Test mysqld: max_used_connections=1
Apr 26 17:11:40 CentOS-Test mysqld: max_threads=153
Apr 26 17:11:40 CentOS-Test mysqld: thread_count=8
Apr 26 17:11:40 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:11:40 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:11:40 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:11:40 CentOS-Test mysqld: Thread pointer: 0x7f4004000e48
Apr 26 17:11:40 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:11:40 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:11:40 CentOS-Test mysqld: terribly wrong...
Apr 26 17:11:40 CentOS-Test mysqld: stack_bottom = 0x7f43a408ed70 thread_stack 0x49000
Apr 26 17:11:40 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x556e138d7cce]
Apr 26 17:11:40 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x556e13363605]
Apr 26 17:11:41 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7f43ab8345e0]
Apr 26 17:11:41 CentOS-Test mysqld: /usr/sbin/mysqld(_Z14join_read_key2P3THDP13st_join_tableP5TABLEP12st_table_ref+0x21)[0x556e13212e71]
Apr 26 17:11:41 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN25Expression_cache_tmptable11check_valueEPP4Item+0x2e)[0x556e132da89e]
Apr 26 17:11:41 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x556e13190eb7]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x556e13190eb7]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x556e13190eb7]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN5TABLE16mark_virtual_colEP5Field+0x48)[0x556e1327b658]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_Z13insert_fieldsP3THDP23Name_resolution_contextPKcS4_P13List_iteratorI4ItemEb+0x320)[0x556e1318e0b0]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_Z10setup_wildP3THDP10TABLE_LISTR4ListI4ItemEPS5_j+0x212)[0x556e1318e6b2]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN4JOIN7prepareEP10TABLE_LISTjP4ItemjP8st_orderbS5_S3_S5_P13st_select_lexP18st_select_lex_unit+0x2b9)[0x556e13216979]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x90c)[0x556e13226e7c]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x254)[0x556e132271e4]
Apr 26 17:11:42 CentOS-Test mysqld: /usr/sbin/mysqld(+0x418bd9)[0x556e13108bd9]
Apr 26 17:11:43 CentOS-Test mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x688e)[0x556e131d31ce]
Apr 26 17:11:43 CentOS-Test mysqld: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x2de)[0x556e131d5b2e]
Apr 26 17:11:43 CentOS-Test mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x20e3)[0x556e131d8b33]
Apr 26 17:11:43 CentOS-Test mysqld: sql/sql_select.cc:19321(join_read_key2(THD*, st_join_table*, TABLE*, st_table_ref*))[0x556e131d976b]
Apr 26 17:11:43 CentOS-Test mysqld: sql/sql_expression_cache.cc:220(Expression_cache_tmptable::check_value(Item**))[0x556e132a0d3a]
Apr 26 17:11:43 CentOS-Test mysqld: /usr/sbin/mysqld(handle_one_connection+0x3d)[0x556e132a0e5d]
Apr 26 17:11:44 CentOS-Test mysqld: /lib64/libpthread.so.0(+0x7e25)[0x7f43ab82ce25]
Apr 26 17:11:44 CentOS-Test mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f43a9e0434d]
Apr 26 17:11:44 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:11:44 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:11:44 CentOS-Test kernel: traps: mysqld[28074] general protection ip:556e13212e71 sp:7f43a408bdf0 error:0 in mysqld[556e12cf0000+111d000]
Apr 26 17:11:44 CentOS-Test mysqld: Query (0x7f40040123d0): select * from `bugTest`.`suppliers2` limit 0, 1000
Apr 26 17:11:44 CentOS-Test mysqld: Connection ID (thread ID): 12
Apr 26 17:11:44 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:11:44 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:11:44 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:11:44 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:11:45 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:11:45 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:11:45 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:11:50 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:11:50 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:11:55 CentOS-Test mysqld: 2018-04-26 17:11:55 140617914226816 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28115 ...
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Uses event mutexes
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Using Linux native AIO
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Number of pools: 1
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:11:56 CentOS-Test mysqld: 2018-04-26 17:11:56 140617914226816 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:12:02 CentOS-Test mysqld: 2018-04-26 17:12:01 140617914226816 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:12:02 CentOS-Test mysqld: 2018-04-26 17:12:02 140603562084096 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:12:02 CentOS-Test mysqld: 2018-04-26 17:12:02 140617914226816 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:12:02 CentOS-Test mysqld: 2018-04-26 17:12:02 140617914226816 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52060977340
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: Waiting for purge to start
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] InnoDB: 5.7.21 started; log sequence number 52060977349
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140603799103232 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Recovering after a crash using tc.log
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Starting crash recovery...
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Crash recovery finished.
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Warning] Checking table:   './mysql/event'
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140603799103232 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:12:03
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617435125504 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Reading of all Master_info entries succeded
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] Added new Master_info '' to hash table
Apr 26 17:12:03 CentOS-Test mysqld: 2018-04-26 17:12:03 140617914226816 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:12:03 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:12:04 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:12:46 CentOS-Test mysqld: 2018-04-26 17:12:46 140617434519296 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:16:26 CentOS-Test mysqld: 180426 17:16:26 [ERROR] mysqld got signal 11 ;
Apr 26 17:16:26 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:16:26 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:16:26 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:16:26 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:16:26 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:16:26 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:16:26 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:16:26 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:16:26 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:16:26 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:16:26 CentOS-Test mysqld: max_used_connections=4
Apr 26 17:16:26 CentOS-Test mysqld: max_threads=153
Apr 26 17:16:26 CentOS-Test mysqld: thread_count=11
Apr 26 17:16:26 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:16:26 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:16:26 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:16:26 CentOS-Test mysqld: Thread pointer: 0x7fe0640009a8
Apr 26 17:16:26 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:16:26 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:16:26 CentOS-Test mysqld: terribly wrong...
Apr 26 17:16:26 CentOS-Test mysqld: stack_bottom = 0x7fe40c0d8d70 thread_stack 0x49000
Apr 26 17:16:26 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x561011100cce]
Apr 26 17:16:26 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x561010b8c605]
Apr 26 17:16:27 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7fe42894b5e0]
Apr 26 17:16:27 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:16:27 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:16:27 CentOS-Test kernel: mysqld[28200]: segfault at 0 ip           (null) sp 00007fe40c0d2948 error 14 in mysqld[561010519000+111d000]
Apr 26 17:16:27 CentOS-Test mysqld: Query (0x7fe06400f040): show full fields from `bugTest`.`jsonDateCrash`
Apr 26 17:16:27 CentOS-Test mysqld: Connection ID (thread ID): 15
Apr 26 17:16:27 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:16:27 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:16:27 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:16:27 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:16:27 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:16:27 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:16:27 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:16:32 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:16:32 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28240 ...
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Uses event mutexes
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Using Linux native AIO
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Number of pools: 1
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:16:37 CentOS-Test mysqld: 2018-04-26 17:16:37 140348407670912 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:16:44 CentOS-Test mysqld: 2018-04-26 17:16:44 140348407670912 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:16:44 CentOS-Test mysqld: 2018-04-26 17:16:44 140334052886272 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:16:44 CentOS-Test mysqld: 2018-04-26 17:16:44 140348407670912 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:16:44 CentOS-Test mysqld: 2018-04-26 17:16:44 140348407670912 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52061036623
Apr 26 17:16:45 CentOS-Test mysqld: 2018-04-26 17:16:45 140348407670912 [Note] InnoDB: Starting final batch to recover 13 pages from redo log.
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: Waiting for purge to start
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] InnoDB: 5.7.21 started; log sequence number 52061041353
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140334289905408 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Recovering after a crash using tc.log
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Starting crash recovery...
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Crash recovery finished.
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Warning] Checking table:   './mysql/event'
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348259784448 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140334289905408 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:16:46
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Reading of all Master_info entries succeded
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] Added new Master_info '' to hash table
Apr 26 17:16:46 CentOS-Test mysqld: 2018-04-26 17:16:46 140348407670912 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:16:46 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:16:47 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:17:57 CentOS-Test mysqld: 2018-04-26 17:17:57 140348259178240 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:18:00 CentOS-Test mysqld: 180426 17:18:00 [ERROR] mysqld got signal 11 ;
Apr 26 17:18:00 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:18:00 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:18:00 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:18:00 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:18:00 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:18:01 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:18:01 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:18:01 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:18:01 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:18:01 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:18:01 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:18:01 CentOS-Test mysqld: max_threads=153
Apr 26 17:18:01 CentOS-Test mysqld: thread_count=9
Apr 26 17:18:01 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:18:01 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:18:01 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:18:01 CentOS-Test mysqld: Thread pointer: 0x7fa1ac000e98
Apr 26 17:18:01 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:18:01 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:18:01 CentOS-Test mysqld: terribly wrong...
Apr 26 17:18:01 CentOS-Test mysqld: stack_bottom = 0x7fa5601c5d70 thread_stack 0x49000
Apr 26 17:18:01 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x558295c82cce]
Apr 26 17:18:01 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x55829570e605]
Apr 26 17:18:02 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7fa568bd05e0]
Apr 26 17:18:02 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:18:02 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:18:02 CentOS-Test kernel: mysqld[28308]: segfault at 0 ip           (null) sp 00007fa5601c21c8 error 14 in mysqld[55829509b000+111d000]
Apr 26 17:18:02 CentOS-Test mysqld: Query (0x7fa1ac014de0): show create table `bugTest`.`jsonDateCrash`
Apr 26 17:18:02 CentOS-Test mysqld: Connection ID (thread ID): 12
Apr 26 17:18:02 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:18:02 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:18:02 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:18:02 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:18:02 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:18:02 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:18:02 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:18:08 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:18:08 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28335 ...
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Uses event mutexes
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Using Linux native AIO
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Number of pools: 1
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:18:14 CentOS-Test mysqld: 2018-04-26 17:18:14 140171454453888 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:18:20 CentOS-Test mysqld: 2018-04-26 17:18:20 140171454453888 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:18:21 CentOS-Test mysqld: 2018-04-26 17:18:21 140157103597312 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:18:21 CentOS-Test mysqld: 2018-04-26 17:18:21 140171454453888 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:18:21 CentOS-Test mysqld: 2018-04-26 17:18:21 140171454453888 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52061101320
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: Waiting for purge to start
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] InnoDB: 5.7.21 started; log sequence number 52061101465
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140157323831040 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Recovering after a crash using tc.log
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Starting crash recovery...
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Crash recovery finished.
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Warning] Checking table:   './mysql/event'
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140170958726912 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Reading of all Master_info entries succeded
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] Added new Master_info '' to hash table
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140171454453888 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:18:22 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:18:22 CentOS-Test mysqld: 2018-04-26 17:18:22 140157323831040 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:18:22
Apr 26 17:18:23 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:19:42 CentOS-Test mysqld: 2018-04-26 17:19:42 140170958120704 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:19:44 CentOS-Test mysqld: 180426 17:19:44 [ERROR] mysqld got signal 11 ;
Apr 26 17:19:44 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:19:44 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:19:44 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:19:44 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:19:44 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:19:44 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:19:44 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:19:44 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:19:44 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:19:44 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:19:45 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:19:45 CentOS-Test mysqld: max_threads=153
Apr 26 17:19:45 CentOS-Test mysqld: thread_count=9
Apr 26 17:19:45 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:19:45 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:19:45 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:19:45 CentOS-Test mysqld: Thread pointer: 0x7f787c0009a8
Apr 26 17:19:45 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:19:45 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:19:45 CentOS-Test mysqld: terribly wrong...
Apr 26 17:19:45 CentOS-Test mysqld: stack_bottom = 0x7f7c18048d70 thread_stack 0x49000
Apr 26 17:19:45 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56147bf84cce]
Apr 26 17:19:45 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x56147ba10605]
Apr 26 17:19:46 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7f7c358135e0]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN9Item_func10print_argsEP6Stringj15enum_query_type+0x49)[0x56147ba7e029]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN9Item_func5printEP6String15enum_query_type+0x4d)[0x56147ba7e11d]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN9Item_func10print_argsEP6Stringj15enum_query_type+0x4f)[0x56147ba7e02f]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN9Item_func5printEP6String15enum_query_type+0x4d)[0x56147ba7e11d]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN9Item_func10print_argsEP6Stringj15enum_query_type+0x4f)[0x56147ba7e02f]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN9Item_func5printEP6String15enum_query_type+0x4d)[0x56147ba7e11d]
Apr 26 17:19:47 CentOS-Test mysqld: /usr/sbin/mysqld(_Z17show_create_tableP3THDP10TABLE_LISTP6StringP22Table_specification_st17enum_with_db_name+0x58b)[0x56147b8dbb4b]
Apr 26 17:19:48 CentOS-Test mysqld: /usr/sbin/mysqld(_Z29mysqld_show_create_get_fieldsP3THDP10TABLE_LISTP4ListI4ItemEP6String+0x51b)[0x56147b8dd74b]
Apr 26 17:19:48 CentOS-Test mysqld: /usr/sbin/mysqld(_Z18mysqld_show_createP3THDP10TABLE_LIST+0xc3)[0x56147b8dd913]
Apr 26 17:19:48 CentOS-Test mysqld: sql/item_func.cc:470(Item_func::print_args(String*, unsigned int, enum_query_type))[0x56147b87d42d]
Apr 26 17:19:48 CentOS-Test mysqld: sql/sql_string.h:485(String::append(char))[0x56147b882b2e]
Apr 26 17:19:48 CentOS-Test mysqld: sql/sql_show.cc:1986(show_create_table(THD*, TABLE_LIST*, String*, Table_specification_st*, enum_with_db_name))[0x56147b885b33]
Apr 26 17:19:48 CentOS-Test mysqld: sql/sql_parse.cc:4237(mysql_execute_command(THD*))[0x56147b88676b]
Apr 26 17:19:48 CentOS-Test mysqld: sql/sql_parse.cc:1815(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x56147b94dd3a]
Apr 26 17:19:48 CentOS-Test mysqld: sql/sql_parse.cc:1371(do_command(THD*))[0x56147b94de5d]
Apr 26 17:19:49 CentOS-Test mysqld: /lib64/libpthread.so.0(+0x7e25)[0x7f7c3580be25]
Apr 26 17:19:49 CentOS-Test mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f7c33de334d]
Apr 26 17:19:49 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:19:50 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:19:50 CentOS-Test kernel: mysqld[28388]: segfault at 1f8 ip 000056147ba7e029 sp 00007f7c180451d0 error 4 in mysqld[56147b39d000+111d000]
Apr 26 17:19:50 CentOS-Test mysqld: Query (0x7f787c00f040): show create table `bugTest`.`jsonDateCrash`
Apr 26 17:19:50 CentOS-Test mysqld: Connection ID (thread ID): 11
Apr 26 17:19:50 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:19:50 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:19:50 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:19:50 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:19:50 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:19:50 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:19:50 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:19:55 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:19:55 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28416 ...
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Uses event mutexes
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Using Linux native AIO
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Number of pools: 1
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:20:01 CentOS-Test mysqld: 2018-04-26 17:20:01 140550044248192 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:20:09 CentOS-Test mysqld: 2018-04-26 17:20:09 140550044248192 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:20:10 CentOS-Test mysqld: 2018-04-26 17:20:10 140535697913600 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:20:10 CentOS-Test mysqld: 2018-04-26 17:20:10 140550044248192 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:20:10 CentOS-Test mysqld: 2018-04-26 17:20:10 140550044248192 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52061161517
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: Waiting for purge to start
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] InnoDB: 5.7.21 started; log sequence number 52061161526
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140535926863616 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Recovering after a crash using tc.log
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Starting crash recovery...
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Crash recovery finished.
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [ERROR] mysqld: Table 'event' is marked as crashed and should be repaired
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Warning] Checking table:   './mysql/event'
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140549584606976 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Reading of all Master_info entries succeded
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] Added new Master_info '' to hash table
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140550044248192 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:20:11 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:20:11 CentOS-Test mysqld: 2018-04-26 17:20:11 140535926863616 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:20:11
Apr 26 17:20:12 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:20:12 CentOS-Test mysqld: 2018-04-26 17:20:12 140549584000768 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:20:49 CentOS-Test mysqld: 180426 17:20:49 [ERROR] mysqld got signal 11 ;
Apr 26 17:20:49 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:20:49 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:20:49 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:20:49 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:20:50 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:20:50 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:20:50 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:20:50 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:20:50 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:20:50 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:20:50 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:20:50 CentOS-Test mysqld: max_threads=153
Apr 26 17:20:50 CentOS-Test mysqld: thread_count=9
Apr 26 17:20:50 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:20:50 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:20:50 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:20:50 CentOS-Test mysqld: Thread pointer: 0x7fd0b80009a8
Apr 26 17:20:50 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:20:50 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:20:50 CentOS-Test mysqld: terribly wrong...
Apr 26 17:20:50 CentOS-Test mysqld: stack_bottom = 0x7fd440070d70 thread_stack 0x49000
Apr 26 17:20:50 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5636320f7cce]
Apr 26 17:20:50 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x563631b83605]
Apr 26 17:20:52 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7fd45b3705e0]
Apr 26 17:20:53 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x60)[0x5636319b0eb0]
Apr 26 17:20:53 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x5636319b0eb7]
Apr 26 17:20:53 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x5636319b0eb7]
Apr 26 17:20:53 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN5TABLE16mark_virtual_colEP5Field+0x48)[0x563631a9b658]
Apr 26 17:20:53 CentOS-Test mysqld: /usr/sbin/mysqld(_Z13insert_fieldsP3THDP23Name_resolution_contextPKcS4_P13List_iteratorI4ItemEb+0x320)[0x5636319ae0b0]
Apr 26 17:20:53 CentOS-Test mysqld: sql/item.h:3907(Item_args::walk_args(bool (Item::*)(void*), bool, void*))[0x5636319ae6b2]
Apr 26 17:20:53 CentOS-Test mysqld: sql/table.cc:6576(TABLE::mark_virtual_col(Field*))[0x563631a36979]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_base.cc:7577(insert_fields(THD*, Name_resolution_context*, char const*, char const*, List_iterator<Item>*, bool))[0x563631a46e7c]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_base.cc:6946(setup_wild(THD*, TABLE_LIST*, List<Item>&, List<Item>*, unsigned int))[0x563631a471e4]
Apr 26 17:20:53 CentOS-Test mysqld: /usr/sbin/mysqld(+0x418bd9)[0x563631928bd9]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_select.cc:802(JOIN::prepare(TABLE_LIST*, unsigned int, Item*, unsigned int, st_order*, bool, st_order*, Item*, st_order*, st_select_lex*, st_select_lex_unit*))[0x5636319f31ce]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_parse.cc:6469(execute_sqlcom_select(THD*, TABLE_LIST*))[0x5636319f5b2e]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_parse.cc:3479(mysql_execute_command(THD*))[0x5636319f8b33]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_parse.cc:1371(do_command(THD*))[0x5636319f976b]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_connect.cc:1335(do_handle_one_connection(CONNECT*))[0x563631ac0d3a]
Apr 26 17:20:53 CentOS-Test mysqld: sql/sql_connect.cc:1243(handle_one_connection)[0x563631ac0e5d]
Apr 26 17:20:54 CentOS-Test mysqld: /lib64/libpthread.so.0(+0x7e25)[0x7fd45b368e25]
Apr 26 17:20:55 CentOS-Test mysqld: /lib64/libc.so.6(clone+0x6d)[0x7fd45994034d]
Apr 26 17:20:55 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:20:55 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:20:55 CentOS-Test kernel: traps: mysqld[28467] general protection ip:5636319b0eb0 sp:7fd44006de60 error:0 in mysqld[563631510000+111d000]
Apr 26 17:20:55 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:20:55 CentOS-Test mysqld: Query (0x7fd0b8010350): select * from `bugTest`.`jsonDateCrash` limit 0, 1000
Apr 26 17:20:55 CentOS-Test mysqld: Connection ID (thread ID): 9
Apr 26 17:20:55 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:20:55 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:20:55 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:20:55 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:20:55 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:20:55 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:21:01 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:21:01 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:21:06 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28497 ...
Apr 26 17:21:06 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:21:06 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [Note] InnoDB: Uses event mutexes
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:06 139623432591488 [Note] InnoDB: Using Linux native AIO
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:07 139623432591488 [Note] InnoDB: Number of pools: 1
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:07 139623432591488 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:21:07 CentOS-Test mysqld: 2018-04-26 17:21:07 139623432591488 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:21:14 CentOS-Test mysqld: 2018-04-26 17:21:14 139623432591488 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:21:14 CentOS-Test mysqld: 2018-04-26 17:21:14 139609084221184 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:21:14 CentOS-Test mysqld: 2018-04-26 17:21:14 139623432591488 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:21:14 CentOS-Test mysqld: 2018-04-26 17:21:14 139623432591488 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52061221307
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: Waiting for purge to start
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] InnoDB: 5.7.21 started; log sequence number 52061221316
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139609321240320 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Recovering after a crash using tc.log
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Starting crash recovery...
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Crash recovery finished.
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623347914496 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139609321240320 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:21:15
Apr 26 17:21:15 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Reading of all Master_info entries succeded
Apr 26 17:21:16 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] Added new Master_info '' to hash table
Apr 26 17:21:16 CentOS-Test mysqld: 2018-04-26 17:21:15 139623432591488 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:21:16 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:21:16 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:21:21 CentOS-Test mysqld: 2018-04-26 17:21:21 139623347308288 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:21:59 CentOS-Test mysqld: 180426 17:21:59 [ERROR] mysqld got signal 11 ;
Apr 26 17:21:59 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:21:59 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:21:59 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:21:59 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:21:59 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:21:59 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:21:59 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:21:59 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:21:59 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:21:59 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:21:59 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:21:59 CentOS-Test mysqld: max_threads=153
Apr 26 17:21:59 CentOS-Test mysqld: thread_count=9
Apr 26 17:21:59 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:21:59 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:21:59 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:21:59 CentOS-Test mysqld: Thread pointer: 0x7ef8ec0009a8
Apr 26 17:21:59 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:21:59 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:21:59 CentOS-Test mysqld: terribly wrong...
Apr 26 17:21:59 CentOS-Test kernel: mysqld[28548]: segfault at 1 ip 00007efc99f66118 sp 00007efc98048100 error 4 in libgcc_s-4.8.5-20150702.so.1[7efc99f57000+15000]
Apr 26 17:21:59 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:21:59 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:21:59 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:22:04 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:22:04 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:22:11 CentOS-Test mysqld: 2018-04-26 17:22:11 140292065851520 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28577 ...
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Uses event mutexes
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Using Linux native AIO
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Number of pools: 1
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:22:12 CentOS-Test mysqld: 2018-04-26 17:22:12 140292065851520 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:22:19 CentOS-Test mysqld: 2018-04-26 17:22:19 140292065851520 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:22:19 CentOS-Test mysqld: 2018-04-26 17:22:19 140277718873856 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:22:19 CentOS-Test mysqld: 2018-04-26 17:22:19 140292065851520 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52061281115
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:22:20 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: Waiting for purge to start
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:20 140292065851520 [Note] InnoDB: 5.7.21 started; log sequence number 52061281124
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:20 140277951997696 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Recovering after a crash using tc.log
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Starting crash recovery...
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Crash recovery finished.
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140291618563840 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140277951997696 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:22:21
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Reading of all Master_info entries succeded
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] Added new Master_info '' to hash table
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140292065851520 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:22:21 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:22:21 CentOS-Test mysqld: 2018-04-26 17:22:21 140291617957632 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known
Apr 26 17:22:21 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:22:52 CentOS-Test mysqld: 180426 17:22:52 [ERROR] mysqld got signal 11 ;
Apr 26 17:22:52 CentOS-Test mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 26 17:22:52 CentOS-Test mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 26 17:22:52 CentOS-Test mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 26 17:22:52 CentOS-Test mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Apr 26 17:22:53 CentOS-Test mysqld: We will try our best to scrape up some info that will hopefully help
Apr 26 17:22:53 CentOS-Test mysqld: diagnose the problem, but since we have already crashed,
Apr 26 17:22:53 CentOS-Test mysqld: something is definitely wrong and this may fail.
Apr 26 17:22:53 CentOS-Test mysqld: Server version: 10.2.14-MariaDB
Apr 26 17:22:53 CentOS-Test mysqld: key_buffer_size=134217728
Apr 26 17:22:53 CentOS-Test mysqld: read_buffer_size=131072
Apr 26 17:22:53 CentOS-Test mysqld: max_used_connections=2
Apr 26 17:22:53 CentOS-Test mysqld: max_threads=153
Apr 26 17:22:53 CentOS-Test mysqld: thread_count=9
Apr 26 17:22:53 CentOS-Test mysqld: It is possible that mysqld could use up to
Apr 26 17:22:53 CentOS-Test mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467245 K  bytes of memory
Apr 26 17:22:53 CentOS-Test mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 26 17:22:53 CentOS-Test mysqld: Thread pointer: 0x7f94a80009a8
Apr 26 17:22:53 CentOS-Test mysqld: Attempting backtrace. You can use the following information to find out
Apr 26 17:22:53 CentOS-Test mysqld: where mysqld died. If you see no messages after this, something went
Apr 26 17:22:53 CentOS-Test mysqld: terribly wrong...
Apr 26 17:22:53 CentOS-Test mysqld: stack_bottom = 0x7f98300d9d70 thread_stack 0x49000
Apr 26 17:22:53 CentOS-Test mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x557f7516acce]
Apr 26 17:22:53 CentOS-Test mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x355)[0x557f74bf6605]
Apr 26 17:22:54 CentOS-Test mysqld: /lib64/libpthread.so.0(+0xf5e0)[0x7f984a8115e0]
Apr 26 17:22:55 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x60)[0x557f74a23eb0]
Apr 26 17:22:56 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x557f74a23eb7]
Apr 26 17:22:56 CentOS-Test mysqld: /usr/sbin/mysqld(_ZN16Item_func_or_sum4walkEM4ItemFbPvEbS1_+0x67)[0x557f74a23eb7]
Apr 26 17:22:56 CentOS-Test mysqld: /usr/sbin/mysqld(_Z21fix_session_vcol_exprP3THDP19Virtual_column_info+0x3c)[0x557f74b053ec]
Apr 26 17:22:56 CentOS-Test mysqld: /usr/sbin/mysqld(_Z11lock_tablesP3THDP10TABLE_LISTjj+0x3ff)[0x557f74a1d08f]
Apr 26 17:22:56 CentOS-Test mysqld: /usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDRK14DDL_options_stP10TABLE_LISTbjP19Prelocking_strategy+0x8a)[0x557f74a1e49a]
Apr 26 17:22:56 CentOS-Test mysqld: /usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xfa)[0x557f74a4afca]
Apr 26 17:22:56 CentOS-Test mysqld: sql/item.h:3907(Item_args::walk_args(bool (Item::*)(void*), bool, void*))[0x557f74a61354]
Apr 26 17:22:56 CentOS-Test mysqld: sql/item.h:3907(Item_args::walk_args(bool (Item::*)(void*), bool, void*))[0x557f74a68b2e]
Apr 26 17:22:56 CentOS-Test mysqld: sql/table.cc:2773(fix_session_vcol_expr(THD*, Virtual_column_info*))[0x557f74a6bb33]
Apr 26 17:22:56 CentOS-Test mysqld: sql/sql_base.cc:4819(lock_tables(THD*, TABLE_LIST*, unsigned int, unsigned int))[0x557f74a6c76b]
Apr 26 17:22:56 CentOS-Test mysqld: sql/sql_insert.cc:753(mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool))[0x557f74b33d3a]
Apr 26 17:22:56 CentOS-Test mysqld: sql/sql_parse.cc:4430(mysql_execute_command(THD*))[0x557f74b33e5d]
Apr 26 17:22:57 CentOS-Test mysqld: /lib64/libpthread.so.0(+0x7e25)[0x7f984a809e25]
Apr 26 17:22:59 CentOS-Test mysqld: /lib64/libc.so.6(clone+0x6d)[0x7f9848de134d]
Apr 26 17:22:59 CentOS-Test mysqld: Trying to get some variables.
Apr 26 17:22:59 CentOS-Test mysqld: Some pointers may be invalid and cause the dump to abort.
Apr 26 17:22:59 CentOS-Test kernel: mysqld[28624]: segfault at 2d8 ip 0000557f74a23eb0 sp 00007f98300d7540 error 4 in mysqld[557f74583000+111d000]
Apr 26 17:22:59 CentOS-Test mysqld: Query (0x7f94a8010350): INSERT INTO `jsonDateCrash` (`supplierName`, `supplierCaps`, `supplierSentToday`) VALUES ('TFLI Ltd', '{\"Thursday\":100}', '0')
Apr 26 17:22:59 CentOS-Test mysqld: Connection ID (thread ID): 9
Apr 26 17:22:59 CentOS-Test mysqld: Status: NOT_KILLED
Apr 26 17:22:59 CentOS-Test mysqld: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
Apr 26 17:22:59 CentOS-Test mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 26 17:22:59 CentOS-Test mysqld: information that should help you find out what is causing the crash.
Apr 26 17:22:59 CentOS-Test systemd: mariadb.service: main process exited, code=killed, status=11/SEGV
Apr 26 17:22:59 CentOS-Test systemd: Unit mariadb.service entered failed state.
Apr 26 17:22:59 CentOS-Test systemd: mariadb.service failed.
Apr 26 17:23:04 CentOS-Test systemd: mariadb.service holdoff time over, scheduling restart.
Apr 26 17:23:04 CentOS-Test systemd: Starting MariaDB 10.2.14 database server...
Apr 26 17:23:10 CentOS-Test mysqld: 2018-04-26 17:23:10 140593188124800 [Note] /usr/sbin/mysqld (mysqld 10.2.14-MariaDB) starting as process 28653 ...
Apr 26 17:23:10 CentOS-Test mysqld: 2018-04-26 17:23:10 140593188124800 [ERROR] Plugin 'CONNECT' already installed
Apr 26 17:23:10 CentOS-Test mysqld: 2018-04-26 17:23:10 140593188124800 [Note] CONNECT: Version 1.06.0007 March 11, 2018
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Uses event mutexes
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Compressed tables use zlib 1.2.7
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Using Linux native AIO
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Number of pools: 1
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Using generic crc32 instructions
Apr 26 17:23:11 CentOS-Test mysqld: 2018-04-26 17:23:11 140593188124800 [Note] InnoDB: Initializing buffer pool, total size = 12G, instances = 8, chunk size = 128M
Apr 26 17:23:20 CentOS-Test mysqld: 2018-04-26 17:23:20 140593188124800 [Note] InnoDB: Completed initialization of buffer pool
Apr 26 17:23:20 CentOS-Test mysqld: 2018-04-26 17:23:20 140578840520448 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Apr 26 17:23:20 CentOS-Test mysqld: 2018-04-26 17:23:20 140593188124800 [Note] InnoDB: Highest supported file format is Barracuda.
Apr 26 17:23:20 CentOS-Test mysqld: 2018-04-26 17:23:20 140593188124800 [Note] InnoDB: Starting crash recovery from checkpoint LSN=52061340913
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: 128 out of 128 rollback segments are active.
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: Creating shared tablespace for temporary tables
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: Waiting for purge to start
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] InnoDB: 5.7.21 started; log sequence number 52061340922
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140579077863168 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Plugin 'FEEDBACK' is disabled.
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Recovering after a crash using tc.log
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Starting crash recovery...
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Crash recovery finished.
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Server socket created on IP: '0.0.0.0'.
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593071589120 [Note] Event Scheduler: scheduler thread started with id 6
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140579077863168 [Note] InnoDB: Buffer pool(s) load completed at 180426 17:23:21
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Reading of all Master_info entries succeded
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] Added new Master_info '' to hash table
Apr 26 17:23:21 CentOS-Test mysqld: 2018-04-26 17:23:21 140593188124800 [Note] /usr/sbin/mysqld: ready for connections.
Apr 26 17:23:22 CentOS-Test mysqld: Version: '10.2.14-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
Apr 26 17:23:22 CentOS-Test systemd: Started MariaDB 10.2.14 database server.
Apr 26 17:23:42 CentOS-Test mysqld: 2018-04-26 17:23:42 140593070982912 [Warning] IP address '10.0.10.17' could not be resolved: Name or service not known