When the Server Does Not Answer
Occasionally a MySQL client gets the catastrophic message "Lost connection to server during query" or
"Server has gone away." Although I hope
you will never face this problem, it’s good to be prepared in case it
happens. There are two main reasons for this problem caused by the MySQL
installation itself: server issues (most likely a crash) or the misuse of
connection options (usually timeout options or max_allowed_packet).
We will discuss the configuration of connections in Chapter 3. Problems caused by hardware and third-party software will be touched on in Chapter 4. Here I want to briefly describe what to do if the server crashes.
First, determine whether you really had a server crash. You can do this with the help of process status monitors. If you run mysqld_safe or another daemon that restarts the server after a failure, the error log will contain a message indicating the server has been restarted. When mysqld starts, it always prints something like this to the error logfile:
110716 14:01:44 [Note] /apps/mysql-5.1/libexec/mysqld: ready for connections. Version: '5.1.59-debug' socket: '/tmp/mysql51.sock' port: 3351 Source distribution
So if you find such a message, the server has been restarted. If there is no message and the server is up and running, a lost connection is most likely caused by the misuse of connection options, which will be discussed in Chapter 3.
Note
If you remember when your MySQL server was originally started, you can use the ...
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