Chinaunix首页 | 论坛 | 博客
  • 博客访问: 320800
  • 博文数量: 96
  • 博客积分: 230
  • 博客等级: 二等列兵
  • 技术积分: 722
  • 用 户 组: 普通用户
  • 注册时间: 2012-02-13 22:25
个人简介

心安处即吾乡!

文章分类

全部博文(96)

文章存档

2016年(1)

2014年(79)

2013年(7)

2012年(9)

我的朋友

分类: LINUX

2014-04-17 20:05:15

ERROR Message :

081016 23:25:44 Aborted connection 31084472 to db: ‘ms’ user: ‘login’ host: `x.x.x.12′ (Got timeout reading communication packets)

081016 23:25:44 Aborted connection 31084391 to db: ‘ms’ user: ‘login’ host: `x.x.x.13′ (Got timeout reading communication packets)

081016 23:25:44 Aborted connection 31084488 to db: ‘ms’ user: ‘login’ host: `x.x.x.15′ (Got timeout reading communication packets)

081016 23:25:44 Aborted connection 31084509 to db: ‘ms’ user: ‘login’ host: `x.x.x.15′ (Got timeout reading communication packets)

081016 23:25:45 Aborted connection 31084518 to db: ‘ms’ user: ‘login’ host: `x.x.x..11′ (Got an error reading communication packets)

The below are the Reasons to get the above error :

Aborted connections messages appear in the error log, the cause can be any of the following:

1) The client program did not call mysql_close() before exiting.

2) The client had been sleeping more than wait_timeout or interactive_timeout seconds without issuing any requests to the server.

3) The client program ended abruptly in the middle of a data transfer.

When any of these things happen, the server increments the Aborted_clients status variable.

The server increments the Aborted_connects status variable when the following things happen:

1) A client doesn’t have privileges to connect to a database.

2) A client uses an incorrect password.

3) A connection packet doesn’t contain the right information.

4) It takes more than connect_timeout seconds to get a connect packet.


-Suresh Kuna

阅读(3123) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~