[MXS-809] Failing to start maxscale with init file on RHEL6 Created: 2016-07-25  Updated: 2016-10-10  Resolved: 2016-10-10

Status: Closed
Project: MariaDB MaxScale
Component/s: init script
Affects Version/s: 1.4.3
Fix Version/s: 2.1.0

Type: Bug Priority: Major
Reporter: Karl Levik Assignee: Timofey Turenko
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

RHEL6.8
MariaDB Cluster 10.1

Attachments: File maxscale.cnf    

 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]

 Comments   
Comment by Karl Levik [ 2016-08-01 ]

I've found a decent work-around for this:

In the init file, /etc/init.d/maxscale, move the user parameter from the maxscale program to the daemon program / command, i.e. change this line:

daemon --pidfile $MAXSCALE_PIDFILE /usr/bin/maxscale --user=maxscale $MAXSCALE_OPTIONS >& /dev/null

to:

daemon --pidfile=$MAXSCALE_PIDFILE --user=maxscale /usr/bin/maxscale $MAXSCALE_OPTIONS >& /dev/null

Comment by Karl Levik [ 2016-08-22 ]

Actually, this problem seems to only apply to our "MariaDB Enterprise Certified Binary" version of MaxScale.

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