Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 1.4.3
-
Fix Version/s: 2.1.0
-
Component/s: init script
-
Labels:None
-
Environment:RHEL6.8
MariaDB Cluster 10.1
Description
Hello,
After upgrading our dev cluster to MariaDB 10.1 I discovered that MaxScale would no longer start up when using the init script. (I don't think the upgrade is relevant to this problem, but thought I should mention it.)
Nothing gets logged in the maxscale log file when attempting to start it this way.
$ sudo /sbin/service maxscale start
Starting MaxScale: [FAILED]
I am however able to start it as the maxscale user without any problems:
-bash-4.1$ maxscale -d --user=maxscale
Info : MaxScale will be run in the terminal process.
Configuration file : /etc/maxscale.cnf
Log directory : /var/log/maxscale
Data directory : /var/lib/maxscale
Module directory : /usr/lib64/maxscale
Service cache : /var/cache/maxscale
What could be wrong?
Edited to add:
I should add that SELinux is running in permissive mode, so that shouldn't be a problem:
$ sestatus
SELinux status: enabled
SELinuxfs mount: /selinux
Current mode: permissive
Mode from config file: enforcing
Policy version: 24
Policy from config file: targeted
Also, running the init script directly gives the same error:
$ sudo /etc/init.d/maxscale start
Starting MaxScale: [FAILED]