Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
2.2.4
-
None
-
Linux
Description
After executing a "status;" command (which returns just fine), the current session hangs when executing another command:
$ mysql -u maxscale -p -P 3307 -h 127.0.0.1
|
Enter password:
|
Welcome to the MariaDB monitor. Commands end with ; or \g.
|
Your MySQL connection id is 20808
|
Server version: 10.2.12 2.2.4-maxscale mariadb.org binary distribution
|
|
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
|
|
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
|
|
MySQL [(none)]> status;
|
--------------
|
mysql Ver 15.1 Distrib 10.1.32-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
|
|
Connection id: 20808
|
Current database:
|
Current user: maxscale@10.144.160.60
|
SSL: Not in use
|
Current pager: stdout
|
Using outfile: ''
|
Using delimiter: ;
|
Server: MySQL
|
Server version: 10.2.12 2.2.4-maxscale mariadb.org binary distribution
|
Protocol version: 10
|
Connection: 127.0.0.1 via TCP/IP
|
Server characterset: utf8
|
Db characterset: utf8
|
Client characterset: utf8mb4
|
Conn. characterset: utf8mb4
|
TCP port: 3307
|
Uptime: 9 days 15 hours 21 min 38 sec
|
|
Threads: 7 Questions: 20772825 Slow queries: 0 Opens: 175 Flush tables: 1 Open tables: 169 Queries per second avg: 24.940
|
--------------
|
|
MySQL [(none)]> show status;
|
After this, nothing happens anymore. It does not seem to matter what other command is executed, it hangs for all of them.
Doing the same on the MariaDB server (not going through maxscale) works just fine. Doing it on a 2.1.9 maxscale works just fine as well.
Since check_mysql from Ubuntu's monitoring-plugins-standard first issues a mysql_stat, which appears to be the same thing and then another command ("show global status") this shows up in our monitoring - actually has been for a couple of months.
Attachments
Issue Links
- duplicates
-
MXS-1786 Hang with COM_STATISTICS
- Closed