[MXS-3115] Error loading kubernetes mounted cnf Created: 2020-08-17  Updated: 2020-08-19  Resolved: 2020-08-19

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.3.20, 2.4.11, 2.5.2
Fix Version/s: 2.3.21, 2.4.12, 2.5.3

Type: Bug Priority: Major
Reporter: Stephen Dahl Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: regression
Environment:

kubernetes v1.17.3


Issue Links:
Relates
relates to MXS-1932 MaxScale reads hidden files from maxs... Closed

 Description   

This was reported and fixed in MXS-1932. however I am having this issue now in mariadb/maxscale:2.5.2

when kubernetes mounts files from config maps it creates duplicates of the files in a hidden directory causing me to get the following errors

2020-08-17 14:27:24 notice : MariaDB MaxScale 2.5.2 started (Commit: 72a689b961fdf92feec722453ad6e250e1b2682c
...
2020-08-17 14:27:25 notice : Loading /etc/maxscale.cnf.
2020-08-17 14:27:25 warning: Symbolic link /etc/maxscale.cnf.d/..data in configuration directory points to a directory; it will be ignored.
2020-08-17 14:27:25 notice : Using up to 2.28GiB of memory for query classifier cache
2020-08-17 14:27:25 notice : Loading /etc/maxscale.cnf.d/..2020_08_17_14_21_37.188227681/maxscale.cnf.
2020-08-17 14:27:25 notice : Using up to 2.28GiB of memory for query classifier cache
2020-08-17 14:27:25 notice : Loading /etc/maxscale.cnf.d/maxscale.cnf.
2020-08-17 14:27:25 error : Duplicate section found: mariadb-0
2020-08-17 14:27:25 error : Duplicate section found: mariadb-1
2020-08-17 14:27:25 error : Duplicate section found: mariadb-2
2020-08-17 14:27:25 error : Duplicate section found: MariaDB-Monitor
2020-08-17 14:27:25 error : Duplicate section found: Read-Write-Service
2020-08-17 14:27:25 error : Duplicate section found: Read-Write-Listener
alert : Failed to open, read or process the MaxScale configuration file. See the error log for details.
2020-08-17 14:27:25 alert : Failed to open, read or process the MaxScale configuration file /etc/maxscale.cnf.


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