[MXS-3885] MaxScale unconditionally loads global options from /etc/maxscale.cnf.d/maxscale.cnf Created: 2021-11-18  Updated: 2021-11-19  Resolved: 2021-11-19

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.5.16
Fix Version/s: 2.4.19, 2.5.17

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


 Description   

If the file /etc/maxscale.cnf.d/maxscale.cnf exists and it contains a [maxscale] section, the file is loaded as if it were a persisted file when it isn't. If the file contains no errors, it is successfully loaded after which the normal file processing proceeds to detect a duplicate section which then causes a misleading error message to be logged. The correct thing to do would be to only use the global config handler for persisted files called maxscale.cnf and only run the global config handler for them, not both.


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