ERROR 2013 (HY000): Lost connection to MySQL server during query

问题:
ERROR 2013 (HY000): Lost connection to MySQL server during query



160613  9:11:45 [ERROR] 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.


To report this bug, see https://mariadb.com/kb/en/reporting-bugs


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.


Server version: 10.1.13-MariaDB
key_buffer_size=67108864
read_buffer_size=262144
max_used_connections=1
max_threads=1026
thread_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 874500 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Thread pointer: 0x0x293fd18
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 = 0x7feb60050188 thread_stack 0x48400
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x29)[0xb411f9]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x72d44a]
/lib64/libpthread.so.0[0x3d9c80f500]
/u01/app/product/11.2.0/dbhome_1/lib/libclntsh.so.11.1(kpuhhaloc+0x486)[0x7feb19adc1be]
/u01/app/product/11.2.0/dbhome_1/lib/libclntsh.so.11.1(kpughndl0+0x237)[0x7feb19b2ece5]
/u01/app/product/11.2.0/dbhome_1/lib/libclntsh.so.11.1(OCIHandleAlloc+0x19)[0x7feb19b01d23]
mysys/stacktrace.c:247(my_print_stacktrace)[0x7feb30857e66]
/u01/app/product/11.2.0/dbhome_1/lib/libsqora.so.11.1(+0x7f167)[0x7feb308af167]
/u01/app/product/11.2.0/dbhome_1/lib/libsqora.so.11.1(SQLAllocHandle+0x31)[0x7feb308af341]
/usr/lib64/libodbc.so.2[0x386880ea94]
/usr/lib64/libodbc.so.2(SQLDriverConnect+0x26c)[0x3868812e6c]
/usr/local/mysql/lib/plugin/ha_connect.so(_ZN7ODBConn13DriverConnectEj+0x63)[0x7feb617cf123]
/usr/local/mysql/lib/plugin/ha_connect.so(_ZN7ODBConn4OpenEPcP10odbc_parmsj+0x55)[0x7feb617d0bf5]
/usr/local/mysql/lib/plugin/ha_connect.so(_Z11ODBCColumnsP7_globalPcS1_S1_S1_ibP10odbc_parms+0x37c)[0x7feb617d159c]
/usr/local/mysql/lib/plugin/ha_connect.so(+0x830c5)[0x7feb617500c5]
sql/sql_table.cc:4822(create_table_impl)[0x635032]
sql/sql_table.cc:4958(mysql_create_table_no_lock(THD*, char const*, char const*, Table_specification_st*, Alter_info*, bool*, int))[0x635663]
sql/sql_table.cc:5019(mysql_create_table(THD*, TABLE_LIST*, Table_specification_st*, Alter_info*))[0x635fa7]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x7c07)[0x5bf007]
sql/sql_parse.cc:3455(mysql_execute_command(THD*))[0x5bf70d]
sql/sql_parse.cc:1486(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x5c21b9]
sql/sql_parse.cc:1109(do_command(THD*))[0x5c2a63]
sql/sql_connect.cc:1349(do_handle_one_connection(THD*))[0x67cfdc]
sql/sql_connect.cc:1263(handle_one_connection)[0x67d120]
/lib64/libpthread.so.0[0x3d9c807851]
/lib64/libc.so.6(clone+0x6d)[0x3d9c4e890d]


Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7feb14009c90): is an invalid pointer
Connection ID (thread ID): 2
Status: NOT_KILLED


Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on


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.
160613 09:11:45 mysqld_safe Number of processes running now: 0
160613 09:11:45 mysqld_safe mysqld restarted
2016-06-13  9:11:45 140148821133280 [Note] /usr/local/mysql/bin/mysqld (mysqld 10.1.13-MariaDB) starting as process 37253 ...
2016-06-13  9:11:45 140148821133280 [Note] CONNECT: Version 1.04.0006 March 12, 2016
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Memory barrier is not used
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Using Linux native AIO
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Using SSE crc32 instructions
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Completed initialization of buffer pool
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: The log sequence numbers 189442946158 and 189442946158 in ibdata files do not match the log sequence number 189442946298 in the ib_logfiles!
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Database was not shutdown normally!
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Starting crash recovery.
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: Restoring possible half-written data pages 
2016-06-13  9:11:45 140148821133280 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 360797321, file name /data/mysql/log/master-bin.000086
2016-06-13  9:11:46 140148821133280 [Note] InnoDB: 128 rollback segment(s) are active.
2016-06-13  9:11:46 140148821133280 [Note] InnoDB: Waiting for purge to start
2016-06-13  9:11:46 140148821133280 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequence number 189442946298
2016-06-13  9:11:46 140147874043648 [Note] InnoDB: Dumping buffer pool(s) not yet started
2016-06-13  9:11:46 140148821133280 [Note] Plugin 'FEEDBACK' is disabled.
2016-06-13  9:11:46 140148821133280 [Note] Recovering after a crash using tc.log
2016-06-13  9:11:46 140148821133280 [Note] Starting crash recovery...
2016-06-13  9:11:46 140148821133280 [Note] Crash recovery finished.
2016-06-13  9:11:46 140148821133280 [Note] Server socket created on IP: '::'.
2016-06-13  9:11:46 140148821133280 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '10.1.13-MariaDB'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution






