Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
2.3.4
-
None
-
Linux x85_64. CentOS 7.6
-
MXS-SPRINT-82
Description
When using the tpmfilter filter, connecting using the mysql command line and changing database using the use command cause a signal 11 with MaxScale.
MaxScale.cnf extract:
[tpmfilter]
|
type=filter |
module=tpmfilter
|
filename=/tmp/tpm.log |
|
|
[DefaultService]
|
type=service |
router=readwritesplit
|
servers=server0
|
user=myuser
|
password=mypwd
|
filters=tpmfilter
|
And then run mysql
anders@moe:~$ mysql -h 192.168.0.11 -P 4004 -uanka -panka test |
Reading table information for completion of table and column names |
You can turn off this feature to get a quicker startup with -A |
|
|
Welcome to the MariaDB monitor. Commands end with ; or \g.
|
Your MariaDB connection id is 5 |
Server version: 10.3.12-MariaDB MariaDB Server |
|
|
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. |
|
|
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. |
|
|
MariaDB [test]> use test
|
ERROR 2013 (HY000): Lost connection to MySQL server during query |
MariaDB [test]>
|
And in /var/log/maxscale/maxscale.log we get
2019-03-18 10:34:22 error : (5) The provided buffer does not contain a COM_QUERY, but a COM_INIT_DB. |
2019-03-18 10:34:22 error : (5) The query could not be parsed. Response not valid. |
2019-03-18 10:34:22 alert : (5) Fatal: MaxScale 2.3.4 received fatal signal 11. Attempting backtrace. |
2019-03-18 10:34:22 alert : (5) Commit ID: aea64aede280558ca6b55500dfa7eb049ec9c377 System name: Linux Release string: NAME="CentOS Linux" |
2019-03-18 10:34:22 alert : (5) /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceESt8functionIFvPKcS2_EE+0x2b) [0x40cbab]: /home/vagrant/MaxScale/maxutils/maxbase/src/stacktrace.cc:130 |
2019-03-18 10:34:22 alert : (5) /usr/bin/maxscale(_ZN7maxbase15dump_stacktraceEPFvPKcS1_E+0x4e) [0x40cf0e]: /usr/include/c++/4.8.2/functional:2029 |
2019-03-18 10:34:22 alert : (5) /usr/bin/maxscale() [0x4095b9]: ??:0 |
2019-03-18 10:34:22 alert : (5) /lib64/libpthread.so.0(+0xf5d0) [0x7f546b54b5d0]: sigaction.c:? |
2019-03-18 10:34:22 alert : (5) /usr/lib64/maxscale/libqc_sqlite.so(+0xbe74) [0x7f5465a0fe74]: /home/vagrant/MaxScale/query_classifier/qc_sqlite/qc_sqlite.cc:248 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(qc_get_type_mask+0x351) [0x7f546bcab641]: /usr/include/c++/4.8.2/ext/new_allocator.h:104 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libtpmfilter.so(+0x307b) [0x7f5462d8f07b]: /home/vagrant/MaxScale/server/modules/filter/tpmfilter/tpmfilter.cc:473 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(session_route_query+0x18) [0x7f546bcd6e38]: /home/vagrant/MaxScale/server/core/session.cc:1024 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmariadbclient.so(+0x5d6f) [0x7f54635f1d6f]: /home/vagrant/MaxScale/server/modules/protocol/MySQL/mariadbclient/mysql_client.cc:1785 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7c957) [0x7f546bc88957]: /home/vagrant/MaxScale/server/core/dcb.cc:3136 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(+0x7caf1) [0x7f546bc88af1]: /home/vagrant/MaxScale/server/core/dcb.cc:3228 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker15poll_waiteventsEv+0x1b5) [0x7f546bce45c5]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:844 |
2019-03-18 10:34:23 alert : (5) /usr/lib64/maxscale/libmaxscale-common.so.1.0.0(_ZN7maxbase6Worker3runEPNS_9SemaphoreE+0x51) [0x7f546bce47c1]: /home/vagrant/MaxScale/maxutils/maxbase/src/worker.cc:545 |
2019-03-18 10:34:23 alert : (5) /usr/bin/maxscale(main+0x2019) [0x4087f9]: /home/vagrant/MaxScale/server/core/gateway.cc:2259 |
2019-03-18 10:34:23 alert : (5) /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f546941e3d5]: ??:? |
2019-03-18 10:34:23 alert : (5) /usr/bin/maxscale() [0x409022]: ??:0 |