[MXS-1882] Maxscale don't recognize logdir= in /etc/maxscale.cnf.d/maxscale.cnf Created: 2018-05-23  Updated: 2020-08-25  Resolved: 2018-05-28

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.2.5
Fix Version/s: 2.2.7

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Tested on Ubuntu 18.04



 Description   

To reproduce

Create an empty file
/etc/maxscale.cnf

Create a file
/etc/maxscale.cnf.d/maxscale.cnf

with minimum
[MaxScale]
logdir=<wanted_path>

Maxscale use default logging Path (/var/log/maxscale)
instead <wanted_path> for logging.



 Comments   
Comment by markus makela [ 2018-05-24 ]

The code only checks the root level config for the path variables.

Comment by markus makela [ 2018-05-24 ]

The definition of the [maxscale] section in a non-root configuration file (i.e. /etc/maxscale.cnf) is an error that would be detected if both the root and the sub-configuration files had the sections. As the values in this section are essential for MaxScale during the startup period, which includes the configuration parsing, they must only be defined in the root configuration file.

The code needs to be changed to report the correct error if the [maxscale] section is only defined in a sub-configuration file.

Comment by markus makela [ 2018-05-28 ]

Added the missing error message to MaxScale. Defining [maxscale] section in any other file than the root configuration file is now correctly handled as an error.

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