140724 11:27:32 mysqld_safe Number of processes running now: 0 140724 11:27:32 mysqld_safe mysqld restarted 2014-07-24 11:27:33 30169 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 11:27:33 30169 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 11:27:33 30169 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 11:27:33 30169 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 11:27:33 30169 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 11:27:33 30169 [Note] InnoDB: Using Linux native AIO 2014-07-24 11:27:33 30169 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 11:27:33 30169 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 11:27:33 30169 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 11:27:33 30169 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 11:27:33 30169 [Note] InnoDB: The log sequence numbers 200844763974 and 200844763974 in ibdata files do not match the log sequence number 250931394180 in the ib_logfiles! 2014-07-24 11:27:33 30169 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 11:27:33 30169 [Note] InnoDB: Starting crash recovery. 2014-07-24 11:27:33 30169 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 11:27:33 30169 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 11:27:33 30169 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 11:27:33 30169 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 11:27:33 30169 [Note] InnoDB: Waiting for purge to start 2014-07-24 11:27:33 30169 [Note] InnoDB: 5.6.19 started; log sequence number 250931394180 2014-07-24 11:27:33 30169 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 11:27:33 30169 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 11:27:33 30169 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 11:27:33 30169 [Note] Event Scheduler: Loaded 0 events 2014-07-24 11:27:33 30169 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 15:28:14 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=1 max_threads=500 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 207043 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0xb6c2cb0 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 = 7f219405ce18 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d68f5] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x663224] /lib64/libpthread.so.0(+0xf710)[0x7f2198610710] /usr/sbin/mysqld[0x7621ae] /usr/sbin/mysqld(_ZN7sys_var6updateEP3THDP7set_var+0x8a)[0x66227a] /usr/sbin/mysqld(_ZN7set_var6updateEP3THD+0x17)[0x6627e7] /usr/sbin/mysqld(_Z17sql_set_variablesP3THDP4ListI12set_var_baseE+0x89)[0x661a29] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2380)[0x6e0200] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x32f)[0x6e2dff] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x140b)[0x6e430b] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xcf)[0x6b112f] /usr/sbin/mysqld(handle_one_connection+0x47)[0x6b1257] /usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xabe12a] /lib64/libpthread.so.0(+0x79d1)[0x7f21986089d1] /lib64/libc.so.6(clone+0x6d)[0x7f2197371b5d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f1ffc0050d0): is an invalid pointer Connection ID (thread ID): 5 Status: NOT_KILLED 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. 140724 11:28:14 mysqld_safe Number of processes running now: 0 140724 11:28:14 mysqld_safe mysqld restarted 2014-07-24 11:28:14 30244 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 11:28:14 30244 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 11:28:14 30244 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 11:28:14 30244 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 11:28:14 30244 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 11:28:14 30244 [Note] InnoDB: Using Linux native AIO 2014-07-24 11:28:14 30244 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 11:28:14 30244 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 11:28:15 30244 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 11:28:15 30244 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 11:28:15 30244 [Note] InnoDB: The log sequence numbers 200844763974 and 200844763974 in ibdata files do not match the log sequence number 250931394190 in the ib_logfiles! 2014-07-24 11:28:15 30244 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 11:28:15 30244 [Note] InnoDB: Starting crash recovery. 2014-07-24 11:28:15 30244 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 11:28:15 30244 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 11:28:15 30244 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 11:28:15 30244 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 11:28:15 30244 [Note] InnoDB: Waiting for purge to start 2014-07-24 11:28:15 30244 [Note] InnoDB: 5.6.19 started; log sequence number 250931394190 2014-07-24 11:28:15 30244 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 11:28:15 30244 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 11:28:15 30244 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 11:28:15 30244 [Note] Event Scheduler: Loaded 0 events 2014-07-24 11:28:15 30244 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 140724 11:29:20 mysqld_safe Number of processes running now: 0 140724 11:29:20 mysqld_safe mysqld restarted 2014-07-24 11:29:21 30283 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 11:29:21 30283 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 11:29:21 30283 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 11:29:21 30283 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 11:29:21 30283 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 11:29:21 30283 [Note] InnoDB: Using Linux native AIO 2014-07-24 11:29:21 30283 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 11:29:21 30283 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 11:29:21 30283 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 11:29:21 30283 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 11:29:21 30283 [Note] InnoDB: The log sequence numbers 200844763974 and 200844763974 in ibdata files do not match the log sequence number 250931394200 in the ib_logfiles! 2014-07-24 11:29:21 30283 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 11:29:21 30283 [Note] InnoDB: Starting crash recovery. 2014-07-24 11:29:21 30283 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 11:29:21 30283 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 11:29:21 30283 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 11:29:21 30283 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 11:29:21 30283 [Note] InnoDB: Waiting for purge to start 2014-07-24 11:29:21 30283 [Note] InnoDB: 5.6.19 started; log sequence number 250931394200 2014-07-24 11:29:21 30283 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 11:29:21 30283 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 11:29:21 30283 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 11:29:21 30283 [Note] Event Scheduler: Loaded 0 events 2014-07-24 11:29:21 30283 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 15:29:41 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=500 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 = 207043 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... 140724 11:33:33 mysqld_safe Starting mysqld daemon with databases from /var/local/mysqldata 2014-07-24 11:33:33 31002 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 11:33:33 31002 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 11:33:33 31002 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 11:33:33 31002 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 11:33:33 31002 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 11:33:33 31002 [Note] InnoDB: Using Linux native AIO 2014-07-24 11:33:33 31002 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 11:33:33 31002 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 11:33:34 31002 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 11:33:34 31002 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 11:33:34 31002 [Note] InnoDB: The log sequence numbers 200844763974 and 200844763974 in ibdata files do not match the log sequence number 250931394210 in the ib_logfiles! 2014-07-24 11:33:34 31002 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 11:33:34 31002 [Note] InnoDB: Starting crash recovery. 2014-07-24 11:33:34 31002 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 11:33:34 31002 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 11:33:34 31002 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 11:33:34 31002 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 11:33:34 31002 [Note] InnoDB: Waiting for purge to start 2014-07-24 11:33:34 31002 [Note] InnoDB: 5.6.19 started; log sequence number 250931394210 2014-07-24 11:33:34 31002 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 11:33:34 31002 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 11:33:34 31002 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 11:33:34 31002 [Note] Event Scheduler: Loaded 0 events 2014-07-24 11:33:34 31002 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 17:38:13 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=1 max_threads=500 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 = 207043 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... 140724 13:38:13 mysqld_safe Number of processes running now: 0 140724 13:38:13 mysqld_safe mysqld restarted 2014-07-24 13:38:14 1603 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 13:38:14 1603 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 13:38:14 1603 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 13:38:14 1603 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 13:38:14 1603 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 13:38:14 1603 [Note] InnoDB: Using Linux native AIO 2014-07-24 13:38:14 1603 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 13:38:14 1603 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 13:38:14 1603 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 13:38:14 1603 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 13:38:14 1603 [Note] InnoDB: The log sequence numbers 200844763974 and 200844763974 in ibdata files do not match the log sequence number 250931394220 in the ib_logfiles! 2014-07-24 13:38:14 1603 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 13:38:14 1603 [Note] InnoDB: Starting crash recovery. 2014-07-24 13:38:14 1603 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 13:38:15 1603 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 13:38:15 1603 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 13:38:15 1603 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 13:38:15 1603 [Note] InnoDB: Waiting for purge to start 2014-07-24 13:38:15 1603 [Note] InnoDB: 5.6.19 started; log sequence number 250931394220 2014-07-24 13:38:15 1603 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 13:38:15 1603 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 13:38:15 1603 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 13:38:16 1603 [Note] Event Scheduler: Loaded 0 events 2014-07-24 13:38:16 1603 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 17:38:24 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=500 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 = 207043 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... 140724 13:39:48 mysqld_safe Starting mysqld daemon with databases from /var/local/mysqldata 2014-07-24 13:39:49 2197 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 13:39:49 2197 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 13:39:49 2197 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 13:39:49 2197 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 13:39:49 2197 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 13:39:49 2197 [Note] InnoDB: Using Linux native AIO 2014-07-24 13:39:49 2197 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 13:39:49 2197 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 13:39:49 2197 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 13:39:49 2197 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 13:39:49 2197 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 13:39:49 2197 [Note] InnoDB: Waiting for purge to start 2014-07-24 13:39:49 2197 [Note] InnoDB: 5.6.19 started; log sequence number 1625987 2014-07-24 13:39:49 2197 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 82dc08dd-1359-11e4-865e-001a4aa87777. 2014-07-24 13:39:49 2197 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 13:39:49 2197 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 13:39:49 2197 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 13:39:49 2197 [Note] Event Scheduler: Loaded 0 events 2014-07-24 13:39:49 2197 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '/var/local/mysqldata/mysql.sock' port: 3306 MySQL Community Server (GPL) 2014-07-24 13:40:08 2197 [Note] /usr/sbin/mysqld: Normal shutdown 2014-07-24 13:40:08 2197 [Note] Giving 0 client threads a chance to die gracefully 2014-07-24 13:40:08 2197 [Note] Event Scheduler: Purging the queue. 0 events 2014-07-24 13:40:08 2197 [Note] Shutting down slave threads 2014-07-24 13:40:08 2197 [Note] Forcefully disconnecting 0 remaining clients 2014-07-24 13:40:08 2197 [Note] Binlog end 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'partition' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'BLACKHOLE' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'ARCHIVE' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_METRICS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_CMPMEM' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_CMP' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_LOCKS' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'INNODB_TRX' 2014-07-24 13:40:08 2197 [Note] Shutting down plugin 'InnoDB' 2014-07-24 13:40:08 2197 [Note] InnoDB: FTS optimize thread exiting. 2014-07-24 13:40:08 2197 [Note] InnoDB: Starting shutdown... 2014-07-24 13:40:09 2197 [Note] InnoDB: Shutdown completed; log sequence number 1625997 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'CSV' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'MRG_MYISAM' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'MyISAM' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'MEMORY' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'sha256_password' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'mysql_old_password' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'mysql_native_password' 2014-07-24 13:40:09 2197 [Note] Shutting down plugin 'binlog' 2014-07-24 13:40:09 2197 [Note] /usr/sbin/mysqld: Shutdown complete 140724 13:40:09 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 140724 13:44:38 mysqld_safe Starting mysqld daemon with databases from /var/local/mysqldata 2014-07-24 13:44:38 2799 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 13:44:38 2799 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 13:44:38 2799 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 13:44:38 2799 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 13:44:38 2799 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 13:44:38 2799 [Note] InnoDB: Using Linux native AIO 2014-07-24 13:44:38 2799 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 13:44:38 2799 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 13:44:39 2799 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 13:44:39 2799 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 13:44:39 2799 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 13:44:39 2799 [Note] InnoDB: Waiting for purge to start 2014-07-24 13:44:39 2799 [Note] InnoDB: 5.6.19 started; log sequence number 1625997 2014-07-24 13:44:39 2799 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 13:44:39 2799 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 13:44:39 2799 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 13:44:39 2799 [Note] Event Scheduler: Loaded 0 events 2014-07-24 13:44:39 2799 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '/var/local/mysqldata/mysql.sock' port: 3306 MySQL Community Server (GPL) 2014-07-24 18:18:29 2799 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='', master_port= 3306, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='tdx-db02', master_port= 3306, master_log_file='test-db02-mysqld-bin.001499', master_log_pos= 105404552, master_bind=''. 2014-07-24 18:18:52 2799 [Note] /usr/sbin/mysqld: Normal shutdown 2014-07-24 18:18:52 2799 [Note] Giving 0 client threads a chance to die gracefully 2014-07-24 18:18:52 2799 [Note] Event Scheduler: Purging the queue. 0 events 2014-07-24 18:18:52 2799 [Note] Shutting down slave threads 2014-07-24 18:18:52 2799 [Note] Forcefully disconnecting 0 remaining clients 2014-07-24 18:18:52 2799 [Note] Binlog end 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'partition' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'BLACKHOLE' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'ARCHIVE' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_FT_DELETED' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_METRICS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_CMPMEM' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_CMP_RESET' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_CMP' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_LOCKS' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'INNODB_TRX' 2014-07-24 18:18:52 2799 [Note] Shutting down plugin 'InnoDB' 2014-07-24 18:18:53 2799 [Note] InnoDB: FTS optimize thread exiting. 2014-07-24 18:18:53 2799 [Note] InnoDB: Starting shutdown... 2014-07-24 18:18:56 2799 [Note] InnoDB: Shutdown completed; log sequence number 83485230396 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'CSV' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'MRG_MYISAM' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'MyISAM' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'MEMORY' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'sha256_password' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'mysql_old_password' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'mysql_native_password' 2014-07-24 18:18:56 2799 [Note] Shutting down plugin 'binlog' 2014-07-24 18:18:56 2799 [Note] /usr/sbin/mysqld: Shutdown complete 140724 18:18:56 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 140724 18:19:04 mysqld_safe Starting mysqld daemon with databases from /var/local/mysqldata 2014-07-24 18:19:05 3729 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 18:19:05 3729 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 18:19:05 3729 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 18:19:05 3729 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 18:19:05 3729 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 18:19:05 3729 [Note] InnoDB: Using Linux native AIO 2014-07-24 18:19:05 3729 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 18:19:05 3729 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 18:19:06 3729 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 18:19:06 3729 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 18:19:06 3729 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 18:19:06 3729 [Note] InnoDB: Waiting for purge to start 2014-07-24 18:19:06 3729 [Note] InnoDB: 5.6.19 started; log sequence number 83485230396 2014-07-24 18:19:06 3729 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 18:19:06 3729 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 18:19:06 3729 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 18:19:06 3729 [Warning] Recovery from master pos 105404552 and file test-db02-mysqld-bin.001499. 2014-07-24 18:19:06 3729 [Note] Event Scheduler: Loaded 0 events 2014-07-24 18:19:06 3729 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '/var/local/mysqldata/mysql.sock' port: 3306 MySQL Community Server (GPL) 2014-07-24 18:19:20 3729 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. 2014-07-24 18:19:20 3729 [Note] Slave SQL thread initialized, starting replication in log 'test-db02-mysqld-bin.001499' at position 105404552, relay log './tdx-db03-relay-bin.000002' position: 4 2014-07-24 18:19:20 3729 [Note] Slave I/O thread: connected to master 'repl_slave@tdx-db02:3306',replication started in log 'test-db02-mysqld-bin.001499' at position 105404552 2014-07-24 18:19:20 3729 [Warning] Slave I/O: Notifying master by SET @master_binlog_checksum= @@global.binlog_checksum failed with error: Unknown system variable 'binlog_checksum', Error_code: 1193 2014-07-24 18:19:20 3729 [Warning] Slave I/O: Unknown system variable 'SERVER_UUID' on master. A probable cause is that the variable is not supported on the master (version: 5.1.73-log), even though it is on the slave (version: 5.6.19), Error_code: 1193 2014-07-24 18:19:21 3729 [ERROR] Slave SQL: Error 'FUNCTION cdna.blob2file does not exist' on query. Default database: 'cdna'. Query: 'insert into cdna.TestCaseFile (TestCaseID_FK, DataType, FileName, BinaryData, CharacterData) values (208858513, 'log', 'vofMultiComponent.ConvectionTurbulentTest.log', _binary'Starting local server: /home/install3/lin64-r8/STAR-CCM+9.05.073-R8/star/bin/starccm+ -np 3 -mpi platform -portrange 10000 -pidfile -server\nStarting STAR-CCM+ parallel server\nIBM Platform MPI licensed for CD-adapco.\nMPI Distribution : Platform Computing MPI-08.3.0.6\nHost 0 -- cloud049 -- Ranks 0-2\nProcess rank 0 cloud049 20119\nTotal number of processes : 3\n\nSTAR-CCM+ 9.05.073 (linux-x86_64-2.5/gnu4.6-r8)\nLicense version: 06 February 2013\nRequired feature version set to 2014.02 or later\nChecking license file: 1999@lnxsrv\nChecking license file: 1999@license\nChecking license file: 1999@linsrv01.lebanon.cd-adapco.com\n1 copy of ccmpsuite checked out from 1999@lnxsrv\nFeature ccmpsuite expires in 281 days\nWed Jul 23 21:41:14 2 2014-07-24 18:19:21 3729 [Warning] Slave: FUNCTION cdna.blob2file does not exist Error_code: 1305 2014-07-24 18:19:21 3729 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'test-db02-mysqld-bin.001499' position 105404552 2014-07-24 18:20:05 3729 [Note] Slave SQL thread initialized, starting replication in log 'test-db02-mysqld-bin.001499' at position 105404552, relay log './tdx-db03-relay-bin.000003' position: 280 22:32:43 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=1 max_threads=500 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 = 207043 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... 140724 18:32:43 mysqld_safe Number of processes running now: 0 140724 18:32:43 mysqld_safe mysqld restarted 2014-07-24 18:32:44 3877 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 18:32:44 3877 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 18:32:44 3877 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 18:32:44 3877 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 18:32:44 3877 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 18:32:44 3877 [Note] InnoDB: Using Linux native AIO 2014-07-24 18:32:44 3877 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 18:32:44 3877 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 18:32:44 3877 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 18:32:44 3877 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 18:32:44 3877 [Note] InnoDB: Log scan progressed past the checkpoint lsn 83485289258 2014-07-24 18:32:44 3877 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 18:32:44 3877 [Note] InnoDB: Starting crash recovery. 2014-07-24 18:32:44 3877 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 18:32:45 3877 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 18:32:45 3877 [Note] InnoDB: from the doublewrite buffer... InnoDB: Doing recovery: scanned up to log sequence number 83490531840 InnoDB: Doing recovery: scanned up to log sequence number 83495774720 InnoDB: Doing recovery: scanned up to log sequence number 83501017600 InnoDB: Doing recovery: scanned up to log sequence number 83506260480 InnoDB: Doing recovery: scanned up to log sequence number 83511503360 InnoDB: Doing recovery: scanned up to log sequence number 83516746240 InnoDB: Doing recovery: scanned up to log sequence number 83517999162 2014-07-24 18:32:46 3877 [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 2014-07-24 18:32:58 3877 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 18:33:02 3877 [Note] InnoDB: Waiting for purge to start 2014-07-24 18:33:02 3877 [Note] InnoDB: 5.6.19 started; log sequence number 83517999162 2014-07-24 18:33:02 3877 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 18:33:02 3877 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 18:33:02 3877 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 18:33:04 3877 [Warning] Recovery from master pos 42834278 and file test-db02-mysqld-bin.001503. 2014-07-24 18:33:04 3877 [Note] Event Scheduler: Loaded 0 events 2014-07-24 18:33:04 3877 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 22:33:34 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=1 max_threads=500 thread_count=2 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 207043 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f89c0000990 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... 2014-07-24 18:33:34 3877 [Warning] Slave SQL: If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0 2014-07-24 18:33:34 3877 [Note] Slave SQL thread initialized, starting replication in log 'test-db02-mysqld-bin.001503' at position 42834278, relay log './tdx-db03-relay-bin.000057' position: 4 stack_bottom = 7f89f7e1ed80 thread_stack 0x40000 /usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8d6885] /usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x663234] /lib64/libpthread.so.0(+0xf710)[0x7f8b7b5d4710] /lib64/libc.so.6(+0x13385f)[0x7f8b7a38085f] /usr/sbin/mysqld(my_strdup+0x1e)[0x8d21ce] /usr/sbin/mysqld(mysql_options+0x513)[0x77daa3] /usr/sbin/mysqld[0x8a40e2] /usr/sbin/mysqld(handle_slave_io+0x812)[0x8ae242] /usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xafc8ea] /lib64/libpthread.so.0(+0x79d1)[0x7f8b7b5cc9d1] /lib64/libc.so.6(clone+0x6d)[0x7f8b7a335b5d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0): is an invalid pointer Connection ID (thread ID): 2 Status: NOT_KILLED 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. 140724 18:33:34 mysqld_safe Number of processes running now: 0 140724 18:33:34 mysqld_safe mysqld restarted 2014-07-24 18:33:34 3930 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 18:33:34 3930 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 18:33:34 3930 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 18:33:34 3930 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 18:33:34 3930 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 18:33:34 3930 [Note] InnoDB: Using Linux native AIO 2014-07-24 18:33:34 3930 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 18:33:34 3930 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 18:33:34 3930 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 18:33:34 3930 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 18:33:34 3930 [Note] InnoDB: The log sequence numbers 83485230396 and 83485230396 in ibdata files do not match the log sequence number 83518006646 in the ib_logfiles! 2014-07-24 18:33:34 3930 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 18:33:34 3930 [Note] InnoDB: Starting crash recovery. 2014-07-24 18:33:34 3930 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 18:33:34 3930 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 18:33:34 3930 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 18:33:35 3930 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 18:33:35 3930 [Note] InnoDB: Waiting for purge to start 2014-07-24 18:33:35 3930 [Note] InnoDB: 5.6.19 started; log sequence number 83518006646 2014-07-24 18:33:35 3930 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 18:33:35 3930 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 18:33:35 3930 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 18:33:36 3930 [Warning] Recovery from master pos 42834278 and file test-db02-mysqld-bin.001503. 2014-07-24 18:33:36 3930 [Note] Event Scheduler: Loaded 0 events 2014-07-24 18:33:36 3930 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 01:21:54 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=1 max_threads=500 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 = 207043 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... 140724 21:21:54 mysqld_safe Number of processes running now: 0 140724 21:21:54 mysqld_safe mysqld restarted 2014-07-24 21:21:54 4193 [Note] Plugin 'FEDERATED' is disabled. 2014-07-24 21:21:54 4193 [Note] InnoDB: Using atomics to ref count buffer pool pages 2014-07-24 21:21:54 4193 [Note] InnoDB: The InnoDB memory heap is disabled 2014-07-24 21:21:54 4193 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2014-07-24 21:21:54 4193 [Note] InnoDB: Compressed tables use zlib 1.2.3 2014-07-24 21:21:54 4193 [Note] InnoDB: Using Linux native AIO 2014-07-24 21:21:54 4193 [Note] InnoDB: Using CPU crc32 instructions 2014-07-24 21:21:54 4193 [Note] InnoDB: Initializing buffer pool, size = 5.0G 2014-07-24 21:21:55 4193 [Note] InnoDB: Completed initialization of buffer pool 2014-07-24 21:21:55 4193 [Note] InnoDB: Highest supported file format is Barracuda. 2014-07-24 21:21:55 4193 [Note] InnoDB: The log sequence numbers 83485230396 and 83485230396 in ibdata files do not match the log sequence number 83518007008 in the ib_logfiles! 2014-07-24 21:21:55 4193 [Note] InnoDB: Database was not shutdown normally! 2014-07-24 21:21:55 4193 [Note] InnoDB: Starting crash recovery. 2014-07-24 21:21:55 4193 [Note] InnoDB: Reading tablespace information from the .ibd files... 2014-07-24 21:21:55 4193 [Note] InnoDB: Restoring possible half-written data pages 2014-07-24 21:21:55 4193 [Note] InnoDB: from the doublewrite buffer... 2014-07-24 21:21:55 4193 [Note] InnoDB: 128 rollback segment(s) are active. 2014-07-24 21:21:55 4193 [Note] InnoDB: Waiting for purge to start 2014-07-24 21:21:55 4193 [Note] InnoDB: 5.6.19 started; log sequence number 83518007008 2014-07-24 21:21:55 4193 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 2014-07-24 21:21:55 4193 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 2014-07-24 21:21:55 4193 [Note] Server socket created on IP: '0.0.0.0'. 2014-07-24 21:21:56 4193 [Warning] Recovery from master pos 42834278 and file test-db02-mysqld-bin.001503. 2014-07-24 21:21:56 4193 [Note] Event Scheduler: Loaded 0 events 2014-07-24 21:21:56 4193 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.6.19' socket: '(null)' port: 3306 MySQL Community Server (GPL) 01:22:17 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=500 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 = 207043 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...