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

Using backend protocol as client protocol causes a crash

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.5
    • Fix Version/s: 2.3.8
    • Component/s: Core
    • Labels:
      None
    • Environment:
      software platform

      Description

      We are trying to setup MaxScale 2.2.5 so we untar the software and created /etc/maxscale.cnf file. We got the below errors while starting up maxscale.

      $ ./bin/maxscale --user=maxscale --basedir=/mysql/maxscale --config=/etc/maxscale.cnf -d
      Info : MaxScale will be run in the terminal process.
      Configuration file : /etc/maxscale.cnf
      Log directory : /mysql/maxscale/var/log/maxscale
      Data directory : /mysql/maxscale/var/lib/maxscale
      Module directory : /mysql/maxscale/lib64/maxscale
      Service cache : /mysql/maxscale/var/cache/maxscale

      Fatal: MaxScale 2.2.5 received fatal signal 11. Attempting backtrace.
      Commit ID: d9e69413b4d18da24aa04e68e3ce9208159a267a System name: Linux Release string: Red Hat Enterprise Linux Server release 7.4 (Maipo)

      ./bin/maxscale[0x407901]
      /lib64/libpthread.so.0(+0xf5e0)[0x7f41367d65e0]

      Writing core dump
      Segmentation fault

      Could you please let us know, is it a bug? or if not please provide us a solution to fix this.

      Thanks,
      Venkat Beru

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              markus makela markus makela
              Reporter:
              venkatberu Venkatarao Beru
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration