InnoDB: Warning: Index PRIMARY points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 0 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index AAAAA points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index AAAAA points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index XXXXX points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index XXXXX points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index BBBBB points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index BBBBB points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index CCCCC points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index CCCCC points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index EEEEE points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index EEEEE points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index FFFFF points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index FFFFF points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index GGGGG points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index GGGGG points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index YYYYY points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index YYYYY points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index HHHHH points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index HHHHH points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html 2016-06-19 08:42:57 7f959ea10700 InnoDB: Assertion failure in thread 140280588207872 in file ha_innodb.cc line 8022 InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 160619 8:42:57 [ERROR] mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.1.14-MariaDB-1~jessie key_buffer_size=16777216 read_buffer_size=131072 max_used_connections=173 max_threads=202 thread_count=41 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 460053 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7f95a121a008 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x7f959ea0fdf8 thread_stack 0x30000 (my_addr_resolve failure: fork) InnoDB: Warning: Index PRIMARY points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index AAAAA points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index AAAAA points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index XXXXX points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index XXXXX points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index BBBBB points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index BBBBB points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index CCCCC points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index CCCCC points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index DDDDD points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index EEEEE points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index EEEEE points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index FFFFF points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index FFFFF points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index GGGGG points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index GGGGG points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index HHHHH points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html InnoDB: Warning: Index HHHHH points to table DATABASE/TABLE_2016_05_23 and ib_table DATABASE/TABLE_2016_05_23 statistics is initialized 1 but index table DATABASE/TABLE_2016_05_23 initialized 1 mysql table is TABLE_2016_05_23. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html 2016-06-19 08:42:59 7fac0ab6b700 InnoDB: Assertion failure in thread 140376890849024 in file ha_innodb.cc line 8022 InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 2016-06-19 8:43:11 140336549058496 [Note] Using unique option prefix 'myisam-recover' is error-prone and can break in the future. Please use the full name 'myisam-recover-options' instead. 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: The InnoDB memory heap is disabled 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Memory barrier is not used 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Compressed tables use zlib 1.2.8 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Using Linux native AIO 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Using SSE crc32 instructions 2016-06-19 8:43:12 140336549058496 [Note] InnoDB: Initializing buffer pool, size = 80.0G 2016-06-19 8:43:15 140336549058496 [Note] InnoDB: Completed initialization of buffer pool 2016-06-19 8:43:16 140336549058496 [Note] InnoDB: Highest supported file format is Barracuda. 2016-06-19 8:43:16 140336549058496 [Note] InnoDB: Log scan progressed past the checkpoint lsn 9620603949851 2016-06-19 8:43:16 140336549058496 [Note] InnoDB: Database was not shutdown normally! 2016-06-19 8:43:16 140336549058496 [Note] InnoDB: Starting crash recovery. 2016-06-19 8:43:16 140336549058496 [Note] InnoDB: Reading tablespace information from the .ibd files... 2016-06-19 8:43:32 140336549058496 [Note] InnoDB: Processed 2321 .ibd/.isl files 2016-06-19 9:26:28 140336549058496 [Note] InnoDB: Processed 202202 .ibd/.isl files ... ... ... 2016-06-19 9:26:44 140336549058496 [Note] InnoDB: Processed 203665 .ibd/.isl files 2016-06-19 9:26:49 140336549058496 [Note] InnoDB: Restoring possible half-written data pages 2016-06-19 9:26:49 140336549058496 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 9620609192448 ... ... ... ... InnoDB: Doing recovery: scanned up to log sequence number 9620923765248 InnoDB: Doing recovery: scanned up to log sequence number 9620929008128 2016-06-19 9:27:55 140336549058496 [Note] InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 8714, file name /home/mysql/log/mysql-bin.054509 2016-06-19 9:28:38 140336549058496 [Note] InnoDB: 128 rollback segment(s) are active. 2016-06-19 9:28:38 140336549058496 [Note] InnoDB: Waiting for purge to start 2016-06-19 9:28:38 140336549058496 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.29-76.2 started; log sequence number 9626646641207 2016-06-19 9:29:49 140336549058496 [Note] Plugin 'FEEDBACK' is disabled. 2016-06-19 9:29:49 140241620932352 [Note] InnoDB: Dumping buffer pool(s) not yet started 2016-06-19 9:29:49 140336549058496 [Note] Recovering after a crash using /home/mysql/log/mysql-bin 2016-06-19 9:29:49 140336549058496 [Note] Starting crash recovery... 2016-06-19 9:29:49 140336549058496 [Note] Crash recovery finished. 2016-06-19 9:29:49 140336549058496 [Note] Server socket created on IP: '0.0.0.0'. 2016-06-19 9:29:49 140336548423424 [Note] /usr/sbin/mysqld: Normal shutdown 2016-06-19 9:29:49 140336549058496 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.1.14-MariaDB-1~jessie' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 2016-06-19 9:29:49 140336548423424 [Note] Event Scheduler: Purging the queue. 0 events 2016-06-19 9:29:49 140241604146944 [Note] InnoDB: FTS optimize thread exiting. 2016-06-19 9:29:49 140336548423424 [Note] InnoDB: Starting shutdown... 2016-06-19 9:29:56 140336548423424 [Note] InnoDB: Shutdown completed; log sequence number 9626646642806 2016-06-19 9:29:56 140336548423424 [Note] /usr/sbin/mysqld: Shutdown complete