MariaDB [checkdb]> check table c_9_code;
+--------------------------+-------+----------+----------------------------------------------------------+
| Table                    | Op    | Msg_type | Msg_text                                                 |
+--------------------------+-------+----------+----------------------------------------------------------+
| checkdb.c_9_code | check | Error    | CONNECT Unsupported command                              |
| checkdb.c_9_code | check | Error    | Got error 122 'CONNECT Unsupported command' from CONNECT |
| checkdb.c_9_code | check | error    | Corrupt                                                  |
+--------------------------+-------+----------+----------------------------------------------------------+
3 rows in set (0.00 sec)


解决
/etc/my.cnf
  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
引用:ERROR 2013 (HY000): Lost connection to MySQL server during query(已解决) 1.问题描述 使用mycat连接逻辑库创建表时,出现问题ERROR 2013 (HY000): Lost connection to MySQL server during query 这个错误提示表示在执行MySQL查询时,与MySQL服务器的连接丢失了。这通常是由于网络问题或MySQL服务器配置不正确引起的。 引用:最近在用phpstudy安装discuz时默认数据库mysql8.0.12只在本地,在用phpstudy安装完discuz时数据库正常,但是在命令行执行新建其他数据库的时候报如下错误: 报错 ERROR 2013 (HY000): Lost connection to MySQL server during query 这个错误提示表示在命令行执行创建其他数据库的操作时,与MySQL服务器的连接丢失了。这可能是由于网络问题或MySQL服务器配置不正确引起的。 对于这个问题,你可以尝试以下解决办法: 1. 检查网络连接是否正常,确保你能够正常访问MySQL服务器。 2. 检查MySQL服务器的配置文件,确保配置正确。特别是检查datadir、socket、log-error等参数的设置是否正确。 3. 尝试增加max_allowed_packet参数的值,以便处理更大的查询请求。 4. 检查net_read_timeout和net_write_timeout参数的设置,适当调整其值以避免连接超时。 5. 如果使用的是phpstudy工具,可以尝试使用其他工具如navicat连接数据库,看是否能够正常连接。 希望以上解决办法能够帮到你解决问题,如果还有其他疑问,欢迎进一步交流。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* [ERROR 2013 (HY000): Lost connection to MySQL server during query(已解决)](https://blog.csdn.net/weixin_52457745/article/details/124239964)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] - *2* *3* [Mysql 8.0.12 报错:ERROR 2013 (HY000): Lost connection to MySQL server during query](https://blog.csdn.net/zp357252539/article/details/122872855)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值