[MXS-2058] Reload configuration with SIGHUP is broken Created: 2018-09-17  Updated: 2019-04-29  Resolved: 2019-04-29

Status: Closed
Project: MariaDB MaxScale
Component/s: N/A
Affects Version/s: 2.2.14
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Jose Rodriguez Assignee: markus makela
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

I'm trying to reload the configuration file by sending the SIGHUP signal to Maxscale, but I'm persistently getting this error:

2018-09-17 19:38:08   notice : Loading /secrets/maxscale.cnf.
2018-09-17 19:38:08   error  : The [maxscale] section must only be defined in the root configuration file.
2018-09-17 19:38:08   error  : The [maxscale] section must only be defined in the root configuration file.
2018-09-17 19:38:08   error  : The [maxscale] section must only be defined in the root configuration file.
2018-09-17 19:38:08   error  : The [maxscale] section must only be defined in the root configuration file.
2018-09-17 19:38:08   error  : The [maxscale] section must only be defined in the root configuration file.
2018-09-17 19:38:08   error  : Failed to parse configuration file /secrets/maxscale.cnf. Error on line 2.

If I remove the [maxcale] section from the config file manually before sending the signal, then everything works as expected. Am I doing anything wrong on my side?



 Comments   
Comment by markus makela [ 2018-09-18 ]

Unfortunately the reloading of the configuration has never worker properly and has been deprecated in favor of configuration via the REST API and MaxAdmin. It is possible that this behavior was broken by commit a7051307088d854a10ff06736058c064d9ee0d7e.

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