:: DEVELOPER ZONE
MySQL Reference Manual :: A.2.10 Communication Errors and Aborted Connections
Search the MySQL manual:
- A.2 Common Errors When Using MySQL Programs
- A.2.1 Access denied
- A.2.2 Can't connect to [local] MySQL server
- A.2.3 Client does not support authentication protocol
- A.2.4 Password Fails When Entered Interactively
- A.2.5 Host 'host_name' is blocked
- A.2.6 Too many connections
- A.2.7 Out of memory
- A.2.8 MySQL server has gone away
- A.2.9 Packet too large
- A.2.10 Communication Errors and Aborted Connections
- A.2.11 The table is full
- A.2.12 Can't create/write to file
- A.2.13 Commands out of sync
- A.2.14 Ignoring user
- A.2.15 Table 'tbl_name' doesn't exist
- A.2.16 Can't initialize character set
- A.2.17 File Not Found
Additional languages
Additional formats
The server error log can be a useful source of information about
connection problems. See Section 5.10.1, “The Error Log”. Starting with
MySQL 3.23.40, if you start the server with the
--warnings option (or
--log-warnings from MySQL 4.0.3 on), you might
find messages like this in your error log:
010301 14:38:23 Aborted connection 854 to db: 'users' user: 'josh'
If Aborted connections messages appear in the
error log, the cause can be any of the following:
The client program did not call
mysql_close()before exiting.The client had been sleeping more than
wait_timeoutorinteractive_timeoutseconds without issuing any requests to the server. See Section 5.3.3, “Server System Variables”.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:
A client doesn't have privileges to connect to a database.
A client uses an incorrect password.
A connection packet doesn't contain the right information.
It takes more than
connect_timeoutseconds to get a connect packet. See Section 5.3.3, “Server System Variables”.
If these kinds of things happen, it might indicate that someone is trying to break into your server!
Other reasons for problems with aborted clients or aborted connections:
Use of Ethernet protocol with Linux, both half and full duplex. Many Linux Ethernet drivers have this bug. You should test for this bug by transferring a huge file via FTP between the client and server machines. If a transfer goes in burst-pause-burst-pause mode, you are experiencing a Linux duplex syndrome. The only solution is switching the duplex mode for both your network card and hub/switch to either full duplex or to half duplex and testing the results to determine the best setting.
Some problem with the thread library that causes interrupts on reads.
Badly configured TCP/IP.
Faulty Ethernets, hubs, switches, cables, and so forth. This can be diagnosed properly only by replacing hardware.
The
max_allowed_packetvariable value is too small or queries require more memory than you have allocated for mysqld. See Section A.2.9, “Packet too large”.
See also See Section A.2.8, “MySQL server has gone away”.
© 1995-2005 MySQL AB. All rights reserved.
User Comments
Warning: query failed: Unknown column 'user.firstname' in 'field list' in /data0/sites/live/web-main/lib/mysql-cxn.php on line 69
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /data0/sites/live/web-main/lib/docbook.php on line 245
Add your own comment.