Home » Mysql » MySQL error 2013

MySQL error 2013

Posted by: admin November 29, 2017 Leave a comment

Questions:

In MySQL, how can I solve the error below?

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

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

Questions:
Answers:

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

Questions:
Answers:

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”)

Questions:
Answers:

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! 🙂

Questions:
Answers:

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

Questions:
Answers:

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

Questions:
Answers:

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