-
Notifications
You must be signed in to change notification settings - Fork 976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing often with strange new error (Error setting MYSQL_OPTION_MULTI_STATEMENTS) #2727
Comments
Hi. Meanwhile I would like to find a way to reduce the probability of hitting such bug. |
Hi @renecannao, and thanks for your quick reply. Yes, we have a lot of such errors ( After enabled general log on each mysql node I found this strange activity by monitor user (the time is corresponding to the crash):
Someone have an idea why Monitor should execute this query The complete proxysql.log was sent to renecannao gmail. Thanks a lot, |
Hi again, the post below (about The crash continues even after setting and loading the mysql variables to runtime:
Even after disabling ProxySQL Cache it's still crashing... If someone has an idea how to decrease the chances to hit this bug please share. Thanks |
Hi @dzadzakin . Ignore what monitor user is doing, it is absolutely not related. What I would recommend now (before checking the log) is to increase global wait_timeout on MySQL server (not in proxysql). Thanks |
Hi @renecannao,
Thanks for your reply.
Following your recommendation I discovered a strange wait_timeout setting
on each node of our XtraDB Percona Cluster:
mysql> SELECT @@global.wait_timeout , @@session.wait_timeout;
+-----------------------+------------------------+
| @@global.wait_timeout | @@session.wait_timeout |
+-----------------------+------------------------+
| 150 | 28800 |
+-----------------------+------------------------+
1 row in set (0.00 sec)
I always used this query (which probably returns only the value for current
session):
mysql> show variables like '%wait_timeout%';
+-------------------------------------+----------+
| Variable_name | Value |
+-------------------------------------+----------+
| innodb_lock_wait_timeout | 120 |
| innodb_print_lock_wait_timeout_info | OFF |
| lock_wait_timeout | 31536000 |
| wait_timeout | 28800 |
+-------------------------------------+----------+
4 rows in set (0.00 sec)
I set global wait_timeout to 28800 too:
mysql> SET GLOBAL wait_timeout = 28800;
Query OK, 0 rows affected (0.00 sec)
mysql> SELECT @@global.wait_timeout , @@session.wait_timeout;
+-----------------------+------------------------+
| @@global.wait_timeout | @@session.wait_timeout |
+-----------------------+------------------------+
| 28800 | 28800 |
+-----------------------+------------------------+
1 row in set (0.00 sec)
Can you please confirm that this could be a good reason of multiple crashes
(almost 50 in 2 days)?
I'll continue to monitor the situation, it's about 45 min since this change
and and no crash.
Thanks a lot
…On Sun, 3 May 2020 at 14:02, René Cannaò ***@***.***> wrote:
Hi @dzadzakin <https://github.com/dzadzakin> .
Thank you for the log.
I haven't review it yet.
Ignore what monitor user is doing, it is absolutely not related.
What I would recommend now (before checking the log) is to increase global
wait_timeout on MySQL server (not in proxysql).
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2727 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AESFGSKJCTL5ZUBSUYD7CEDRPVML5ANCNFSM4MXOIDVQ>
.
|
Hi all, low wait_timeout (150) caused the crash and plenty of errors related to pings. Thanks all, |
Hi @dzadzakin . Thanks |
Hi @renecannao, and thanks for the workaround and the fix. Keep up the great work with ProxySQL, dzadzakin |
Thank you for the feedback @dzadzakin . Closing, as fixed in 2.0.12 |
Hi everyone,
yesterday we started to receive multiple crashes of ProxySQL.
Inside captured information by tcpdump on ProxySQL instance there is no any multi statement query or any attempt to set it.
We also tried to disable mysql-client_multi_statements but it not helps (after saving and reloading the global variables to runtime).
Our Mysql clients are receiving the following errors:
Below is the ProxySQL log:
Below is the output of core dump with gdb:
Can you help please?
Thanks
The text was updated successfully, but these errors were encountered: