MySQL error 2013

Question

In MySQL, how can I solve the error below?

2013: Lost connection to MySQL server at 'reading authorization packet', system error: 0

Have you checked your log file? It may contain some more descriptive information on the problem. — Dana the Sane, Apr 20 '09 at 04:27
Lots of theories on this one, but never a definitive reason. — Carson Reinke, Apr 01 '14 at 17:39

score 12 · Answer 1 · answered Apr 20 '09 at 09:13

From documentation:

More rarely, it can happen when the client is attempting the initial connection to the server. In this case, if your connect_timeout value is set to only a few seconds, you may be able to resolve the problem by increasing it to ten seconds, perhaps more if you have a very long distance or slow connection. You can determine whether you are experiencing this more uncommon cause by using SHOW STATUS LIKE 'aborted_connections'. It will increase by one for each initial connection attempt that the server aborts. You may see “reading authorization packet” as part of the error message; if so, that also suggests that this is the solution that you need.

Try increasing connect_timeout in your my.cnf file

score 4 · Answer 2 · edited Sep 28 '12 at 10:02

4

Adding skip-name-resolve to my.cnf solved the problem for me.

edited Sep 28 '12 at 10:02

Mihai Iorga

39,330
16
106
107

answered Sep 28 '12 at 09:48

Kenneth Andreasen

41
1

Patrick Barry · Answer 3 · 2014-04-05T00:48:55.090

I had this same issue today and it turned out to be an issue with mysql 5.6.*. After uninstalling that and installing 5.5.36, I'm not getting this error anymore.

EDIT: On another computer, I was getting this error very consistently until I set this in my.cnf:

[mysqld]
max_allowed_packet = 32M

Well, technically, my error was slightly different:

_mysql_exceptions.OperationalError: (2013, "Lost connection to MySQL server at 'sending authentication information', system error: 32")

score 1 · Answer 4 · edited May 23 '17 at 11:44

1

If you are using Mac OS X and MySQL 5.6.6 or later, the default value of innodb_file_per_table was changed to ON. Setting innodb_file_per_table = OFF might fix your issue. See Mysql 5.6 headaches on Mac OSX and http://bugs.mysql.com/bug.php?id=71960

edited May 23 '17 at 11:44

Community

1
1

answered Sep 25 '14 at 03:50

Steve Peery

11
1

ethanpil · Answer 5 · 2013-01-28T07:37:06.797

1

I was having this problem too. For me the solution was to comment out the line:

skip_networking

I simply added the comment #, like this:

#skip_networking

And then I restarted mysql and it was all good!

Beware, this will disable all ability to make network connections to MySQL. If you are only using as localhost, it should be fine, but otherwise, watch out! :)

edited Jan 28 '13 at 07:37

answered Oct 11 '11 at 08:47

ethanpil

2,522
2
24
34

why am I voted down? I had a legitimate answer to this exact problem which was solved!? – ethanpil Nov 30 '11 at 17:30
5

skip_networking would stop all socket connections to the database server from outside. Only local servers would be able to connect. – Pradeep Dec 01 '11 at 15:46
2

So what? It still solved the problem for my case, which had nothing to do with remote access. – ethanpil Jan 18 '12 at 07:25

score 0 · Answer 6 · answered Apr 06 '10 at 23:32

0

Check your my.cnf file. set the bind-address to the server's actual IP address.

answered Apr 06 '10 at 23:32

Dennis Day

607
2
5
13

score 0 · Answer 7 · answered Apr 11 '10 at 20:54

0

Take a look at your mysqld log file - there's a high chance 'show status' crashes MySQL for some reason.

answered Apr 11 '10 at 20:54

grateful.dev

1,437
10
21

MySQL error 2013

7 Answers7

Linked