Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 0  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Warning: Index type_revision points to table li7_cahumanresources/metatag and ib_table li7_cahumanresources/metatag statistics is initialized 1  but index table li7_cahumanresources/metatag initialized 1  mysql table is metatag. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: 2016-06-13 10:29:56 7f3d3587bb00  InnoDB: Assertion failure in thread 139900867820288 in file ha_innodb.cc line 8022
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: We intentionally generate a memory trap.
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: immediately after the mysqld startup, there may be
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Jun 13 10:29:56 wms-mdb10-1 mysqld: InnoDB: about forcing recovery.
Jun 13 10:29:56 wms-mdb10-1 mysqld: 160613 10:29:56 [ERROR] mysqld got signal 6 ;
Jun 13 10:29:56 wms-mdb10-1 mysqld: This could be because you hit a bug. It is also possible that this binary
Jun 13 10:29:56 wms-mdb10-1 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Jun 13 10:29:56 wms-mdb10-1 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Jun 13 10:29:56 wms-mdb10-1 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jun 13 10:29:56 wms-mdb10-1 mysqld: We will try our best to scrape up some info that will hopefully help
Jun 13 10:29:56 wms-mdb10-1 mysqld: diagnose the problem, but since we have already crashed,
Jun 13 10:29:56 wms-mdb10-1 mysqld: something is definitely wrong and this may fail.
Jun 13 10:29:56 wms-mdb10-1 mysqld: Server version: 10.1.14-MariaDB
Jun 13 10:29:56 wms-mdb10-1 mysqld: key_buffer_size=134217728
Jun 13 10:29:56 wms-mdb10-1 mysqld: read_buffer_size=131072
Jun 13 10:29:56 wms-mdb10-1 mysqld: max_used_connections=87
Jun 13 10:29:56 wms-mdb10-1 mysqld: max_threads=602
Jun 13 10:29:56 wms-mdb10-1 mysqld: thread_count=49
Jun 13 10:29:56 wms-mdb10-1 mysqld: It is possible that mysqld could use up to
Jun 13 10:29:56 wms-mdb10-1 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1453335 K  bytes of memory
Jun 13 10:29:56 wms-mdb10-1 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Jun 13 10:29:56 wms-mdb10-1 mysqld: Thread pointer: 0x0x7f3d06863008
Jun 13 10:29:56 wms-mdb10-1 mysqld: Attempting backtrace. You can use the following information to find out
Jun 13 10:29:56 wms-mdb10-1 mysqld: where mysqld died. If you see no messages after this, something went
Jun 13 10:29:56 wms-mdb10-1 mysqld: terribly wrong...
Jun 13 10:29:56 wms-mdb10-1 mysqld: stack_bottom = 0x7f3d3587b130 thread_stack 0x48400
Jun 13 10:29:56 wms-mdb10-1 mysqld: (my_addr_resolve failure: fork)
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e) [0x7f4ef46f61be]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x38d) [0x7f4ef4221f0d]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /lib64/libpthread.so.0(+0xf100) [0x7f4ef3840100]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /lib64/libc.so.6(gsignal+0x37) [0x7f4ef1b995f7]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /lib64/libc.so.6(abort+0x148) [0x7f4ef1b9ace8]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(+0x716350) [0x7f4ef4387350]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(+0x726300) [0x7f4ef4397300]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(+0x728009) [0x7f4ef4399009]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(QUICK_RANGE_SELECT::reset()+0x153) [0x7f4ef430b233]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(QUICK_RANGE_SELECT::init_ror_merged_scan(bool, st_mem_root*)+0x1f5) [0x7f4ef430aab5]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(QUICK_ROR_INTERSECT_SELECT::init_ror_merged_scan(bool, st_mem_root*)+0x7d) [0x7f4ef430abed]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(QUICK_ROR_INTERSECT_SELECT::reset()+0x5f) [0x7f4ef430b9ef]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(filesort(THD*, TABLE*, st_sort_field*, unsigned int, SQL_SELECT*, unsigned long long, bool, unsigned long long*, unsigned long long*, Filesort_tracker*)+0x15fe) [0x7f4ef42214de]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(+0x47eead) [0x7f4ef40efead]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(JOIN::exec_inner()+0xa57) [0x7f4ef40f7f97]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x54) [0x7f4ef40fa084]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x112) [0x7f4ef40f6732]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(handle_select(THD*, LEX*, select_result*, unsigned long)+0x245) [0x7f4ef40f7205]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(+0x428c91) [0x7f4ef4099c91]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x5f8f) [0x7f4ef40a589f]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, Parser_state*)+0x28e) [0x7f4ef40a917e]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x25db) [0x7f4ef40ac63b]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(do_command(THD*)+0x169) [0x7f4ef40aceb9]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(do_handle_one_connection(THD*)+0x18a) [0x7f4ef417062a]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /usr/sbin/mysqld(handle_one_connection+0x40) [0x7f4ef4170800]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /lib64/libpthread.so.0(+0x7dc5) [0x7f4ef3838dc5]
Jun 13 10:29:56 wms-mdb10-1 mysqld: /lib64/libc.so.6(clone+0x6d) [0x7f4ef1c5a28d]
Jun 13 10:29:56 wms-mdb10-1 mysqld: Trying to get some variables.
Jun 13 10:29:56 wms-mdb10-1 mysqld: Some pointers may be invalid and cause the dump to abort.
Jun 13 10:29:56 wms-mdb10-1 mysqld: Query (0x7f3d04806020): SELECT m.entity_id AS entity_id, m.revision_id AS revision_id, m.language AS language, m.data AS data FROM  metatag m WHERE  (m.entity_type = 'node') AND (m.revision_id IN  ('2972'))  ORDER BY entity_id ASC, revision_id ASC
Jun 13 10:29:56 wms-mdb10-1 mysqld: Connection ID (thread ID): 12666554
Jun 13 10:29:56 wms-mdb10-1 mysqld: Status: NOT_KILLED
Jun 13 10:29:56 wms-mdb10-1 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
Jun 13 10:29:56 wms-mdb10-1 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Jun 13 10:29:56 wms-mdb10-1 mysqld: information that should help you find out what is causing the crash.