PHP PDO异常+ MySQL上的警告已经走了？[重复]

Question

This question already has an answer here:

MySQL error 2006: mysql server has gone away 17 answers

We are getting both a PDOException and warnings. These warnings are driving us crazy.

Warning: PDOStatement::execute(): MySQL server has gone away in /home/Database.php on line 120

Warning: PDOStatement::execute(): Error reading result set's header in /home/Database.php on line 120

Here is the code that does this -- this is just to simulate a connection going away:

$db = new PDO('mysql:dbname=' . $name . ';host=' . $host, $user, $pass);
$db->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
$db->setAttribute(PDO::ATTR_DEFAULT_FETCH_MODE, PDO::FETCH_ASSOC);

$statement = $db->prepare('SET SESSION wait_timeout = 1');
$statement->execute();

sleep(3);

try {
    $statement = $db->prepare('SELECT 1');
    $statement->execute();
} catch (PDOException $e) {
    echo 'Exception! Err #:' . $e->errorInfo[1] . PHP_EOL;
}

EDIT: The question is why does this generate a warning and an exception. The code above just generates both even though we specifically tell PDO to throw exceptions.
The code above makes it happen faster than waiting for our servers default wait_timeout.

EDIT 2: I'm not sure why this was closed. The question is WHY is PHP spawning both a Warning, and an Exception regardless of the PDO Error Level?

Why are you setting session timeout anyway? What problem are you trying to solve by doing that? You explain symptoms but not what you were actually doing to cause the issue. You also do not explain what you are trying to do. I need to know that. — Ryan Vincent, Dec 4 '15 at 23:12
This is not a duplicate of that question. I'm asking why there are warnings AND exceptions regardless of ATTR_ERRMODE being set to ERRMODE_EXCEPTION. — Michael, Dec 5 '15 at 0:44
Answered with details at stackoverflow.com/questions/35341276 — gaRex, Feb 11 '16 at 14:46

Community · Accepted Answer · 2017-05-23 12:17:54Z

You set wait_timeout to 1 then you sleep 3, what will happen? MySql will close connection after one second and you will get error "Mysql Server has gone away" with next statement 'cause you sleep for 3.

http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout

edit

Question is duplicate of MySQL error 2006: mysql server has gone away

edit 2

Causes of this error:

low wait_timeout - solution: ping, reconnect or increase it too
large packets - solution: tune max_allowed_packet in my.cfg

PDO reconnect - simulate ping in PDO How do i ping the MySQL db and reconnect using PDO

edit 3 question updated

The only way (afaik) to get rid of these warnings is to set expected (eg. E_ERROR) error_reporting level. You could wrapped pdo calls up in for example to set E_ERROR before and reset to default after execution.

PDO logs warnings/errors for logs purposes (sic!) for further analytics. The attribute you set (by setAttribute or constructor) only changes error handling/behavior of pdo - throw or not:). These two things are separated.

The question metioned as the duplicated question isn't explaining how to do this with PDO. But it explains the Mysql logic behind it. — jankal, Dec 4 '15 at 23:04
I updated the question to add a little more detail behind the code snippet. Sorry for the confusion. — Michael, Dec 5 '15 at 0:11
Thanks, that's a possibility I will look into. I'm hoping for something else though. — Michael, Dec 5 '15 at 0:46
I'm still not sure why this was closed (and downvoted), since it was about why there are warnings when you set PDO to give exceptions. Regardless, since you gave an answer that answered the question I am marking it as the best. Thanks. — Michael, Dec 18 '15 at 15:39
THIS is not a duplicate. The question clearly states: Why the f..k PDO gives us warnings when we tell to it to throw exceptions? — gaRex, Feb 11 '16 at 8:09

jankal · Answer 2 · 2015-12-04 22:56:25Z

To prevent this error I'd just add

$db->setAttribute(PDO::ATTR_TIMEOUT,ini_get('max_execution_time'));

to your ->setAttribute calls after creating the PDO object.

I don't really know if this really works, but it should work.

(didn't test it)

I updated the question to add a little more detail behind the code snippet. Sorry for the confusion. — Michael, Dec 5 '15 at 0:11
Unfortunately, PDO::ATTR_TIMEOUT attribute is not supported by MySQL driver. — Krzysztof Przygoda, Mar 23 at 17:00

社区 · Accepted Answer · 2017-05-23 12：17：54Z

你设置wait_timeout为1，然后你睡3，会发生什么？一秒钟后，MySql将关闭连接，您将收到错误“Mysql Server已经消失”与下一个语句'因为你睡3“。

http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout

编辑

问题重复MySQL错误2006：mysql server已经消失了

编辑2

导致此错误的原因：

低wait_timeout - 解决方案：ping，重新连接或增加它
大包 - 解决方案：调用max_allowed_packetmy.cfg

PDO重新连接 - 在PDO中模拟ping 如何ping数据库并使用PDO重新连接

编辑3个问题更新

摆脱这些警告的唯一方法（afaik）是设置预期（例如E_ERROR）error_reporting级别。例如，您可以打包pdo调用来设置E_ERROR，并在执行后将其重置为默认值。

PDO针对日志目的（sic！）记录警告/错误，以进一步分析。您设置的属性（通过setAttribute或构造函数）只会更改pdo-throw或not :)的错误处理/行为。这两件事情是分开的。

