[MXS-345] maxscale.conf in /etc/init.d prevents puppet from starting maxscale Created: 2015-08-31  Updated: 2015-09-01  Resolved: 2015-09-01

Status: Closed
Project: MariaDB MaxScale
Component/s: StartupScripts
Affects Version/s: 1.2.0
Fix Version/s: 1.3.0

Type: Bug Priority: Major
Reporter: André Bauer Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None
Environment:

Ubuntu 14.04


 Description   

After installing maxscale 1.2.0 puppet is not longer able to start maxscale:

Info: Retrieving plugin
 
Info: Caching catalog for server.local
 
Info: Applying configuration version '1441033701'
 
Error: Could not start Service[maxscale]: Execution of '/etc/init.d/maxscale.conf start' returned 126: 
Error: /Stage[main]/Loadbalancer::Maxscale/Service[maxscale]/ensure: change from stopped to running failed: Could not start Service[maxscale]: Execution of '/etc/init.d/maxscale.conf start' returned 126:

Imho the file maxscale.conf should go to /etc/init/ instead of /etc/init.d.

 Comments   
Comment by Dipti Joshi (Inactive) [ 2015-08-31 ]

johan.wikman, markus makela Please evaluate this, if this is a real bug or configuration issue on user side.

Comment by markus makela [ 2015-09-01 ]

Puppet seems to try to start the ld.so configuration file which causes the failure. I checked the 1.2.0 code and it seems the file is installed into /etc/init.d instead of /etc/ld.so.conf.d. The installation directory of the ld.so configuration file has been fixed on develop and should work without errors.

To resolve this issue, move the maxscale.conf file in the /etc/init.d folder to /etc/ld.so.conf.d/ and confirm that the maxscale init script is in /etc/init.d/. After this, make sure that Puppet is calling the right script.

Comment by André Bauer [ 2015-09-01 ]

At the moment i just deleted the .conf file. Works for me. ..

markus makela (JIRA) <jira@mariadb.atlassian.net> schrieb am Di., 1. Sep.

Generated at Thu Feb 08 03:58:36 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.