Centsos 6.7

Could you please provide some additional details.

• What did you do?
• What did you expect to happen?
• What was the actual outcome?

max-admin

MaxScale> enable log-priority debug
MaxScale>

then
session b
mysql -u max -pmaxscale -h 192.168.143.188 -P4007 -e "select * from make.student limit 1"
----------------------------------+

----------------------------------+

----------------------------------+

**********************************************

[root@bogon log]# ll
total 0
rw-rr- 1 root root 0 Jul 26 14:57 maxscale.log
[root@bogon log]# tailf maxscale.log
nothing

**********************************************
global config

[maxscale]
threads=auto
auth_connect_timeout = 3
auth_read_timeout = 1
auth_write_timeout = 2
ms_timestamp=1
syslog=0
maxlog=1
logdir=/data/maxscale1/log
datadir=/data/maxscale1/data
cachedir=/data/maxscale1_cache
piddir=/data/maxscale1
libdir=/usr/local/maxscale-2.1.3/lib/maxscale

This is caused by the fact that debug logging is only enabled for debug builds due to the high performance impact it can cause. The command should not be accepted on non-debug builds and it should return an error.

Changed into a bug-report.

Not a bug as debug messages are enabled only if MaxScale has been built in debug mode.

But now the user of maxadmin will get a warning about enabling debug logging having no effect if MaxScale is built in release mode.