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

Segmentation fault - MaxScale 2.1.10 received fatal signal 11

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.1.10
    • Fix Version/s: N/A
    • Component/s: avrorouter
    • Labels:
      None
    • Environment:
      Debian 9.2.
    • Sprint:
      2017-49

      Description

      After some successful tests, today we found a possible issue with maxscale:

      • Maxscale stopped working while we were doing some inserts, deletes, updates on PartyPersonalDetails table (attached DDL) to test CDC events.
      • Then we looked at maxscale.log (attached), and saw that maxscale process died with an error like this, which seems a segmentation fault:

        2017-12-11 11:29:54   alert  : Fatal: MaxScale 2.1.10 received fatal signal 11. Attempting backtrace.
        

      If we restart maxscale service, it dies again with exactly the same error.

      This is the kind of tests we were doing when the problem raised:

      update PartyPersonalDetails set Gender = 'M' where PP_ID = 'AAAAA'
      

      Attached also the binlog that's causing the error: mariadb-bin.000001.gz

      Could you take a look, and advice any possible cause or solution?

        Attachments

        1. avro.tar.gz
          60 kB
        2. mariadb-bin.000001.gz
          104 kB
        3. maxscale_fault_DDL.sql
          1 kB
        4. maxscale_fault.log.gz
          995 kB

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            c.friaszapater Carlos Frias
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration