Details
Major Description
The --config-check option should not require write access to all directories if the configuration files are readable. The following demonstrates the problem:
$ maxscale --config-check
|
2024-09-20 16:08:53 notice : MaxScale will be run in the terminal process.
|
2024-09-20 16:08:53 notice : MariaDB MaxScale 99.99.99 started (Commit: 57355bfde88b0ee745e653f56bc2e0bae876b5a0)
|
2024-09-20 16:08:53 notice : Process: 524113, Memory: 2.71GiB (2.71GiB total), CPUs: 8.00 (8 total)
|
2024-09-20 16:08:53 notice : Host: 'maxscale', OS: Linux@4.18.0-553.16.1.el8_10.x86_64, #1 SMP Thu Aug 8 17:47:08 UTC 2024, x86_64
|
2024-09-20 16:08:53 notice : Transparent hugepages are set to 'always', MaxScale may end up using more memory than it needs. To disable it, set '/sys/kernel/mm/transparent_hugepage/enabled' to 'madvise'
|
2024-09-20 16:08:53 notice : syslog logging is disabled.
|
2024-09-20 16:08:53 notice : maxlog logging is enabled.
|
2024-09-20 16:08:53 notice : Configuration file: /etc/maxscale.cnf
|
2024-09-20 16:08:53 notice : Log directory: /var/log/maxscale
|
2024-09-20 16:08:53 notice : Data directory: /var/lib/maxscale
|
2024-09-20 16:08:53 notice : Module directory: /usr/lib64/maxscale
|
2024-09-20 16:08:53 notice : Service cache: /var/cache/maxscale
|
2024-09-20 16:08:53 notice : /etc/maxscale.cnf.d exists, reading.
|
2024-09-20 16:08:53 notice : /var/lib/maxscale/maxscale.cnf.d exists, reading.
|
2024-09-20 16:08:53 notice : Module 'mariadbmon' loaded from '/usr/lib64/maxscale/libmariadbmon.so'.
|
2024-09-20 16:08:53 alert : MaxScale doesn't have write permission to '/var/cache/maxscale'.: Permission denied
|