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

Fatal signal 11 after slave down

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 6.2.3, 6.3.0
    • N/A
    • Monitor
    • Ubuntu 20.04.4

    Description

      MaxScale service seems to crash and restart following detection of slave no longer running.
      Not sure what exactly this fatal signal 11 refers to.

      2022-04-12 12:28:39 error : Monitor timed out when connecting to server g1sql2[192.168.45.32:3306] : 'Can't connect to server on '192.168.45.32' (110)'
      2022-04-12 12:28:39 notice : Server changed state: g1sql2[192.168.45.32:3306]: slave_down. [Slave, Running] -> [Down]
      2022-04-12 12:28:40 notice : Server changed state: g1sql2[192.168.45.32:3306]: slave_up. [Down] -> [Slave, Running]
      {color:red}2022-04-12 12:28:40 alert : MaxScale 6.2.3 received fatal signal 11. Commit ID: 1ac7a0ddfdb5e7dc2df5d120b4aa9bf5961f0c3e System name: Linux Release string: Ubuntu 20.04.4 LTS
      2022-04-12 12:28:40 alert : Statement currently being classified: none/unknown
      2022-04-12 12:28:40 alert : DCB: 0x7f8b34042610 Session: 7 Service: Read-Write-Service{color}
      2022-04-12 12:28:40 notice : For a more detailed stacktrace, install GDB and add 'debug=gdb-stacktrace' under the [maxscale] section.
      2022-04-12 12:28:41 notice : The systemd watchdog is Enabled. Internal timeout = 30s
      2022-04-12 12:28:41 notice : Worker message queue size: 1MiB
      2022-04-12 12:28:41 notice : Using up to 1.16GiB of memory for query classifier cache
      2022-04-12 12:28:41 notice : syslog logging is disabled.
      2022-04-12 12:28:41 notice : maxlog logging is enabled.
      2022-04-12 12:28:41 notice : Host: 'g1maxscale1' OS: Linux@5.13.0-37-generic, #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC 2022, x86_64 with 4 processor cores.
      2022-04-12 12:28:41 notice : Total usable main memory: 7.77GiB.
      2022-04-12 12:28:41 notice : MariaDB MaxScale 6.2.3 started (Commit: 1ac7a0ddfdb5e7dc2df5d120b4aa9bf5961f0c3e)
      2022-04-12 12:28:41 notice : MaxScale is running in process 97161
      2022-04-12 12:28:41 notice : Configuration file: /etc/maxscale.cnf
      2022-04-12 12:28:41 notice : Log directory: /var/log/maxscale
      

      Attachments

        Activity

          People

            markus makela markus makela
            richNZ99 Richard Lee
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.