重复问题的问题不是解释如何使用PDO来解决问题。但它解释了它后面的Mysql逻辑。 — jankal, Dec 4 '15 at 23:04
我更新了这个问题，在代码段后面添加了一些更多的细节。对困惑感到抱歉。 — Michael, Dec 5 '15 at 0:11
谢谢，这是我会研究的一个可能性。我希望别的东西。 — Michael, Dec 5 '15 at 0:46
我仍然不知道为什么这是关闭（和downvoted），因为它是为什么当你设置PDO给出例外时有警告。无论如何，由于你给出了答案，我回答了我把它标记为最好的问题。谢谢。 — Michael, Dec 18 '15 at 15:39
这不是重复的。这个问题清楚地表明：为什么当我们告诉它抛出异常时，为什么PDO给我们警告？ — gaRex, Feb 11 '16 at 8:09

score -2 · Answer 4

为了防止这个错误，我只是添加

$db->setAttribute(PDO::ATTR_TIMEOUT,ini_get('max_execution_time'));

您->setAttribute创建PDO对象后调用。

我真的不知道这是否真的有效，但它应该有效。

（没测试）

我更新了这个问题，在代码段后面添加了一些更多的细节。对困惑感到抱歉。 — Michael, Dec 5 '15 at 0:11
不幸的是，PDO::ATTR_TIMEOUTMySQL驱动程序不支持属性。 — Krzysztof Przygoda, 3月23日17:00

Community · Accepted Answer · 2017-05-23 12:17:54Z

You set wait_timeout to 1 then you sleep 3, what will happen? MySql will close connection after one second and you will get error "Mysql Server has gone away" with next statement 'cause you sleep for 3.

http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout

edit

Question is duplicate of MySQL error 2006: mysql server has gone away

edit 2

Causes of this error:

low wait_timeout - solution: ping, reconnect or increase it too
large packets - solution: tune max_allowed_packet in my.cfg

PDO reconnect - simulate ping in PDO How do i ping the MySQL db and reconnect using PDO

edit 3 question updated

The only way (afaik) to get rid of these warnings is to set expected (eg. E_ERROR) error_reporting level. You could wrapped pdo calls up in for example to set E_ERROR before and reset to default after execution.

PDO logs warnings/errors for logs purposes (sic!) for further analytics. The attribute you set (by setAttribute or constructor) only changes error handling/behavior of pdo - throw or not:). These two things are separated.

The question metioned as the duplicated question isn't explaining how to do this with PDO. But it explains the Mysql logic behind it. — jankal, Dec 4 '15 at 23:04
I updated the question to add a little more detail behind the code snippet. Sorry for the confusion. — Michael, Dec 5 '15 at 0:11
Thanks, that's a possibility I will look into. I'm hoping for something else though. — Michael, Dec 5 '15 at 0:46
I'm still not sure why this was closed (and downvoted), since it was about why there are warnings when you set PDO to give exceptions. Regardless, since you gave an answer that answered the question I am marking it as the best. Thanks. — Michael, Dec 18 '15 at 15:39
THIS is not a duplicate. The question clearly states: Why the f..k PDO gives us warnings when we tell to it to throw exceptions? — gaRex, Feb 11 '16 at 8:09

score -2 · Answer 6

To prevent this error I'd just add

$db->setAttribute(PDO::ATTR_TIMEOUT,ini_get('max_execution_time'));

to your ->setAttribute calls after creating the PDO object.

I don't really know if this really works, but it should work.

(didn't test it)

I updated the question to add a little more detail behind the code snippet. Sorry for the confusion. — Michael, Dec 5 '15 at 0:11
Unfortunately, PDO::ATTR_TIMEOUT attribute is not supported by MySQL driver. — Krzysztof Przygoda, Mar 23 at 17:00

You are here

piwik Warning - PDOStatement::execute(): Error reading result set's header Warning: PDOStatement::execute(): MySQL server has gone away in

marked as duplicate by Bogdan, amdixon, Bartłomiej Semańczyk, eirenaios, Sufiyan Ghori Dec 5 '15 at 10:11

2 Answers 正确答案

Not the answer you're looking for? Browse other questions tagged php mysql or ask your own question.

PHP PDO异常+ MySQL上的警告已经走了？[重复]

Bogdan，amdixon，BartłomiejSemańczyk，eirenaios，Sufiyan Ghori 被标记为重复12月5日在10:11

2答案正确答案

不是你要找的答案？浏览其他问题标记php mysql 或问自己的问题。

marked as duplicate by Bogdan, amdixon, Bartłomiej Semańczyk, eirenaios, Sufiyan Ghori Dec 5 '15 at 10:11

2 Answers

Not the answer you're looking for? Browse other questions tagged php mysql or ask your own question.

友情链接

搜索表单

用户登录

You are here

piwik Warning - PDOStatement::execute(): Error reading result set's header Warning: PDOStatement::execute(): MySQL server has gone away in

marked as duplicate by Bogdan, amdixon, Bartłomiej Semańczyk, eirenaios, Sufiyan Ghori Dec 5 '15 at 10:11

2 Answers 正确答案

Not the answer you're looking for? Browse other questions tagged php mysql or ask your own question.

PHP PDO异常+ MySQL上的警告已经走了？[重复]

Bogdan，amdixon，BartłomiejSemańczyk，eirenaios，Sufiyan Ghori 被标记为重复12月5日在10:11

2答案 正确答案

不是你要找的答案？浏览其他问题标记php mysql 或问自己的问题。

marked as duplicate by Bogdan, amdixon, Bartłomiej Semańczyk, eirenaios, Sufiyan Ghori Dec 5 '15 at 10:11

2 Answers

Not the answer you're looking for? Browse other questions tagged php mysql or ask your own question.

友情链接

2答案正确答案