[MXS-1663] MaxScale should detect conflicting configurations and refuse to start Created: 2018-02-12  Updated: 2018-08-20  Resolved: 2018-08-20

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.3.0

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: Marko Rajala (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-1661 Excessive logging by MySQLAuth at aut... Closed
Sprint: MXS-SPRINT-62, MXS-SPRINT-63, MXS-SPRINT-64

 Description   

MaxScale should detect if two or more instances of MaxScale are running on the same computer and refuse to start if they are started in a way that causes conflicts between them.

Case in point; MXS-1661 describes a situation where when there was an authentication error, MaxScale would log database is locked. The reason was that two MaxScale instances were running; both using the same cache directory and thus the same sqlite user database.

When a second MaxScale instances is started, it should detect if there is such a conflict, log a descriptive error message, and refuse to start.


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