Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_calibrary/scheduler and ib_table li7_calibrary/scheduler statistics is initialized 1 but index table li7_calibrary/scheduler initialized 0 mysql table is scheduler. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Warning: Index scheduler_publish_on points to table li7_calibrary/scheduler and ib_table li7_calibrary/scheduler statistics is initialized 1 but index table li7_calibrary/scheduler initialized 1 mysql table is scheduler. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Warning: Index scheduler_publish_on points to table li7_calibrary/scheduler and ib_table li7_calibrary/scheduler statistics is initialized 1 but index table li7_calibrary/scheduler initialized 1 mysql table is scheduler. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Warning: Index scheduler_unpublish_on points to table li7_calibrary/scheduler and ib_table li7_calibrary/scheduler statistics is initialized 1 but index table li7_calibrary/scheduler initialized 1 mysql table is scheduler. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Warning: Index scheduler_unpublish_on points to table li7_calibrary/scheduler and ib_table li7_calibrary/scheduler statistics is initialized 1 but index table li7_calibrary/scheduler initialized 1 mysql table is scheduler. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [Note] InnoDB: Looking for field 0 name nid from table li7_calibrary/scheduler Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [Note] InnoDB: InnoDB Table li7_calibrary/scheduler field 0 name nid Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [Note] InnoDB: MySQL table scheduler field 0 name nid Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [Note] InnoDB: MySQL table scheduler field 1 name publish_on Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [Note] InnoDB: MySQL table scheduler field 2 name unpublish_on Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [Note] InnoDB: MySQL table scheduler field 3 name uid Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 140025928473344 [ERROR] InnoDB: Clustered record field for column 0 not found table n_user_defined 1 index n_user_defined 4 InnoDB table li7_calibrary/scheduler field name nid MySQL table scheduler field name nid n_fields 4 query SELECT * FROM scheduler WHERE nid IN ('336') Jun 5 12:19:46 wms-mdb10-2 mysqld: 2017-06-05 12:19:46 7f5a53b9db00 InnoDB: Assertion failure in thread 140025928473344 in file ha_innodb.cc line 8359 Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: We intentionally generate a memory trap. Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: If you get repeated assertion failures or crashes, even Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: immediately after the mysqld startup, there may be Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html Jun 5 12:19:46 wms-mdb10-2 mysqld: InnoDB: about forcing recovery. Jun 5 12:19:46 wms-mdb10-2 mysqld: 170605 12:19:46 [ERROR] mysqld got signal 6 ; Jun 5 12:19:46 wms-mdb10-2 mysqld: This could be because you hit a bug. It is also possible that this binary Jun 5 12:19:46 wms-mdb10-2 mysqld: or one of the libraries it was linked against is corrupt, improperly built, Jun 5 12:19:46 wms-mdb10-2 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Jun 5 12:19:46 wms-mdb10-2 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs Jun 5 12:19:46 wms-mdb10-2 mysqld: We will try our best to scrape up some info that will hopefully help Jun 5 12:19:46 wms-mdb10-2 mysqld: diagnose the problem, but since we have already crashed, Jun 5 12:19:46 wms-mdb10-2 mysqld: something is definitely wrong and this may fail. Jun 5 12:19:46 wms-mdb10-2 mysqld: Server version: 10.1.20-MariaDB Jun 5 12:19:46 wms-mdb10-2 mysqld: key_buffer_size=134217728 Jun 5 12:19:46 wms-mdb10-2 mysqld: read_buffer_size=131072 Jun 5 12:19:46 wms-mdb10-2 mysqld: max_used_connections=69 Jun 5 12:19:46 wms-mdb10-2 mysqld: max_threads=602 Jun 5 12:19:46 wms-mdb10-2 mysqld: thread_count=60 Jun 5 12:19:46 wms-mdb10-2 mysqld: It is possible that mysqld could use up to Jun 5 12:19:46 wms-mdb10-2 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1453367 K bytes of memory Jun 5 12:19:46 wms-mdb10-2 mysqld: Hope that's ok; if not, decrease some variables in the equation. Jun 5 12:19:46 wms-mdb10-2 mysqld: Thread pointer: 0x0x7f5ae4047008 Jun 5 12:19:46 wms-mdb10-2 mysqld: Attempting backtrace. You can use the following information to find out Jun 5 12:19:46 wms-mdb10-2 mysqld: where mysqld died. If you see no messages after this, something went Jun 5 12:19:46 wms-mdb10-2 mysqld: terribly wrong... Jun 5 12:19:46 wms-mdb10-2 mysqld: stack_bottom = 0x7f5a53b9d0b0 thread_stack 0x48400 Jun 5 12:19:46 wms-mdb10-2 mysqld: (my_addr_resolve failure: fork) Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e) [0x7f7d8473a6fe] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x305) [0x7f7d8425cf75] Jun 5 12:19:46 wms-mdb10-2 mysqld: /lib64/libpthread.so.0(+0xf370) [0x7f7d83878370] Jun 5 12:19:46 wms-mdb10-2 mysqld: /lib64/libc.so.6(gsignal+0x37) [0x7f7d81bce1d7] Jun 5 12:19:46 wms-mdb10-2 mysqld: /lib64/libc.so.6(abort+0x148) [0x7f7d81bcf8c8] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x7381c5) [0x7f7d843df1c5] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x7386d0) [0x7f7d843df6d0] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x738d19) [0x7f7d843dfd19] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(handler::index_read_idx_map(unsigned char*, unsigned int, unsigned char const*, unsigned long, ha_rkey_function)+0x33) [0x7f7d8425d873] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(handler::ha_index_read_idx_map(unsigned char*, unsigned int, unsigned char const*, unsigned long, ha_rkey_function)+0x17c) [0x7f7d84261cdc] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x479c04) [0x7f7d84120c04] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x479d80) [0x7f7d84120d80] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x47f4b6) [0x7f7d841264b6] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(JOIN::optimize_inner()+0x72f) [0x7f7d8412e2ff] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(JOIN::optimize()+0x2f) [0x7f7d84130bff] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x8f) [0x7f7d84130d3f] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(handle_select(THD*, LEX*, select_result*, unsigned long)+0x245) [0x7f7d841318a5] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(+0x429881) [0x7f7d840d0881] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x5f8f) [0x7f7d840dcbaf] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, Parser_state*)+0x352) [0x7f7d840e0542] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x25db) [0x7f7d840e3a1b] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(do_command(THD*)+0x169) [0x7f7d840e4299] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(do_handle_one_connection(THD*)+0x18a) [0x7f7d841ab35a] Jun 5 12:19:46 wms-mdb10-2 mysqld: /usr/sbin/mysqld(handle_one_connection+0x40) [0x7f7d841ab530] Jun 5 12:19:46 wms-mdb10-2 mysqld: /lib64/libpthread.so.0(+0x7dc5) [0x7f7d83870dc5] Jun 5 12:19:46 wms-mdb10-2 mysqld: /lib64/libc.so.6(clone+0x6d) [0x7f7d81c9073d] Jun 5 12:19:46 wms-mdb10-2 mysqld: Trying to get some variables. Jun 5 12:19:46 wms-mdb10-2 mysqld: Some pointers may be invalid and cause the dump to abort. Jun 5 12:19:46 wms-mdb10-2 mysqld: Query (0x7f5ad84b7020): SELECT * FROM scheduler WHERE nid IN ('336') Jun 5 12:19:46 wms-mdb10-2 mysqld: Connection ID (thread ID): 45201 Jun 5 12:19:46 wms-mdb10-2 mysqld: Status: NOT_KILLED Jun 5 12:19:46 wms-mdb10-2 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=off Jun 5 12:19:46 wms-mdb10-2 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Jun 5 12:19:46 wms-mdb10-2 mysqld: information that should help you find out what is causing the crash. Jun 5 12:19:51 wms-mdb10-2 systemd[1]: mariadb.service: main process exited, code=killed, status=6/ABRT Jun 5 12:19:51 wms-mdb10-2 systemd[1]: Unit mariadb.service entered failed state. Jun 5 12:19:51 wms-mdb10-2 systemd[1]: mariadb.service failed. Jun 5 12:19:56 wms-mdb10-2 systemd[1]: mariadb.service holdoff time over, scheduling restart. Jun 5 12:19:56 wms-mdb10-2 systemd[1]: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument. Jun 5 12:19:56 wms-mdb10-2 systemd[1]: Starting MariaDB database server...