[MXS-578] MaxScale don't start on Debian Jessie + Systemd Created: 2016-02-11  Updated: 2016-03-29  Resolved: 2016-03-29

Status: Closed
Project: MariaDB MaxScale
Component/s: init script, StartupScripts
Affects Version/s: 1.3.0
Fix Version/s: 1.4.1

Type: Bug Priority: Major
Reporter: Emilien Mantel Assignee: Timofey Turenko
Resolution: Cannot Reproduce Votes: 1
Labels: None
Environment:

Debian Jessie 8 (vagrant box debian/jessie64)


 Description   

Hi,

I have many issues with systemd integration of Maxsale on Debian Jessie. I have no problem with sysvinit.

"TimeOutStartSec" is not managed by Debian

----------------------------------------------------------------

root@debian-jessie:~

{3}

# systemctl start maxscale.service
Job for maxscale.service failed. See 'systemctl status maxscale.service' and 'journalctl -xn' for details.
root@debian-jessie:~

{1}# systemctl status maxscale.service
● maxscale.service - MariaDB MaxScale Database Proxy
Loaded: loaded (/lib/systemd/system/maxscale.service; disabled)
Active: failed (Result: exit-code) since Thu 2016-02-11 13:15:45 GMT; 3s ago
Process: 1256 ExecStart=/usr/bin/maxscale --user=maxscale (code=exited, status=1/FAILURE)
Process: 1255 ExecStartPre=/usr/bin/install -d /var/run/maxscale -o maxscale -g maxscale (code=exited, status=0/SUCCESS)

Feb 11 13:15:45 debian-jessie systemd[1]: maxscale.service: control process exited, code=exited status=1
Feb 11 13:15:45 debian-jessie systemd[1]: Failed to start MariaDB MaxScale Database Proxy.
Feb 11 13:15:45 debian-jessie systemd[1]: Unit maxscale.service entered failed state.

----------------------------------------------------------------


h3. Maxscale don't start (TimeOutStartSec removed of systemd service)

----------------------------------------------------------------

root@debian-jessie:~{0}# systemctl start maxscale.service
Job for maxscale.service failed. See 'systemctl status maxscale.service' and 'journalctl -xn' for details.

root@debian-jessie:~{1}

# systemctl status maxscale.service
● maxscale.service - MariaDB MaxScale Database Proxy
Loaded: loaded (/lib/systemd/system/maxscale.service; disabled)
Active: failed (Result: exit-code) since Thu 2016-02-11 13:18:31 GMT; 6s ago
Process: 1315 ExecStart=/usr/bin/maxscale --user=maxscale (code=exited, status=1/FAILURE)
Process: 1312 ExecStartPre=/usr/bin/install -d /var/run/maxscale -o maxscale -g maxscale (code=exited, status=0/SUCCESS)

Feb 11 13:18:31 debian-jessie systemd[1]: maxscale.service: control process exited, code=exited status=1
Feb 11 13:18:31 debian-jessie systemd[1]: Failed to start MariaDB MaxScale Database Proxy.
Feb 11 13:18:31 debian-jessie systemd[1]: Unit maxscale.service entered failed state.

----------------------------------------------------------------

I have no maxscale logs. It seems the programs crashes before lauching logging code.

I can start Maxscale without systemd:

root@debian-jessie:~

{0}# /usr/bin/maxscale --user=maxscale -d
Info : MaxScale will be run in the terminal process.
Configuration file : /etc/maxscale.cnf
Log directory : /var/log/maxscale
Data directory : /var/lib/maxscale/data
Module directory : /usr/lib/x86_64-linux-gnu/maxscale
Service cache : /var/cache/maxscale

^C

Shutting down MaxScale


----------------------------------------------------------------

root@debian-jessie:~{0}

# maxscale --version
MaxScale 1.3.0
root@debian-jessie:~

{0}

# dpkg -l | grep maxscale
ii maxscale 1.3.0 amd64 MaxScale

Cheers,

Emilien

 Comments   
Comment by Emilien Mantel [ 2016-02-18 ]

Hi!

Any news about this bug?

Regards,

Emilien

Comment by markus makela [ 2016-03-01 ]

The capitalization of the TimeOutStartSec has been fixed for 1.4.0 but we haven't been able to reproduce the starting failures.

Comment by Arthur Dali [ 2016-03-09 ]

I'm having the same issue in Debian 8.3. I had it with MaxScale 1.2, and now with 1.3.
Bypassed systemd redirect for now by adding the following to /etc/init.d/maxscale:

export _SYSTEMCTL_SKIP_REDIRECT="true"

Comment by markus makela [ 2016-03-24 ]

Please try this with the 1.4.0 version of MaxScale. You can find the packages on the Portal.

There was a bug in 1.3.0 that sometimes caused no log messages to appear. This has been fixed in 1.4.0 so we'll at least get any missing error messages.

Another option is to run MaxScale from the console with sudo maxscale -d --user=maxscale. This assumes that MaxScale runs as the default maxscale user. This will tell if there are any errors when MaxScale is started.

Comment by Johan Wikman [ 2016-03-29 ]

We are not able to reproduce this bug.

Please try with 1.4.1 and create a new bug-report if it still fails for you.

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