[MXS-712] Please recognise some commands seen by the binlog router which trigger error reporting Created: 2016-05-06  Updated: 2016-05-09  Resolved: 2016-05-09

Status: Closed
Project: MariaDB MaxScale
Component/s: binlogrouter
Affects Version/s: 1.4.3
Fix Version/s: 1.4.3

Type: Bug Priority: Minor
Reporter: Simon Mudd Assignee: Massimiliano Pinto (Inactive)
Resolution: Fixed Votes: 0
Labels: None


 Description   

Seen in 1.4.3.2.

The following 2 messages get seen in the maxscale log files triggered by some monitoring scripts etc. They cause no harm but it would be useful if the binlog router could recognise them and respond accordingly:

Unexpected query from 'user'@'10.1.2.3': set autocommit=1
Unexpected query from 'user'@'10.1.2.4': select USER()

The first command just requires some sort of "OK" type response, and the second one would give the given user details, such as:

root@localhost [(none)]> select USER();
+----------------+
| USER()         |
+----------------+
| root@localhost |
+----------------+
1 row in set (0.00 sec)

This is not very important but does keep noisy logging to a minimum.



 Comments   
Comment by Massimiliano Pinto (Inactive) [ 2016-05-09 ]

Working on select USER();

Comment by Massimiliano Pinto (Inactive) [ 2016-05-09 ]

-bash-4.1$ mysql -S /tmp/binlogserver.sock -P 8808 -umassi -pxxx

MySQL [(none)]> select USER();
-----------------------------

USER()

-----------------------------

massi@localhost_from_socket

-----------------------------

-bash-4.1$ mysql -h 127.0.0.1 -P 8808 -umassi -pxxx

MySQL [(none)]> select USER();
-----------------

USER()

-----------------

massi@127.0.0.1

-----------------

-bash-4.1$ mysql -h 198.105.232.15 -P 8808 -umassi -pmassi

MySQL [(none)]> select USER();
---------------------

USER()

---------------------

massi@198.105.232.15

---------------------

Comment by Massimiliano Pinto (Inactive) [ 2016-05-09 ]

Added "set utocommit=1"

MySQL [(none)]> set autocommit=1;
Query OK, 0 rows affected (0.00 sec)

Generated at Thu Feb 08 04:01:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.