10.1.9-MariaDB-log MariaDB Server crashed while changing Query cache

160805 13:08:06 [ERROR] mysqld got signal 11 ;

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 http://kb.askmonty.org/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.9-MariaDB-log

key_buffer_size=16777216

read_buffer_size=2097152

max_used_connections=231

max_threads=2511

thread_count=99

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 18066490 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7ee1d73d3008

Attempting backtrace. You can use the following information to find out

where mysqld died. If you see no messages after this, something went

....

.....

....

2016-08-05 13:09:33 140389545150336 [Note] InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progress in percent: 0 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 88325172, file name /logs/binarylogs/binary-log-174.004436

2016-08-05 13:09:56 140389545150336 [Note] InnoDB: 128 rollback segment(s) are active.

2016-08-05 13:09:56 140389545150336 [Note] InnoDB: Waiting for purge to start

2016-08-05 13:09:56 140389545150336 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 3717164310403

2016-08-05 13:10:13 140206342641408 [Note] InnoDB: Dumping buffer pool(s) not yet started

2016-08-05 13:10:13 140389545150336 [Note] Plugin 'FEEDBACK' is disabled.

160805 13:10:13 server_audit: MariaDB Audit Plugin version 1.3.0 STARTED.

160805 13:10:13 server_audit: logging started to the file /logs/auditlogs/server_audit.log.

2016-08-05 13:10:13 140389545150336 [Note] Recovering after a crash using /logs/binarylogs/binary-log-174

2016-08-05 13:10:13 140389545150336 [Note] Starting crash recovery...

2016-08-05 13:10:13 140389545150336 [Note] Crash recovery finished.

2016-08-05 13:10:13 140389545150336 [Note] Server socket created on IP: '::'.

2016-08-05 13:10:13 140389545150336 [Note] Server socket created on IP: '::'.

2016-08-05 13:10:13 140389545150336 [ERROR] mysqld: Table './mysql/user' is marked as crashed and should be repaired

2016-08-05 13:10:13 140389545150336 [Warning] Checking table:   './mysql/user'

2016-08-05 13:10:13 140389545150336 [ERROR] mysql.user: 1 client is using or hasn't closed the table properly

2016-08-05 13:10:13 140389545150336 [ERROR] mysqld: Table './mysql/tables_priv' is marked as crashed and should be repaired

2016-08-05 13:10:13 140389545150336 [Warning] Checking table:   './mysql/tables_priv'

2016-08-05 13:10:13 140389545150336 [ERROR] mysql.tables_priv: 1 client is using or hasn't closed the table properly

2016-08-05 13:10:13 140389545150336 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=mariadb-relay-bin' to avoid this problem.

2016-08-05 13:10:13 140389545150336 [Note] /opt/mariadb/bin/mysqld: ready for connections.

Version: '10.1.9-MariaDB-log'  socket: '/data/mariadb-data/mariadb.sock'  port: 3310  MariaDB Server