“PHP, by default, sets a read timeout of 60s for streams. Before you send hate mail, please read here first. Eventually, it quits with the “MySQL server has gone away” error. Creating a wait that utilizes the default_socket_timeout. IMPORTANT: Read first about PHP Persistent Database Connections to understand the benefits and caveats.Īlso, adjust PHP’s default_socket_timeout. For example, a PHP script could be running a slow query. It’s also when waiting for the first response from the MySQL server. Try increasing nnect_timeout to match or exceed your MySQL wait_timeout and make sure that mysql.allow_persistent is on (default = enabled). Make sure the nnect_timeout setting isn’t set lower than MySQL wait_timeout, discussed above. The PHP option nnect_timeout is not only used for connect timeout. Adjust or add the following lines in my.cnf to meet your requirements: wait_timeout=90 Also, check the variables: net_read_timeout, net_write_timeout and interactive_timeout. That said, the lower you can set wait_timeout without affecting database connections, can be a good sign of MySQL database efficiency. The default for MySQL wait_timeout is 28800 seconds. You should make sure the wait_timeout is not set too low. MySQL wait_timeout is the number of seconds the server waits for activity on a non-interactive connection before closing it. The reason for MySQL server has gone away error is often because MySQL’s wait_timeout was exceeded.
Datadog Database Monitoring is closely integrated with the rest of the Datadog platform further improve your Database performance with other key features such as SLO tracking, monitors & alerts, Security Monitoring, and more! Utilize our integrations for MySQL, PostgreSQL, SQL Server, and more to visualize key system performance metrics on an out-of-the-box dashboard alongside query and host-level metrics. Easily search, compare, and filter your queries on execution plans to quickly identify areas for performance and cost improvements. Sponsored: Datadog – View query metrics and explain plans from all of your databases in a single place.ĭatadog is a unified monitoring, analytics, and security platform that offers end-to-end monitoring for all of your databases, including MySQL, PostgreSQL, and more! Quickly pinpoint costly, slow queries and troubleshoot performance issues faster with key database metrics and patterns in one place. Lost connection to MySQL server during query Warning: Error while sending QUERY packet PDOException: SQLSTATE: General error: 2006 MySQL server has gone away With this in mind, here are error log examples of the MySQL server has gone away error: General error: 2006 MySQL server has gone away Error Code: 2013. Application Performance Monitoring solutions and PHP Stack trace tools can be of help. In this case, you need to check ALL related error logs with the same timestamp to determine whether another issue may be to blame. Meaning the error could be due to a problem or bug in your connecting application or remote service. In addition, at times, the error is only an indication of a deeper underlying issue. Keep in mind that this error can be logged in a few ways, as listed below. MySQL server has gone away error log examples. If you’ve found a solution not listed or linked to on this page, please send me a note or leave a comment. This article includes solutions I’ve seen for this MySQL server general error. This is partly because, to solve this error, sometimes the solution involves multiple layers, application, or service config changes. MySQL server has gone away, can be a frustrating error to solve.
0 kommentar(er)
