[#MXS-2202] Adding non-existing variable in maxscale does not warn or error

[MXS-2202] Adding non-existing variable in maxscale does not warn or error Created: 2018-11-29 Updated: 2018-11-29 Resolved: 2018-11-29
Status:	Closed
Project:	MariaDB MaxScale
Component/s:	Core
Affects Version/s:	None
Fix Version/s:	2.3.1

Type:

Bug

Priority:

Minor

Reporter:

Claudio Nanni

Assignee:

Unassigned

Resolution:

Fixed

Votes:

Labels:

None

Description

$ cat /etc/maxscale.cnf | head -4

[maxscale]

threads=4

magic_switch_go_faster=1

$ service maxscale start

Starting MaxScale: maxscale (pid 2329) is running...       [  OK  ]

$ cat /var/log/maxscale/maxscale.log | egrep -i "magic|unknown|existing"

In this way we are not sure if a variable is not picked up or it does not exist (/exist any more).

I think it should either error on start or print a warning in the log.

Comments

Comment by markus makela [ 2018-11-29 ]

Already fixed in 2.3.1.

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