Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-28146

SST via mysqldump crash when testing MDEV-27246-galera-allowlist

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 10.9(EOL)
    • 10.9.0
    • Galera SST, Server
    • None

    Description

      2022-03-18 20:11:18 0 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 6)
      2022-03-18 20:11:18 4 [Note] WSREP: Requesting state transfer: success, donor: 0
      2022-03-18 20:11:18 4 [Note] WSREP: Resetting GCache seqno map due to different histories.
      2022-03-18 20:11:18 4 [Note] WSREP: GCache history reset: 00000000-0000-0000-0000-000000000000:0 -> 11230f5c-a719-11ec-983c-c7f85e13d114:6
      220318 20:11:18 [ERROR] mysqld got signal 11 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.9.0-MariaDB-1:10.9.0+maria~stretch
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=0
      max_threads=153
      thread_count=3
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467995 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x55b947122aa8
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      stack_bottom = 0x7ffeb6204fa8 thread_stack 0x49000
      /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55b943601b3e]
      /usr/sbin/mariadbd(handle_fatal_signal+0x38f)[0x55b94308239f]
      ??:0(__restore_rt)[0x7f14a8e650e0]
      2022-03-18 20:11:21 0 [Note] WSREP: (18e6473e-be26, 'tcp://127.0.0.1:4567') turning message relay requesting off
      /usr/sbin/mariadbd(_ZN3THD13store_globalsEv+0x24)[0x55b942ded9e4]
      /usr/sbin/mariadbd(_ZN17Master_info_index20init_all_master_infoEv+0x18a)[0x55b942f4c30a]
      /usr/sbin/mariadbd(_Z10init_slavev+0x11c)[0x55b942d9e93c]
      sql/sql_class.cc:2176(THD::store_globals())[0x55b942d5877a]
      csu/libc-start.c:325(__libc_start_main)[0x7f14a824b2e1]
      /usr/sbin/mariadbd(_start+0x2a)[0x55b942d4c89a]

      Attachments

        Issue Links

          Activity

            People

              sysprg Julius Goryavsky
              sysprg Julius Goryavsky
              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.