141102 23:30:23 mysqld_safe Starting mysqld daemon with databases from /u/mysql
2014-11-02 23:30:24 2af6b8399ce0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-02 23:30:24 25381 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-02 23:30:24 25381 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-02 23:30:24 25381 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-11-02 23:30:24 25381 [Note] InnoDB: Memory barrier is not used
2014-11-02 23:30:24 25381 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-02 23:30:24 25381 [Note] InnoDB: Using Linux native AIO
2014-11-02 23:30:24 25381 [Note] InnoDB: Using CPU crc32 instructions
2014-11-02 23:30:24 25381 [Note] InnoDB: Initializing buffer pool, size = 18.0G
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
2014-11-02 23:30:25 25381 [Note] InnoDB: Completed initialization of buffer pool
2014-11-02 23:30:26 25381 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-02 23:30:28 25381 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-02 23:30:28 25381 [Note] InnoDB: Waiting for purge to start
2014-11-02 23:30:28 25381 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 10790146927350
2014-11-02 23:30:28 25381 [Note] RSA private key file not found: /u/mysql//private_key.pem. Some authentication plugins will not work.
2014-11-02 23:30:28 25381 [Note] RSA public key file not found: /u/mysql//public_key.pem. Some authentication plugins will not work.
2014-11-02 23:30:28 25381 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-02 23:30:28 25381 [Note] IPv6 is not available.
2014-11-02 23:30:28 25381 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
2014-11-02 23:30:28 25381 [Note] Server socket created on IP: '0.0.0.0'.
2014-11-02 23:30:28 25381 [Note] Slave SQL thread initialized, starting replication in log 'db2.116407' at position 481198638, relay log './dbslave7-relay-bin.489204' position: 212151674
2014-11-02 23:30:28 25381 [Note] Slave I/O thread: connected to master 'repl@db2.int.company.net:3306',replication started in log 'db2.116407' at position 481198638
2014-11-02 23:30:28 25381 [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-11-02 23:30:28 25381 [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.61-community-log), even though it is on the slave (version: 5.6.21-70.0-log), Error_code: 1193
2014-11-02 23:30:28 25381 [Note] Event Scheduler: Loaded 0 events
2014-11-02 23:30:28 25381 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.21-70.0-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 70.0, Revision 688
2014-11-02 23:30:28 25381 [Warning] IP address '10.129.125.1' could not be resolved: Name or service not known
2014-11-02 23:30:31 25381 [Warning] IP address '192.168.99.2' could not be resolved: Name or service not known
06:10: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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=33
max_threads=502
thread_count=11
connection_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 660185 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2d54b780
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 = 2afbb9716ba0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8bec5c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x651ad1]
/lib64/libpthread.so.0[0x38d380eca0]
/usr/sbin/mysqld(_Z10free_blobsP5TABLE+0x13)[0x74d6f3]
/usr/sbin/mysqld(_ZN14Relay_log_info20clear_tables_to_lockEv+0x31)[0x895551]
/usr/sbin/mysqld(_ZN14Relay_log_info15cleanup_contextEP3THDb+0x7d)[0x8956fd]
/usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0x5d0)[0x8588c0]
/usr/sbin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x61)[0x852231]
/usr/sbin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x23e)[0x88703e]
/usr/sbin/mysqld(handle_slave_sql+0xb96)[0x88a236]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0x8f5643]
/lib64/libpthread.so.0[0x38d380683d]
/lib64/libc.so.6(clone+0x6d)[0x38d30d4fcd]

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

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
141103 00:10:35 mysqld_safe Number of processes running now: 0
141103 00:10:35 mysqld_safe mysqld restarted
2014-11-03 00:10:36 2b6b292c9ce0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2014-11-03 00:10:36 27742 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-11-03 00:10:36 27742 [Note] InnoDB: The InnoDB memory heap is disabled
2014-11-03 00:10:36 27742 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-11-03 00:10:36 27742 [Note] InnoDB: Memory barrier is not used
2014-11-03 00:10:36 27742 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-11-03 00:10:36 27742 [Note] InnoDB: Using Linux native AIO
2014-11-03 00:10:36 27742 [Note] InnoDB: Using CPU crc32 instructions
2014-11-03 00:10:36 27742 [Note] InnoDB: Initializing buffer pool, size = 18.0G
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
InnoDB: HugeTLB: Warning: Failed to allocate 2472542208 bytes. errno 12
InnoDB HugeTLB: Warning: Using conventional memory pool
2014-11-03 00:10:37 27742 [Note] InnoDB: Completed initialization of buffer pool
2014-11-03 00:10:37 27742 [Note] InnoDB: Highest supported file format is Barracuda.
2014-11-03 00:10:37 27742 [Note] InnoDB: Log scan progressed past the checkpoint lsn 10790219474490
2014-11-03 00:10:37 27742 [Note] InnoDB: Database was not shutdown normally!
2014-11-03 00:10:37 27742 [Note] InnoDB: Starting crash recovery.
2014-11-03 00:10:37 27742 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-11-03 00:10:38 27742 [Note] InnoDB: Restoring possible half-written data pages
2014-11-03 00:10:38 27742 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 10790224717312
InnoDB: Doing recovery: scanned up to log sequence number 10790229960192
InnoDB: Doing recovery: scanned up to log sequence number 10790235203072
InnoDB: Doing recovery: scanned up to log sequence number 10790240445952
InnoDB: Doing recovery: scanned up to log sequence number 10790245688832
InnoDB: Doing recovery: scanned up to log sequence number 10790250931712
InnoDB: Doing recovery: scanned up to log sequence number 10790256174592
InnoDB: Doing recovery: scanned up to log sequence number 10790261417472
InnoDB: Doing recovery: scanned up to log sequence number 10790266660352
InnoDB: Doing recovery: scanned up to log sequence number 10790271903232
InnoDB: Doing recovery: scanned up to log sequence number 10790277146112
InnoDB: Doing recovery: scanned up to log sequence number 10790282388992
InnoDB: Doing recovery: scanned up to log sequence number 10790287631872
InnoDB: Doing recovery: scanned up to log sequence number 10790292874752
InnoDB: Doing recovery: scanned up to log sequence number 10790298117632
InnoDB: Doing recovery: scanned up to log sequence number 10790303360512
InnoDB: Doing recovery: scanned up to log sequence number 10790308603392
InnoDB: Doing recovery: scanned up to log sequence number 10790313846272
InnoDB: Doing recovery: scanned up to log sequence number 10790316286064
2014-11-03 00:10:45 27742 [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: In a MySQL replication slave the last master binlog file
InnoDB: position 0 410912948, file name db2.067179
2014-11-03 00:11:12 27742 [Note] InnoDB: 128 rollback segment(s) are active.
2014-11-03 00:11:12 27742 [Note] InnoDB: Waiting for purge to start
2014-11-03 00:11:12 27742 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.21-70.0 started; log sequence number 10790316286064
2014-11-03 00:11:12 27742 [Note] RSA private key file not found: /u/mysql//private_key.pem. Some authentication plugins will not work.
2014-11-03 00:11:12 27742 [Note] RSA public key file not found: /u/mysql//public_key.pem. Some authentication plugins will not work.
2014-11-03 00:11:12 27742 [Note] Server hostname (bind-address): '*'; port: 3306
2014-11-03 00:11:12 27742 [Note] IPv6 is not available.
2014-11-03 00:11:12 27742 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
2014-11-03 00:11:12 27742 [Note] Server socket created on IP: '0.0.0.0'.
2014-11-03 00:11:12 27742 [Note] Slave SQL thread initialized, starting replication in log 'db2.116416' at position 526967736, relay log './dbslave7-relay-bin.489251' position: 258147017
2014-11-03 00:11:12 27742 [Note] Slave I/O thread: connected to master 'repl@db2.int.company.net:3306',replication started in log 'db2.116416' at position 527006807
2014-11-03 00:11:12 27742 [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-11-03 00:11:12 27742 [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.61-community-log), even though it is on the slave (version: 5.6.21-70.0-log), Error_code: 1193
2014-11-03 00:11:12 27742 [Note] Event Scheduler: Loaded 0 events
2014-11-03 00:11:12 27742 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.6.21-70.0-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Percona Server (GPL), Release 70.0, Revision 688
2014-11-03 00:11:13 27742 [Warning] IP address '10.129.125.1' could not be resolved: Name or service not known
2014-11-03 00:11:17 27742 [Warning] IP address '192.168.99.2' could not be resolved: Name or service not known
06:27:08 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=20
max_threads=502
thread_count=19
connection_count=17
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 660185 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x266e1780
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 = 2b7029c45ba0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8bec5c]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x651ad1]
/lib64/libpthread.so.0[0x38d380eca0]
/usr/sbin/mysqld(_Z10free_blobsP5TABLE+0x13)[0x74d6f3]
/usr/sbin/mysqld(_ZN14Relay_log_info20clear_tables_to_lockEv+0x31)[0x895551]
/usr/sbin/mysqld(_ZN14Relay_log_info15cleanup_contextEP3THDb+0x7d)[0x8956fd]
/usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0x5d0)[0x8588c0]
/usr/sbin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x61)[0x852231]
/usr/sbin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x23e)[0x88703e]
/usr/sbin/mysqld(handle_slave_sql+0xb96)[0x88a236]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0x8f5643]
/lib64/libpthread.so.0[0x38d380683d]
/lib64/libc.so.6(clone+0x6d)[0x38d30d4fcd]

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