Lost connection to MySQL server during query

jdx008

Server version:                5.6.23-log MySQL Community Server (GPL)


mysql> create database t1;
Query OK, 1 row affected (0.00 sec)

mysql> create database t2;
Query OK, 1 row affected (0.00 sec)

mysql> use t1
Database changed
mysql> create table t1 (id int);
Query OK, 0 rows affected (0.19 sec)

mysql> use t2;
Database changed
mysql> create table t1 (id int);
Query OK, 0 rows affected (0.18 sec)

mysql> select * from t1;
Empty set (0.00 sec)

mysql> use t1;
Database changed
mysql> select * from t1;
ERROR 2013 (HY000): Lost connection to MySQL server during query
只要查询 t1 库中的 t1表 mysql 就会重启，查询其他库的表都没问题。



以下是错误日志：
2015-10-09 09:09:35 1412 [ERROR] InnoDB:  InnoDB: Unable to allocate memory of size 18446744073709549848.

2015-10-09 09:09:35 7f6bcbe4f700  InnoDB: Assertion failure in thread 140100959008512 in file ha_innodb.cc line 17113
  InnoDB: Assertion failure in thread 140100959008512 in file ha_innodb.cc line 17113
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
01:09:35 UTC - mysqld got signal 6 ;
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=67108864
read_buffer_size=1048576
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=67108864
read_buffer_size=1048576
max_used_connections=2
max_threads=110
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 = 193763 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3239e30
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...
max_threads=110
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 = 193763 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x3239e30
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 = 7f6bcbe4ee40 thread_stack 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x909d45]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x3d8)[0x6731e8]
/lib64/libpthread.so.0[0x391920f710]
/lib64/libc.so.6(gsignal+0x35)[0x3918e32925]
/lib64/libc.so.6(abort+0x175)[0x3918e34105]
/usr/local/mysql/bin/mysqld[0x91b193]
/usr/local/mysql/bin/mysqld[0x965da7]
/usr/local/mysql/bin/mysqld[0x9661cf]
/usr/local/mysql/bin/mysqld[0x9662d8]
/usr/local/mysql/bin/mysqld[0x9e332b]
/usr/local/mysql/bin/mysqld[0x9e5385]
/usr/local/mysql/bin/mysqld[0x9cd9cb]
/usr/local/mysql/bin/mysqld[0x9c585f]
/usr/local/mysql/bin/mysqld[0x9c664b]
/usr/local/mysql/bin/mysqld[0x98aeaf]
/usr/local/mysql/bin/mysqld[0x98b590]
/usr/local/mysql/bin/mysqld[0xa657f1]
/usr/local/mysql/bin/mysqld[0x92d2ac]
/usr/local/mysql/bin/mysqld(_ZN7handler7ha_openEP5TABLEPKcii+0x3e)[0x58e5be]
/usr/local/mysql/bin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPKcjjjP5TABLEb+0x609)[0x786b89]
/usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0x9d0)[0x6aae30]
/usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0xbbc)[0x6ae1ec]
/usr/local/mysql/bin/mysqld(_Z18mysqld_show_createP3THDP10TABLE_LIST+0x154)[0x72d884]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x13b9)[0x6f3009]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x318)[0x6f8c48]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xbcb)[0x6f9f9b]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0xd7)[0x6fbd97]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x116)[0x6c39b6]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x45)[0x6c3a95]
/lib64/libpthread.so.0[0x39192079d1]
/lib64/libpthread.so.0[0x39192079d1]
/lib64/libc.so.6(clone+0x6d)[0x3918ee8b6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f6bac004a90): Query (7f6bac004a90): is an invalid pointer
Connection ID (thread ID): 10463
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.
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.
151009 09:09:35 mysqld_safe Number of processes running now: 0
151009 09:09:36 mysqld_safe mysqld restarted
2015-10-09 09:09:36 26270 [Note] Plugin 'FEDERATED' is disabled.
2015-10-09 09:09:36 26270 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-10-09 09:09:36 26270 [Note] InnoDB: The InnoDB memory heap is disabled
2015-10-09 09:09:36 26270 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-10-09 09:09:36 26270 [Note] InnoDB: The InnoDB memory heap is disabled
2015-10-09 09:09:36 26270 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-10-09 09:09:36 26270 [Note] InnoDB: Memory barrier is not used
2015-10-09 09:09:36 26270 [Note] InnoDB: Memory barrier is not used
2015-10-09 09:09:36 26270 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-10-09 09:09:36 26270 [Note] InnoDB: Using Linux native AIO
2015-10-09 09:09:36 26270 [Note] InnoDB: Not using CPU crc32 instructions
2015-10-09 09:09:36 26270 [Note] InnoDB: Initializing buffer pool, size = 200.0M
2015-10-09 09:09:36 26270 [Note] InnoDB: Completed initialization of buffer pool
2015-10-09 09:09:36 26270 [Note] InnoDB: Highest supported file format is Barracuda.
2015-10-09 09:09:36 26270 [Note] InnoDB: The log sequence numbers 14372738 and 14372738 in ibdata files do not match the log sequence number 14387689 in the ib_logfiles!
2015-10-09 09:09:36 26270 [Note] InnoDB: Database was not shutdown normally!
2015-10-09 09:09:36 26270 [Note] InnoDB: Starting crash recovery.
2015-10-09 09:09:36 26270 [Note] InnoDB: Database was not shutdown normally!
2015-10-09 09:09:36 26270 [Note] InnoDB: Starting crash recovery.
2015-10-09 09:09:36 26270 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-10-09 09:09:36 26270 [Note] InnoDB: Restoring possible half-written data pages
2015-10-09 09:09:36 26270 [Note] InnoDB: from the doublewrite buffer...
6270 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 1843522, file name mysql-bin.000090
2015-10-09 09:09:37 26270 [Note] InnoDB: 128 rollback segment(s) are active.
2015-10-09 09:09:37 26270 [Note] InnoDB: Waiting for purge to start
2015-10-09 09:09:37 26270 [Note] InnoDB: 5.6.23 started; log sequence number 14387689
2015-10-09 09:09:37 26270 [Note] Recovering after a crash using /data/mysql/mysql3306/logs/mysql-bin
2015-10-09 09:09:37 26270 [Note] Starting crash recovery...
2015-10-09 09:09:37 26270 [Note] Starting crash recovery...
2015-10-09 09:09:37 26270 [Note] Crash recovery finished.
2015-10-09 09:09:37 26270 [Note] Server hostname (bind-address): '*'; port: 3306
2015-10-09 09:09:37 26270 [Note] IPv6 is available.
2015-10-09 09:09:37 26270 [Note]   - '::' resolves to '::';
2015-10-09 09:09:37 26270 [Note] Server socket created on IP: '::'.
2015-10-09 09:09:37 26270 [Warning] 'proxies_priv' entry '@ root@localhost.localdomain' ignored in --skip-name-resolve mode.
2015-10-09 09:09:37 26270 [Note] Event Scheduler: Loaded 0 events
2015-10-09 09:09:37 26270 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.6.23-log'  socket: '/data/mysql/mysql3306/mysql.sock'  port: 3306  MySQL Community Server (GPL)

kider

内存分配超限了，估计与某个表没多大关系了，调小内存分配试试...

kider

看看这篇帖子：http://www.mysqlpub.com/thread-59502-1-1.html