[MXS-1416] maxscale should not try to do anything when started with --config-check Created: 2017-09-14  Updated: 2018-01-17  Resolved: 2018-01-17

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.1.7
Fix Version/s: 2.1.14

Type: Bug Priority: Minor
Reporter: Oli Sennhauser Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

ubuntu 14.04


Sprint: MXS-SPRINT-50

 Description   

./maxscale/bin/maxscale --config=/home/mysql/tmp/maxscale.cnf --config-check --log=stdout
Info : MaxScale will be run in the terminal process.
Error: Cannot create log directory: /var/log/maxscale

./maxscale/bin/maxscale --config=/home/mysql/tmp/maxscale.cnf --config-check --log=stdout --logdir=/tmp
Info : MaxScale will be run in the terminal process.
Error: Cannot create data directory '/var/lib/maxscale': 13 Permission denied
2017-09-14 17:06:36 notice : MariaDB MaxScale 2.1.7 started
2017-09-14 17:06:36 notice : MaxScale is running in process 12659
2017-09-14 17:06:36 error : Cannot create data directory '/var/lib/maxscale': 13 Permission denied



 Comments   
Comment by markus makela [ 2017-09-14 ]

A workaround to this could be to define all configurable directories as /tmp/.

Comment by markus makela [ 2018-01-17 ]

The config check now skips directory creation and checks.

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