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

MaxScale can time out systemd if startup of services takes too long

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.1
    • Fix Version/s: 1.3.0
    • Component/s: Core
    • Labels:
      None

      Description

      This relates to the fix to MXS-35 which makes MaxScale wait until it has daemonized itself and that all services have been started before exiting. This causes a problem if the startup takes longer than the default timeout of 90 seconds.

      Either a timeout in the maxscale.service file needs to be added or a way to start MaxScale without waiting for the services to start needs to be added. The preferred option would be to increase the timeout in maxscale.service.

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MXS-35 bugzillaId-451: maxscale main() exit code is always 0 after it daemonizes

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              markus makela markus makela
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.