Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 0 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 0 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index revision_id points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index revision_id points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index revision_id points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index PRIMARY points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index revision_id points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index revision_id points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Warning: Index revision_id points to table li7_cacentreforgermanstudies/entity_translation_revision and ib_table li7_cacentreforgermanstudies/entity_translation_revision statistics is initialized 1 but index table li7_cacentreforgermanstudies/entity_translation_revision initialized 1 mysql table is entity_translation_revision. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html Apr 27 22:15:27 wms-mdb10-1 mysqld: 2016-04-27 22:15:27 7f411751c700 InnoDB: Assertion failure in thread 139917540837120 in file ha_innodb.cc line 7813 Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: We intentionally generate a memory trap. Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: If you get repeated assertion failures or crashes, even Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: immediately after the mysqld startup, there may be Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: about forcing recovery. Apr 27 22:15:27 wms-mdb10-1 mysqld: 2016-04-27 22:15:27 7f411708a700 InnoDB: Assertion failure in thread 139917536044800 in file ha_innodb.cc line 7813 Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: We intentionally generate a memory trap. Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com. Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: If you get repeated assertion failures or crashes, even Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: immediately after the mysqld startup, there may be Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html Apr 27 22:15:27 wms-mdb10-1 mysqld: InnoDB: about forcing recovery. Apr 27 22:15:27 wms-mdb10-1 mysqld: 160427 22:15:27 [ERROR] mysqld got signal 6 ; Apr 27 22:15:27 wms-mdb10-1 mysqld: This could be because you hit a bug. It is also possible that this binary Apr 27 22:15:27 wms-mdb10-1 mysqld: or one of the libraries it was linked against is corrupt, improperly built, Apr 27 22:15:27 wms-mdb10-1 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Apr 27 22:15:27 wms-mdb10-1 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Apr 27 22:15:27 wms-mdb10-1 mysqld: We will try our best to scrape up some info that will hopefully help Apr 27 22:15:27 wms-mdb10-1 mysqld: diagnose the problem, but since we have already crashed, Apr 27 22:15:27 wms-mdb10-1 mysqld: something is definitely wrong and this may fail. Apr 27 22:15:27 wms-mdb10-1 mysqld: Server version: 10.1.10-MariaDB-log Apr 27 22:15:27 wms-mdb10-1 mysqld: key_buffer_size=134217728 Apr 27 22:15:27 wms-mdb10-1 mysqld: read_buffer_size=131072 Apr 27 22:15:27 wms-mdb10-1 mysqld: max_used_connections=200 Apr 27 22:15:27 wms-mdb10-1 mysqld: max_threads=153 Apr 27 22:15:27 wms-mdb10-1 mysqld: thread_count=33 Apr 27 22:15:27 wms-mdb10-1 mysqld: It is possible that mysqld could use up to Apr 27 22:15:27 wms-mdb10-1 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 470149 K bytes of memory Apr 27 22:15:27 wms-mdb10-1 mysqld: Hope that's ok; if not, decrease some variables in the equation. Apr 27 22:15:27 wms-mdb10-1 mysqld: Thread pointer: 0x0x7f4121ae3008 Apr 27 22:15:27 wms-mdb10-1 mysqld: Attempting backtrace. You can use the following information to find out Apr 27 22:15:27 wms-mdb10-1 mysqld: where mysqld died. If you see no messages after this, something went Apr 27 22:15:27 wms-mdb10-1 mysqld: terribly wrong... Apr 27 22:15:28 wms-mdb10-1 systemd: mariadb.service: main process exited, code=killed, status=6/ABRT Apr 27 22:15:28 wms-mdb10-1 systemd: Unit mariadb.service entered failed state.