Oct 27 22:05:01 db4 mysqld: 161027 22:05:01 [ERROR] mysqld got signal 11 ;
Oct 27 22:05:01 db4 mysqld: This could be because you hit a bug. It is also possible that this binary
Oct 27 22:05:01 db4 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Oct 27 22:05:01 db4 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 27 22:05:01 db4 mysqld:
Oct 27 22:05:01 db4 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Oct 27 22:05:01 db4 mysqld:
Oct 27 22:05:01 db4 mysqld: We will try our best to scrape up some info that will hopefully help
Oct 27 22:05:01 db4 mysqld: diagnose the problem, but since we have already crashed,
Oct 27 22:05:01 db4 mysqld: something is definitely wrong and this may fail.
Oct 27 22:05:01 db4 mysqld:
Oct 27 22:05:01 db4 mysqld: Server version: 10.1.18-MariaDB-1~trusty
Oct 27 22:05:01 db4 mysqld: key_buffer_size=134217728
Oct 27 22:05:01 db4 mysqld: read_buffer_size=2097152
Oct 27 22:05:01 db4 mysqld: max_used_connections=32
Oct 27 22:05:01 db4 mysqld: max_threads=102
Oct 27 22:05:01 db4 mysqld: thread_count=8
Oct 27 22:05:01 db4 mysqld: It is possible that mysqld could use up to
Oct 27 22:05:01 db4 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759834 K  bytes of memory
Oct 27 22:05:01 db4 mysqld: Hope that's ok; if not, decrease some variables in the equation.
Oct 27 22:05:01 db4 mysqld:
Oct 27 22:05:01 db4 mysqld: Thread pointer: 0x0x7f367a9c2008
Oct 27 22:05:01 db4 mysqld: Attempting backtrace. You can use the following information to find out
Oct 27 22:05:01 db4 mysqld: where mysqld died. If you see no messages after this, something went
Oct 27 22:05:01 db4 mysqld: terribly wrong...
Oct 27 22:05:01 db4 mysqld: stack_bottom = 0x7f370d45e1f0 thread_stack 0x48400
Oct 27 22:05:02 db4 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f37106d13de]
Oct 27 22:05:02 db4 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x2d5)[0x7f37101f7475]
Oct 27 22:05:02 db4 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f370e749330]
Oct 27 22:05:02 db4 mysqld:
Oct 27 22:05:02 db4 mysqld: Trying to get some variables.
Oct 27 22:05:02 db4 mysqld: Some pointers may be invalid and cause the dump to abort.
Oct 27 22:05:02 db4 mysqld: Query (0x7f36f5b09020): is an invalid pointer
Oct 27 22:05:02 db4 mysqld: Connection ID (thread ID): 288243
Oct 27 22:05:02 db4 mysqld: Status: NOT_KILLED
Oct 27 22:05:02 db4 mysqld:
Oct 27 22:05:02 db4 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
Oct 27 22:05:02 db4 mysqld:
Oct 27 22:05:02 db4 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Oct 27 22:05:02 db4 mysqld: information that should help you find out what is causing the crash.
Oct 27 22:05:02 db4 mysqld:
Oct 27 22:05:02 db4 mysqld: We think the query pointer is invalid, but we will try to print it anyway.
Oct 27 22:05:02 db4 mysqld: Query: SELECT /*!40001 SQL_NO_CACHE */ * FROM `COLUMNS`
Oct 27 22:05:02 db4 mysqld:
Oct 27 22:05:03 db4 mysqld_safe: Number of processes running now: 0
Oct 27 22:05:03 db4 mysqld_safe: mysqld restarted
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] /usr/sbin/mysqld (mysqld 10.1.18-MariaDB-1~trusty) starting as process 4586 ...
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Warning] You need to use --log-bin to make --binlog-format work.
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Using mutexes to ref count buffer pool pages
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: The InnoDB memory heap is disabled
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Compressed tables use zlib 1.2.8
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Using Linux native AIO
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Using SSE crc32 instructions
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Initializing buffer pool, size = 1.0G
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Completed initialization of buffer pool
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Highest supported file format is Barracuda.
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Log scan progressed past the checkpoint lsn 209007133552
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Database was not shutdown normally!
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Starting crash recovery.
Oct 27 22:05:04 db4 mysqld: 2016-10-27 22:05:04 140662774921152 [Note] InnoDB: Reading tablespace information from the .ibd files...
Oct 27 22:05:10 db4 mysqld: 2016-10-27 22:05:10 140662774921152 [Note] InnoDB: Restoring possible half-written data pages
Oct 27 22:05:10 db4 mysqld: 2016-10-27 22:05:10 140662774921152 [Note] InnoDB: from the doublewrite buffer...
Oct 27 22:05:10 db4 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 209007390221
Oct 27 22:05:11 db4 mysqld: InnoDB: 1 transaction(s) which must be rolled back or cleaned up
Oct 27 22:05:11 db4 mysqld: InnoDB: in total 11 row operations to undo
Oct 27 22:05:11 db4 mysqld: InnoDB: Trx id counter is 38513920
Oct 27 22:05:11 db4 mysqld: 2016-10-27 22:05:11 140662774921152 [Note] InnoDB: Starting an apply batch of log records to the database...
Oct 27 22:05:11 db4 mysqld: InnoDB: Progress in percent: 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
Oct 27 22:05:11 db4 mysqld: InnoDB: Apply batch completed
Oct 27 22:05:11 db4 mysqld: InnoDB: Last MySQL binlog file position 0 30872128, file name /var/log/mysql/mariadb-bin.000894
Oct 27 22:05:12 db4 mysqld: InnoDB: Starting in background the rollback of uncommitted transactions
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:11 7fee327ff700  InnoDB: Rolling back trx with id 38513413, 11 rows to undo
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] InnoDB: 128 rollback segment(s) are active.
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] InnoDB: Waiting for purge to start
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140661026191104 [Note] InnoDB: Rollback of trx with id 38513413 completed
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 7fee327ff700  InnoDB: Rollback of non-prepared transactions completed
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.32-78.1 started; log sequence number 209007390221
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140660933891840 [Note] InnoDB: Dumping buffer pool(s) not yet started
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Plugin 'FEEDBACK' is disabled.
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Recovering after a crash using tc.log
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Starting crash recovery...
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Crash recovery finished.
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Server socket created on IP: '::'.
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774373120 [Note] Event Scheduler: scheduler thread started with id 1
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Reading of all Master_info entries succeded
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] Added new Master_info '' to hash table
Oct 27 22:05:12 db4 mysqld: 2016-10-27 22:05:12 140662774921152 [Note] /usr/sbin/mysqld: ready for connections.
Oct 27 22:05:12 db4 mysqld: Version: '10.1.18-MariaDB-1~trusty'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution