Feb 20 06:49:09 server02 mysqld: InnoDB: Warning: Index PRIMARY points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 0  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:09 server02 mysqld: InnoDB: Warning: Index userid points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:09 server02 mysqld: InnoDB: Warning: Index userid points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:09 server02 mysqld: InnoDB: Warning: Index time points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:09 server02 mysqld: InnoDB: Warning: Index time points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: Looking for field 0 name session_id from table quadmoto3_centrum/bflyc_session
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: InnoDB Table quadmoto3_centrum/bflyc_session field 0 name session_id
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 0 name session_id
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 1 name client_id
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 2 name guest
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 3 name time
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 4 name data
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 5 name userid
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [Note] InnoDB: MySQL table bflyc_session field 6 name username
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [ERROR] InnoDB: Clustered record field for column 0 not found table n_user_defined 1 index n_user_defined 7 InnoDB table quadmoto3_centrum/bflyc_session field name session_id MySQL table bflyc_session field name session_id n_fields 7 query SELECT `data`
Feb 20 06:49:09 server02 mysqld: FROM `bflyc_session`
Feb 20 06:49:09 server02 mysqld: WHERE `session_id` = 'ca2d53780578f11d66eea4ccff0ac240'
Feb 20 06:49:09 server02 mysqld: 2017-02-20 06:49:09 7fa311aba700  InnoDB: Assertion failure in thread 140338352858880 in file ha_innodb.cc line 7372
Feb 20 06:49:09 server02 mysqld: InnoDB: Failing assertion: templ->clust_rec_field_no != ULINT_UNDEFINED
Feb 20 06:49:09 server02 mysqld: InnoDB: We intentionally generate a memory trap.
Feb 20 06:49:09 server02 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Feb 20 06:49:09 server02 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Feb 20 06:49:09 server02 mysqld: InnoDB: immediately after the mysqld startup, there may be
Feb 20 06:49:09 server02 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Feb 20 06:49:09 server02 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Feb 20 06:49:09 server02 mysqld: InnoDB: about forcing recovery.
Feb 20 06:49:09 server02 mysqld: 170220  6:49:09 [ERROR] mysqld got signal 6 ;
Feb 20 06:49:09 server02 mysqld: This could be because you hit a bug. It is also possible that this binary
Feb 20 06:49:09 server02 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Feb 20 06:49:09 server02 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb 20 06:49:09 server02 mysqld: 
Feb 20 06:49:09 server02 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Feb 20 06:49:09 server02 mysqld: 
Feb 20 06:49:09 server02 mysqld: We will try our best to scrape up some info that will hopefully help
Feb 20 06:49:09 server02 mysqld: diagnose the problem, but since we have already crashed,
Feb 20 06:49:09 server02 mysqld: something is definitely wrong and this may fail.
Feb 20 06:49:09 server02 mysqld: 
Feb 20 06:49:09 server02 mysqld: Server version: 10.0.29-MariaDB-0+deb8u1
Feb 20 06:49:09 server02 mysqld: key_buffer_size=2147483648
Feb 20 06:49:09 server02 mysqld: read_buffer_size=131072
Feb 20 06:49:09 server02 mysqld: max_used_connections=101
Feb 20 06:49:09 server02 mysqld: max_threads=102
Feb 20 06:49:09 server02 mysqld: thread_count=78
Feb 20 06:49:09 server02 mysqld: It is possible that mysqld could use up to
Feb 20 06:49:09 server02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2321105 K  bytes of memory
Feb 20 06:49:09 server02 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Feb 20 06:49:09 server02 mysqld: 
Feb 20 06:49:09 server02 mysqld: Thread pointer: 0x7fa388ab8008
Feb 20 06:49:09 server02 mysqld: Attempting backtrace. You can use the following information to find out
Feb 20 06:49:09 server02 mysqld: where mysqld died. If you see no messages after this, something went
Feb 20 06:49:09 server02 mysqld: terribly wrong...
Feb 20 06:49:10 server02 mysqld: stack_bottom = 0x7fa311ab9e88 thread_stack 0x40000
Feb 20 06:49:10 server02 mysqld: InnoDB: Warning: Index PRIMARY points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:10 server02 mysqld: InnoDB: Warning: Index userid points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:10 server02 mysqld: InnoDB: Warning: Index userid points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:10 server02 mysqld: InnoDB: Warning: Index time points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:10 server02 mysqld: InnoDB: Warning: Index time points to table quadmoto3_centrum/bflyc_session and ib_table quadmoto3_centrum/bflyc_session statistics is initialized 1  but index table quadmoto3_centrum/bflyc_session initialized 1  mysql table is bflyc_session. Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html
Feb 20 06:49:11 server02 mysqld: InnoDB: clust index for table `quadmoto3_centrum`.`bflyc_session` for index `PRIMARY` not found
Feb 20 06:49:11 server02 mysqld: 2017-02-20 06:49:11 7fa3012aa700  InnoDB: Assertion failure in thread 140338075969280 in file row0row.cc line 652
Feb 20 06:49:11 server02 mysqld: InnoDB: We intentionally generate a memory trap.
Feb 20 06:49:11 server02 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Feb 20 06:49:11 server02 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Feb 20 06:49:11 server02 mysqld: InnoDB: immediately after the mysqld startup, there may be
Feb 20 06:49:11 server02 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Feb 20 06:49:11 server02 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
Feb 20 06:49:11 server02 mysqld: InnoDB: about forcing recovery.
Feb 20 06:49:14 server02 mysqld_safe: Number of processes running now: 0
Feb 20 06:49:14 server02 mysqld_safe: mysqld restarted
Feb 20 06:49:16 server02 mysqld: 170220  6:49:16 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
Feb 20 06:49:16 server02 mysqld: 170220  6:49:16 [Note] /usr/sbin/mysqld (mysqld 10.0.29-MariaDB-0+deb8u1) starting as process 9947 ...
Feb 20 06:49:16 server02 mysqld: 170220  6:49:16 [Warning] An old style --language or -lc-message-dir value with language specific part detected: /usr/share/mysql/english/
Feb 20 06:49:16 server02 mysqld: 170220  6:49:16 [Warning] Use --lc-messages-dir without language specific part instead.
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: The InnoDB memory heap is disabled
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Compressed tables use zlib 1.2.8
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Using Linux native AIO
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Not using CPU crc32 instructions
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Initializing buffer pool, size = 128.0M
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Completed initialization of buffer pool
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Highest supported file format is Barracuda.
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2128712380914
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Database was not shutdown normally!
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Starting crash recovery.
Feb 20 06:49:18 server02 mysqld: 170220  6:49:18 [Note] InnoDB: Reading tablespace information from the .ibd files...
Feb 20 06:54:34 server02 mysqld: 170220  6:54:34 [Note] InnoDB: Restoring possible half-written data pages
Feb 20 06:54:34 server02 mysqld: 170220  6:54:34 [Note] InnoDB: from the doublewrite buffer...
Feb 20 06:54:34 server02 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 2128712391123
Feb 20 06:54:34 server02 mysqld: 170220  6:54:34 [Note] InnoDB: Starting an apply batch of log records to the database...
Feb 20 06:54:35 server02 mysqld: 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
Feb 20 06:54:35 server02 mysqld: InnoDB: Apply batch completed
Feb 20 06:54:36 server02 mysqld: 170220  6:54:36 [Note] InnoDB: 128 rollback segment(s) are active.
Feb 20 06:54:36 server02 mysqld: 170220  6:54:36 [Note] InnoDB: Waiting for purge to start
Feb 20 06:54:36 server02 mysqld: 170220  6:54:36 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 2128712391123
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 [Note] Plugin 'FEEDBACK' is disabled.
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 server_audit: MariaDB Audit Plugin version 1.4.0 STARTED.
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 server_audit: Query cache is enabled with the TABLE events. Some table reads can be veiled.170220  6:54:37 [Note] Server socket created on IP: '::'.
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 [Warning] Checking table:   './mysql/event'
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 [Note] Event Scheduler: scheduler thread started with id 1
Feb 20 06:54:37 server02 mysqld: 170220  6:54:37 [Note] /usr/sbin/mysqld: ready for connections.
Feb 20 06:54:37 server02 mysqld: Version: '10.0.29-MariaDB-0+deb8u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)