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

"show sessions" can crash MaxScale

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 1.1.0
    • 1.1.0
    • cli, Core
    • None
    • CentOS 6

    Description

      After I hung schemarouter via MXS-79, I killed that session and then executed show sessions via maxadmin. This caused MaxScale to crash.

      2015-03-31 05:30:13   Fatal: MaxScale received fatal signal 11. Attempting backtrace.
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/bin/maxscale() [0x503d0c]
      2015-03-31 05:30:13     /lib64/libpthread.so.0(+0xf710) [0x7f0ff974e710]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/bin/maxscale(dprintAllSessions+0x41) [0x50ebea]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/modules/libcli.so(execute_cmd+0x910) [0x7f0fe36406bb]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/modules/libcli.so(+0x59e8) [0x7f0fe363f9e8]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/modules/libmaxscaled.so(+0x33be) [0x7f0fe1de33be]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/bin/maxscale() [0x515dd5]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/bin/maxscale(poll_waitevents+0x634) [0x515694]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/bin/maxscale(main+0x1a45) [0x50685c]
      2015-03-31 05:30:13     /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f0ff7fedd5d]
      2015-03-31 05:30:13     /usr/local/mariadb-maxscale/bin/maxscale() [0x502b29]

      Attachments

        Activity

          People

            tturenko Timofey Turenko
            kolbe Kolbe Kegel (Inactive)
            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.