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

galera_sr.GCF-597 MTR failed: Crash with SIGABRT

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.4.18
    • N/A
    • Galera, Tests
    • None
    • kvm-rpm-fedora32-amd64

    Description

      galera_sr.GCF-597 failed on BB 10.4 CS: Crash with SIGABRT.
      It seems to be a sporadic issue.

      stdio.log:

      10.4.18, 542d769ea1a22a7a6a87c9fe76ff911a162ade44, kvm-rpm-fedora32-amd64

      galera_sr.GCF-597 'innodb'               w1 [ fail ]  timeout after 900 seconds
              Test ended at 2021-01-28 08:09:37
       
      Test case timeout after 900 seconds
       
      == /dev/shm/var/1/log/GCF-597.log == 
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      connection node_2;
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      INSERT INTO t1 VALUES (1);
      connection node_1;
      INSERT INTO t1 VALUES (1);
      INSERT INTO t1 VALUES (2);
      INSERT INTO t1 VALUES (3);
      INSERT INTO t1 VALUES (4);
      INSERT INTO t1 VALUES (5);
      connect node_1a, 127.0.0.1, root, , test, $NODE_MYPORT_1;
      connection node_1a;
      connect node_2a, 127.0.0.1, root, , test, $NODE_MYPORT_2;
      connection node_2a;
      connection node_2;
      ROLLBACK;
      ERROR 40001: Deadlock found when trying to get lock; try restarting transaction
      DROP TABLE t1;
       
      The server [mysqld.1 - pid: 39144, winpid: 39144, exit: 256] crashed while running 'analyze-timeout'
      Server log from this test:
      ----------SERVER LOG START-----------
      210128  8:08:19 [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.4.18-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=3
      max_threads=153
      thread_count=11
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63536 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
      2021-01-28  8:08:19 69 [Warning] Aborted connection 69 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      2021-01-28  8:08:19 67 [Warning] Aborted connection 67 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      2021-01-28  8:08:31 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.80457S), skipping check
      mysys/stacktrace.c:175(my_print_stacktrace)[0x55de471ea14e]
      /usr/sbin/mysqld(handle_fatal_signal+0x54d)[0x55de46cb19cd]
      2021-01-28  8:08:45 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.90036S), skipping check
      sigaction.c:0(__restore_rt)[0x7f69c43caa90]
      :0(__GI___poll)[0x7f69c3a48b6f]
      sql/mysqld.cc:6487(handle_connections_sockets())[0x55de469cfb7f]
      psi/mysql_thread.h:692(mysqld_main(int, char**))[0x55de469d0a6d]
      /lib64/libc.so.6(__libc_start_main+0xf2)[0x7f69c3979042]
      /usr/sbin/mysqld(_start+0x2e)[0x55de469c40ee]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /dev/shm/var/1/mysqld.1/data
      Resource Limits:
      Limit                     Soft Limit           Hard Limit           Units     
      Max cpu time              unlimited            unlimited            seconds   
      Max file size             unlimited            unlimited            bytes     
      Max data size             unlimited            unlimited            bytes     
      Max stack size            8388608              unlimited            bytes     
      Max core file size        unlimited            unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             23589                23589                processes 
      Max open files            1024                 1024                 files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       23589                23589                signals   
      Max msgqueue size         819200               819200               bytes     
      Max nice priority         0                    0                    
      Max realtime priority     0                    0                    
      Max realtime timeout      unlimited            unlimited            us        
      Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
       
      ----------SERVER LOG END-------------
       
       - skipping '/dev/shm/var/1/log/galera_sr.GCF-597-innodb/'
       
      Retrying test galera_sr.GCF-597, attempt(2/3)...
       
      worker[1] > Restart  - not started
      worker[1] > Restart  - not started
      ***Warnings generated in error logs during shutdown after running tests: galera_sr.GCF-572 galera_sr.GCF-597 galera_sr.GCF-1008 galera_sr.GCF-561 galera_sr.GCF-1018 galera_sr.GCF-585 galera_sr.GCF-580 galera_sr.GCF-571 galera_sr.GCF-1051
       
      Attempting backtrace. You can use the following information to find out
      Attempting backtrace. You can use the following information to find out
       
      galera_sr.GCF-597 'innodb'               w1 [ retry-pass ]   2151
       
      Retrying test galera_sr.GCF-597, attempt(3/3)...
       
      galera_sr.GCF-597 'innodb'               w1 [ retry-pass ]   2092
      

      Server logs.

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            stepan.patryshev Stepan Patryshev (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.