Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.4.3
-
None
-
2016-10
Description
In maxscale.cnf, if I add anywhere:
....
any_string_without_equal_sign
....
MaxScale refuses to start but in the error log there is no evidence of misconfiguration:
May 10 18:38:10 dhcppc6 maxscale[2187]: Finished MaxScale log flusher.
May 10 18:38:11 dhcppc6 maxscale[2187]: MaxScale received signal SIGTERM. Exiting.
May 10 18:38:11 dhcppc6 maxscale[2187]: MaxScale is shutting down.
May 10 18:38:11 dhcppc6 maxscale[2187]: MaxScale shutdown completed.
I think MaxScale should point out at the misconfiguration.
While if you add an option like:
....
blah=123
....
It starts but doesn't complain at all.