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

galera_sr.mysql-wsrep-features#8 test failure

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Galera, Server
    • None

    Description


      galera_sr.mysql-wsrep-features#8 'innodb' [ fail ]  timeout after 900 seconds
              Test ended at 2023-11-11 00:39:59
       
      Test case timeout after 900 seconds
       
      == /home/panda/mariadb-10.4/build/mysql-test/var/log/mysql-wsrep-features#8.log == 
      connection node_2;
      connection node_1;
      SET SESSION wsrep_trx_fragment_size = 1;
      CREATE TABLE ten (f1 INTEGER) ENGINE=InnoDB;
      INSERT INTO ten VALUES (1),(2),(3),(4),(5),(6),(7),(8),(9),(10);
      connection node_1;
      CREATE TABLE t1 (f1 INT PRIMARY KEY AUTO_INCREMENT, f2 VARCHAR(100), FULLTEXT (f2)) ENGINE=InnoDB;
      connection node_2;
      SELECT COUNT(*) = 13 FROM INFORMATION_SCHEMA.INNODB_SYS_TABLES WHERE name LIKE 'test/%';
      COUNT(*) = 13
      1
      connection node_1;
      INSERT INTO t1 (f2) SELECT 'foobarbaz' FROM ten AS a1, ten AS a2, ten AS a3, ten AS a4;
       
       == /home/panda/mariadb-10.4/build/mysql-test/var/tmp/analyze-timeout-mysqld.2.err ==
      mysqltest: Could not open connection 'default' after 500 attempts: 2002 Can't connect to local MySQL server through socket '/home/panda/mariadb-10.4/build/mysql-test/var/tmp/mysqld.2.sock' (111)
       
       == /home/panda/mariadb-10.4/build/mysql-test/var/tmp/analyze-timeout-mysqld.1.err ==
      mysqltest: Could not open connection 'default' after 500 attempts: 2002 Can't connect to local MySQL server through socket '/home/panda/mariadb-10.4/build/mysql-test/var/tmp/mysqld.1.sock' (111)
       
       
       - saving '/home/panda/mariadb-10.4/build/mysql-test/var/log/galera_sr.mysql-wsrep-features#8-innodb/' to '/home/panda/mariadb-10.4/build/mysql-test/var/log/galera_sr.mysql-wsrep-features#8-innodb/'
      ***Warnings generated in error logs during shutdown after running tests: galera_sr.mysql-wsrep-features#8
       
      Attempting backtrace. You can use the following information to find out
      Attempting backtrace. You can use the following information to find out

      Fregment with stack trace from error log:

      2023-11-11  0:23:58 2 [Note] WSREP: Server status change joined -> synced
      2023-11-11  0:23:58 2 [Note] WSREP: Synchronized with group, ready for connections
      2023-11-11  0:23:58 2 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2023-11-11  0:39:04 16 [Warning] Aborted connection 16 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      231111  0:39:06 [ERROR] mysqld got signal 6 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      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.32-MariaDB-debug-log source revision: 1b2f8bafb02cbff9c9e42370f854cc2c3cc4eef2
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      thread_count=9
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63665 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
      2023-11-11  0:39:06 0 [Note] WSREP: (35c19bb9-ba3f, 'tcp://0.0.0.0:16025') turning message relay requesting on, nonlive peers: tcp://127.0.0.1:16022 
      mysys/stacktrace.c:174(my_print_stacktrace)[0x5582bad7024f]
      sql/signal_handler.cc:235(handle_fatal_signal)[0x5582ba42365b]
      libc_sigaction.c:0(__restore_rt)[0x7efe835ed520]
      linux/poll.c:29(__GI___poll)[0x7efe836c3dbf]
      sql/mysqld.cc:6518(handle_connections_sockets())[0x5582b9f675e6]
      sql/mysqld.cc:5956(mysqld_main(int, char**))[0x5582b9f66792]
      sql/main.cc:25(main)[0x5582b9f59cad]
      nptl/libc_start_call_main.h:58(__libc_start_call_main)[0x7efe835d4d90]
      csu/libc-start.c:128(call_init)[0x7efe835d4e40]
      /home/panda/mariadb-10.4/build/sql/mysqld(_start+0x25)[0x5582b9f59bc5]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
      information that should help you find out what is causing the crash.
      Writing a core file...
      Working directory at /home/panda/mariadb-10.4/build/mysql-test/var/mysqld.2/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             63457                63457                processes 
      Max open files            1024                 1024                 files     
      Max locked memory         2094301184           2094301184           bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       63457                63457                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/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E

      Attachments

        Activity

          People

            Unassigned Unassigned
            sysprg Julius Goryavsky
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.