Bug #74290 [Fbk->NoF]: [mysqlnd] Annoying "mysqli::close(): Couldn't fetch mysqli" warning
Edit report at https://bugs.php.net/bug.php?id=74290&edit=1
ID: 74290
Updated by: php-bugs@lists.php.net
Reported by: vedad at kajtaz dot net
Summary: [mysqlnd] Annoying "mysqli::close(): Couldn't fetch
mysqli" warning
-Status: Feedback
+Status: No Feedback
Type: Bug
Package: MySQLi related
Operating System: FreeBSD 10.1
PHP Version: 7.0.17
Private report: N
New Comment:
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2017-05-05 14:03:53] vedad at kajtaz dot net
You're right, the MySQL server (tested w/Percona 5.6) does not send the OK_Packet upon COM_QUIT
and neither does the proxy.
I suspect a script issue (double close) instead. Thanks for investigating and sorry for the noise.
------------------------------------------------------------------------
[2017-05-05 06:13:23] fjanisze@php.net
Neither mysqli nor mysqlnd will raise a warning in case of missing OK_packet after a COM_QUIT
(mysqli::close()) to the server, there must have been something else ongoing with the server during
the COM_QUIT.
The fact that "I'm not using a MySQL server, but a closed source MySQL proxy" let me
think that you closed source version is working differently from the opensource MySQL server, thus
it might not be compliant. From our perspective the server behavior is the ground on which we define
what is an expected or non expected event.
I had a peek at the server code and attempted to execute some test scenario with debug logging
enabled, I dot even see the server sending the packet at all in my local setup and no warning is
raised.
------------------------------------------------------------------------
[2017-04-24 09:05:32] vedad at kajtaz dot net
Hello,
As stated in previous comments, the MySQL proxy in use is MySQL specification-compliant, and I
believe the warning should be removed, as it doesn't report any unexpected/un-compliant
behavior. What kind of additional feedback is needed?
------------------------------------------------------------------------
[2017-04-23 04:22:49] php-bugs at lists dot php dot net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.
------------------------------------------------------------------------
[2017-04-12 12:51:21] vedad at kajtaz dot net
I'm not using a MySQL server, but a closed source MySQL proxy. I can provide a test access if
necessary?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=74290
--
Edit this bug report at https://bugs.php.net/bug.php?id=74290&edit=1
Thread (9 messages)