MySQL 5.6 crashing with stack_bottom = 0 thread_stack 0x30000

I’m having serous trouble with one MySQL server. I was getting permission errors in the log that the plugin and user table was not readable. I tried starting the server with innodb_force_recovery = 1 and --skip-grant-tables, then I could access the tables but the user table was still read only.

But when i now starts the server it just crashes with the errors below:

root@DB11a:~# /usr/sbin/mysqld --skip-grant-tables --basedir=/ --datadir=/data/mysql/data --user=mysql --pid-file=/var/lib/mysql/ --skip-external-locking --port=3306 --socket=/var/lib/mysql/mysql.sock
2017-04-16 04:33:09 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-log) starting as process 15357 …
2017-04-16 04:33:09 15357 [Note] Plugin ‘FEDERATED’ is disabled.
2017-04-16 04:33:09 15357 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-04-16 04:33:09 15357 [Note] InnoDB: The InnoDB memory heap is disabled
2017-04-16 04:33:09 15357 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-04-16 04:33:09 15357 [Note] InnoDB: Memory barrier is not used
2017-04-16 04:33:09 15357 [Note] InnoDB: Compressed tables use zlib 1.2.8
2017-04-16 04:33:09 15357 [Note] InnoDB: Using Linux native AIO
2017-04-16 04:33:09 15357 [Note] InnoDB: Using CPU crc32 instructions
2017-04-16 04:33:09 15357 [Note] InnoDB: Initializing buffer pool, size = 64.0G
2017-04-16 04:33:11 15357 [Note] InnoDB: Completed initialization of buffer pool
2017-04-16 04:33:11 15357 [Note] InnoDB: Highest supported file format is Barracuda.
2017-04-16 04:33:12 15357 [Note] InnoDB: 128 rollback segment(s) are active.
2017-04-16 04:33:12 15357 [Note] InnoDB: Waiting for purge to start
02:33:12 UTC - 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.
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61549549 K bytes of memory
Hope that’s ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
The manual page at contains
information that should help you find out what is causing the crash.

I would realy appriciate any help here.


Can you share the logs from the time when mysql.user table was flagged as not writable the first time?