[MXS-1818] Maxscale hangs after executing "status;" Created: 2018-04-20 Updated: 2018-04-30 Resolved: 2018-04-30 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | 2.2.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Peter Ruegg | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux |
||
| Issue Links: |
|
||||||||
| Description |
|
After executing a "status;" command (which returns just fine), the current session hangs when executing another command:
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. |
| Comments |
| Comment by markus makela [ 2018-04-20 ] |
|
I believe this will be fixed by this commit: https://github.com/mariadb-corporation/MaxScale/commit/802b16f7094d5cd64a22a5cd748c1f711d4b64d9 |
| Comment by markus makela [ 2018-04-30 ] |
|
Duplicate of |