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

Assertion failure on galera_bf_abort_shutdown

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.5
    • N/A
    • Galera, Tests
    • None

    Description

      galera.galera_bf_abort_shutdown 'innodb' w5 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2022-10-31 08:31:02
      line
      Attempting backtrace. You can use the following information to find out
      ^ Found warnings in /home/jan/mysql/10.5/mysql-test/var/5/log/mysqld.2.err
      ok
      {noformat]
       
      Error log
      

      2022-10-31 9:59:43 2 [Note] WSREP: Applier thread exiting ret: 0 thd: 2
      2022-10-31 9:59:43 2 [Warning] Aborted connection 2 to db: 'unconnected' user: 'unauthenticated' host: '' (This connection closed normally without authentication)
      221031 10:00:42 [ERROR] mysqld got signal 6 ;
      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.5.18-MariaDB-debug-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=2
      max_threads=153
      thread_count=2
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63745 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0
      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 = 0x0 thread_stack 0x49000
      mysys/stacktrace.c:212(my_print_stacktrace)[0x55dccfe33c5d]
      sql/signal_handler.cc:235(handle_fatal_signal)[0x55dccf51e448]
      libc_sigaction.c:0(__restore_rt)[0x7f011843bcf0]
      linux/clock_nanosleep.c:78(_GI__clock_nanosleep)[0x7f01184ddaf1]
      linux/nanosleep.c:26(_GI__nanosleep)[0x7f01184e2827]
      posix/sleep.c:55(__sleep)[0x7f01184e275e]
      sql/wsrep_mysqld.cc:2893(wsrep_close_client_connections(char, THD*))[0x55dccf8b77c7]
      sql/wsrep_mysqld.cc:1135(wsrep_shutdown_replication())[0x55dccf8b0e7f]
      sql/mysqld.cc:5736(mysqld_main(int, char**))[0x55dccf02c177]
      sql/main.cc:25(main)[0x55dccf021a7d]
      nptl/libc_start_call_main.h:74(__libc_start_call_main)[0x7f0118423510]
      csu/libc-start.c:128(call_init)[0x7f01184235c9]
      ??:0(_start)[0x55dccf021995]

       

      Attachments

        Issue Links

          Activity

            People

              janlindstrom Jan Lindström
              jplindst Jan Lindström (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.