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

MaxScale 1.1.1 crashed with Signal 11

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Duplicate
    • 1.1.1
    • 1.3.0
    • readwritesplit
    • None
    • RHEL 6.5

    Description

      After several weeks MaxScale 1.1.1 first crashed with signal 6, and the day after with signal 11:

      2015-08-27 08:07:31 Fatal: MaxScale received fatal signal 11. Attempting backtrace.
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/bin/maxscale() [0x54979c]
      2015-08-27 08:07:31 /lib64/libpthread.so.0() [0x3588c0f710]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/modules/libreadwritesplit.so(+0x3bfb) [0x7f293ccb7bfb]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/modules/libreadwritesplit.so(+0x4d34) [0x7f293ccb8d34]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/modules/libreadwritesplit.so(+0x4767) [0x7f293ccb8767]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/modules/libMySQLClient.so(+0x4c53) [0x7f292905cc53]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/modules/libMySQLClient.so(+0x39c6) [0x7f292905b9c6]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/bin/maxscale() [0x55b9c1]
      2015-08-27 08:07:31 /usr/local/mariadb-maxscale/bin/maxscale(poll_waitevents+0x634) [0x55b280]
      2015-08-27 08:07:31 /lib64/libpthread.so.0() [0x3588c079d1]
      2015-08-27 08:07:31 /lib64/libc.so.6(clone+0x6d) [0x35888e89dd]

      Attachments

        Issue Links

          Activity

            People

              johan.wikman Johan Wikman
              claudio.nanni Claudio Nanni
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.