Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:MySQL 5.6.13, CentOS 6, 64-bit
Description
Installed MySQL.
Started MySQL.
Installed plugin:
INSTALL PLUGIN server_audit SONAME "server_audit.so";
Stopped MySQL.
Added to my.cnf:
server_audit_logging=OFF server_audit_events=CONNECT,QUERY server_audit_output_type=FILE server_audit_file_path=audit.log server_audit_file_rotate_size=100000
Tried to start MySQL:
Stack Trace:
130822 08:15:58 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2013-08-22 08:15:58 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2013-08-22 08:15:58 26285 [Note] Plugin 'FEDERATED' is disabled. 2013-08-22 08:15:58 26285 [Note] InnoDB: The InnoDB memory heap is disabled 2013-08-22 08:15:58 26285 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2013-08-22 08:15:58 26285 [Note] InnoDB: Compressed tables use zlib 1.2.3 2013-08-22 08:15:58 26285 [Note] InnoDB: Using Linux native AIO 2013-08-22 08:15:58 26285 [Note] InnoDB: Using CPU crc32 instructions 2013-08-22 08:15:58 26285 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2013-08-22 08:15:58 26285 [Note] InnoDB: Completed initialization of buffer pool 2013-08-22 08:15:58 26285 [Note] InnoDB: Highest supported file format is Barracuda. 2013-08-22 08:15:58 26285 [Note] InnoDB: 128 rollback segment(s) are active. 2013-08-22 08:15:58 26285 [Note] InnoDB: Waiting for purge to start 2013-08-22 08:15:59 26285 [Note] InnoDB: 5.6.13 started; log sequence number 1625997 130822 8:15:59 server_audit: STARTED 15:15:59 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. key_buffer_size=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=151 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68225 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)[0x8c90d5] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x65cee4] /lib64/libpthread.so.0[0x3b8060f500] /lib64/libc.so.6[0x3b80332d5f] /usr/sbin/mysqld[0xaec820] /usr/sbin/mysqld[0xaecb60] /usr/lib64/mysql/plugin/server_audit.so(logger_open+0x10a)[0x7ffd398ae2ca] /usr/lib64/mysql/plugin/server_audit.so(+0x3429)[0x7ffd398ae429] /usr/lib64/mysql/plugin/server_audit.so(+0x3624)[0x7ffd398ae624] /usr/sbin/mysqld(_Z23initialize_audit_pluginP13st_plugin_int+0x4f)[0x68894f] /usr/sbin/mysqld[0x6e1fa1] /usr/sbin/mysqld(_Z11plugin_initPiPPci+0xb16)[0x6e5b66] /usr/sbin/mysqld[0x596c21] /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x40d)[0x59b7ad] /lib64/libc.so.6(__libc_start_main+0xfd)[0x3b8021ecdd] /usr/sbin/mysqld[0x58e191] 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. 130822 08:15:59 mysqld_safe mysqld from pid file /var/lib/mysql/audit3.pid ended
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
PSI structure becomes different in MySQL 5.6.
So we have to avoid using it in the 'general purpose' build of the AUDIT PLUGIN.
The fixing patch:
http://lists.askmonty.org/pipermail/commits/2013-September/005399.html