Server Crash in thd_killed When Audit Log Plugin is Enabled (Doc ID 2140369.1)

Last updated on MAY 21, 2016

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Symptoms

MySQL server crashes with the following in the error log (focus is on the bold text):

03:36:05 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=197
max_threads=1264
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 632441 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 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0xf8a355]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x7b0ca4]
/lib64/libpthread.so.0[0x37a6e0eca0]
/usr/sbin/mysqld(thd_killed+0x26)[0xd04bb6]
/usr/sbin/mysqld(my_write+0xae)[0xf891ee]
/usr/lib64/mysql/plugin/audit_log.so(alog_writer+0x1fd)[0x2b4f5b06b80d]
/usr/sbin/mysqld(pfs_spawn_thread+0x174)[0x125e224]
/lib64/libpthread.so.0[0x37a6e0683d]
/lib64/libc.so.6(clone+0x6d)[0x37a66d4fcd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2016-05-17T03:36:09.474786Z mysqld_safe Number of processes running now: 0
2016-05-17T03:36:09.585701Z mysqld_safe mysqld restarted

 

Changes

 The disk where MySQL Audit Log writes its logs has become full.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms