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

MaxScale 1.4.1 fails to start on Debian 8 (Jessie)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: 1.3.0, 1.4.1
    • Fix Version/s: 1.4.1
    • Component/s: init script
    • Labels:
      None
    • Environment:
      Debian 8.4

      Description

      Opening a new bug as suggested in the comments of MXS-578.

      MaxScale 1.4.1 still fails to start on Debian 8 using systemd. This issue I've had in 1.2 and 1.3 also. In 1.3 I was able to bypass it by adding

      export _SYSTEMCTL_SKIP_REDIRECT="true"

      to /etc/init.d/maxscale

      However that is no longer working with MaxScale 1.4.1.

      I am able to successfully start MaxScale from the command line manually using:

      /usr/bin/maxscale --user=maxscale

      When using systemd the service won't start and log files under /var/log/maxscale do not get updated with any new info whatsoever:

      1. systemctl start maxscale.service
        Job for maxscale.service failed. See 'systemctl status maxscale.service' and 'journalctl -xn' for details.
      1. systemctl status maxscale.service
        ● maxscale.service - MariaDB MaxScale Database Proxy
        Loaded: loaded (/lib/systemd/system/maxscale.service; enabled)
        Active: failed (Result: exit-code) since Tue 2016-04-05 05:38:30 UTC; 24s ago
        Process: 30051 ExecStart=/usr/bin/maxscale --user=maxscale (code=exited, status=1/FAILURE)
        Process: 30048 ExecStartPre=/usr/bin/install -d /var/run/maxscale -o maxscale -g maxscale (code=exited, status=0/SUCCESS)

      Apr 05 05:38:30 look systemd[1]: maxscale.service: control process exited, code=exited status=1
      Apr 05 05:38:30 look systemd[1]: Failed to start MariaDB MaxScale Database Proxy.
      Apr 05 05:38:30 look systemd[1]: Unit maxscale.service entered failed state.

      1. journalctl -xn
        • Logs begin at Tue 2016-04-05 05:14:31 UTC, end at Tue 2016-04-05 05:39:01 UTC. –
          Apr 05 05:38:21 look maxscale[15886]: MaxScale shutdown completed.
          Apr 05 05:38:30 look systemd[1]: maxscale.service: control process exited, code=exited status=1
          Apr 05 05:38:30 look systemd[1]: Failed to start MariaDB MaxScale Database Proxy.
        • Subject: Unit maxscale.service has failed
        • Defined-By: systemd
        • Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
        • Unit maxscale.service has failed.
        • The result is failed.
          Apr 05 05:38:30 look systemd[1]: Unit maxscale.service entered failed state.
          Apr 05 05:39:01 look CRON[31786]: pam_unix(cron:session): session opened for user root by (uid=0)
          Apr 05 05:39:01 look CRON[31787]: pam_unix(cron:session): session opened for user root by (uid=0)
          Apr 05 05:39:01 look CRON[31788]: (root) CMD (command -v pidof > /dev/null && pidof -s cmon >/dev/null || /etc/in
          Apr 05 05:39:01 look CRON[31789]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
          Apr 05 05:39:01 look CRON[31786]: pam_unix(cron:session): session closed for user root
          Apr 05 05:39:01 look CRON[31787]: pam_unix(cron:session): session closed for user root

        Attachments

          Activity

            People

            Assignee:
            tturenko Timofey Turenko
            Reporter:
            ek6dali Arthur Dali
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration