[MXS-720] MaxScale fails to start and doesn't log any useful message when there are spurious characters in the config file Created: 2016-05-12 Updated: 2016-05-20 Resolved: 2016-05-20 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | 2.0.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Claudio Nanni | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2016-10 |
| Description |
|
In maxscale.cnf, if I add anywhere: .... 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. I think MaxScale should point out at the misconfiguration. While if you add an option like: .... It starts but doesn't complain at all. |
| Comments |
| Comment by Claudio Nanni [ 2016-05-13 ] |
|
Even more interestingly, if I mistype an existing basic setting, like: tipe=monitor, it fails to start, or also usera=mysql. |
| Comment by Timofey Turenko [ 2016-05-16 ] |
|
Duplicate of |
| Comment by Claudio Nanni [ 2016-05-16 ] |
|
Timofey, I don't think so, similar because it doesn't log the problem, but the problem is different, also read my previous comment on how it behaves with mistyped options. |
| Comment by Timofey Turenko [ 2016-05-18 ] |
|
tests ' maxscale.cnf.template.mxs720_wierd_line' and 'mxs720_line_with_no_equal' added. |
| Comment by markus makela [ 2016-05-20 ] |
|
Configuration errors are now properly logged. |