Common Errors When Using MySQL
This section lists some errors that users frequently get. You will find descriptions of the errors and how to solve the problems here.
Access denied Error
See Section 4.2.6, and especially, see Section 4.2.11.
MySQL server has gone away Error
This section also covers the related Lost connection to server during query error.
The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection. By default, the server closes the connection after 8 hours if nothing has happened. You can change the time limit by setting the wait_timeout variable when you start mysqld.
Another common reason to receive the MySQL server has gone away error is because you have issued a “close” on your MySQL connection and then tried to run a query on the closed connection.
If you have a script, you just have to issue the query again for the client to do an automatic reconnection.
You normally can get the following error codes in this case (which one you get is OS-dependent):
|
Error code |
Description |
|---|---|
|
CR_SERVER_GONE_ERROR |
The client couldn’t send a question to the server. |
|
CR_SERVER_LOST |
The client didn’t get an error when writing to the server, but it didn’t get a full answer (or any answer) to the question. |
You will also get this error if someone has kills the running thread with kill #threadid#.
You can check that MySQL hasn’t died by executing mysqladmin version and examining the uptime. If the problem is that mysqld crashed you ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access