Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-345

maxscale.conf in /etc/init.d prevents puppet from starting maxscale

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.3.0
    • Component/s: StartupScripts
    • 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.

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            monotek André Bauer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.