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

Maxscale takes signal 11 w/backtrace and ends up hung

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.2.5
    • Fix Version/s: 2.2.7
    • Component/s: maxadmin
    • Labels:
      None
    • Environment:
      RHEL7.4 container

      Description

      In the attached log there are two problems found:
      1. Two cases where maxscale received a signal 11 and generated a stack trace and was restarted
      2. This log was saved when maxscale was apparently hung. There were a number of maxadmin list server commands hung (which we do to verify sanity of maxscale). Running a maxadmin list server just hangs.

      Once we killed all the hung maxadmin list server processes and restarted maxscale, everything was back to normal.

      So two questions:
      (a) why is maxscale taking a signal 11 and restarting
      (b) why is maxscale hanging (unfortunately this is container environment so there is no backtrace capability).

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            rvlane Richard Lane
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration