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

galera.galera_nopk_unicode MTR failed: timeout after 900 seconds

    XMLWordPrintable

Details

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

    Description

      galera.galera_nopk_unicode failed on bb: timeout after 900 seconds.

      stdio.log:

      10.5.2 d23c3e03ac4f6227df49f7674ca7572102ed8eb1

      galera.galera_nopk_unicode 'innodb'      w1 [ fail ]  timeout after 900 seconds
              Test ended at 2020-03-24 22:28:25
       
      Test case timeout after 900 seconds
       
      == /dev/shm/var/1/log/galera_nopk_unicode.log == 
      f1 VARCHAR(255),
      KEY (f1)
      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
      INSERT INTO t1 VALUES ('текст');
      connection node_2;
      SELECT f1 = 'текст' FROM t1;
      f1 = 'текст'
      1
      connection node_1;
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      UPDATE t1 SET f1 = 'текст2';
      connection node_2;
      SET AUTOCOMMIT=OFF;
      START TRANSACTION;
      UPDATE t1 SET f1 = 'текст3';
      connection node_1;
      COMMIT;
      connection node_2;
      COMMIT;
       
      The server [mysqld.1 - pid: 7669, winpid: 7669, exit: 256] crashed while running 'analyze-timeout'
      Server log from this test:
      ----------SERVER LOG START-----------
      200324 22:27:04 [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.2-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=3
      max_threads=153
      thread_count=5
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63593 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
      2020-03-24 22:27:04 83 [Warning] Aborted connection 83 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      2020-03-24 22:27:04 84 [Warning] Aborted connection 84 to db: 'test' user: 'root' host: 'localhost' (Got an error reading communication packets)
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56018c94f63e]
      /usr/sbin/mysqld(handle_fatal_signal+0x485)[0x56018c380495]
      2020-03-24 22:27:15 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.62393S), skipping check
      2020-03-24 22:27:16 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') connection to peer 53ed5b2b-a0c8 with addr tcp://127.0.0.1:16025 timed out, no messages seen in PT3S, socket stats: rtt: 32 rttvar: 15 rto: 201000 lost: 0 last_data_recv: 3327 cwnd: 10 last_queued_since: 1135882886 last_delivered_since: 3327197388 send_queue_length: 2 send_queue_bytes: 108 segment: 0 messages: 2
      2020-03-24 22:27:16 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') turning message relay requesting on, nonlive peers: tcp://127.0.0.1:16025 
      2020-03-24 22:27:18 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') reconnecting to 53ed5b2b-a0c8 (tcp://127.0.0.1:16025), attempt 0
      2020-03-24 22:27:18 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.19929S), skipping check
      2020-03-24 22:27:18 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') connection established to 53ed5b2b-a0c8 tcp://127.0.0.1:16025
      2020-03-24 22:27:22 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') turning message relay requesting off
      2020-03-24 22:27:23 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.66605S), skipping check
      2020-03-24 22:27:24 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.52887S), skipping check
      2020-03-24 22:27:26 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.84901S), skipping check
      2020-03-24 22:27:32 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.63565S), skipping check
      2020-03-24 22:27:33 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.95948S), skipping check
      2020-03-24 22:27:34 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') turning message relay requesting on, nonlive peers: tcp://127.0.0.1:16025 
      2020-03-24 22:27:35 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') connection established to 53ed5b2b-a0c8 tcp://127.0.0.1:16025
      2020-03-24 22:27:40 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') turning message relay requesting off
      2020-03-24 22:27:40 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT2.28477S), skipping check
      2020-03-24 22:27:40 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') connection to peer 53ed5b2b-a0c8 with addr tcp://127.0.0.1:16025 timed out, no messages seen in PT3S, socket stats: rtt: 4619 rttvar: 9117 rto: 205000 lost: 0 last_data_recv: 3191 cwnd: 10 last_queued_since: 720669332 last_delivered_since: 3191066191 send_queue_length: 2 send_queue_bytes: 108 segment: 0 messages: 2
      2020-03-24 22:27:40 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') turning message relay requesting on, nonlive peers: tcp://127.0.0.1:16025 
      2020-03-24 22:27:42 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') reconnecting to 53ed5b2b-a0c8 (tcp://127.0.0.1:16025), attempt 0
      2020-03-24 22:27:44 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.80236S), skipping check
      2020-03-24 22:27:45 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') connection established to 53ed5b2b-a0c8 tcp://127.0.0.1:16025
      2020-03-24 22:27:45 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.93608S), skipping check
      2020-03-24 22:27:49 0 [Note] WSREP: (53b59c10-9b56, 'tcp://0.0.0.0:16022') turning message relay requesting off
      2020-03-24 22:27:52 0 [Warning] WSREP: last inactive check more than PT1.5S ago (PT1.66325S), skipping check
      /lib64/libpthread.so.0(+0x14b20)[0x7fb447c6bb20]
      :0(__GI___poll)[0x7fb4472dea1f]
      /usr/sbin/mysqld(_Z26handle_connections_socketsv+0x22f)[0x56018c0bbacf]
      /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0xc6b)[0x56018c0bcaab]
      ??:0(__libc_start_main)[0x7fb44720f1a3]
      /usr/sbin/mysqld(_start+0x2e)[0x56018c0b0ace]
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html 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             23626                23626                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       23626                23626                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-------------
       
       - saving '/dev/shm/var/1/log/galera.galera_nopk_unicode-innodb/' to '/dev/shm/var/log/galera.galera_nopk_unicode-innodb/'
       
      Retrying test galera.galera_nopk_unicode, attempt(2/3)...
       
      worker[1] > Restart  - not started
      worker[1] > Restart  - not started
      ***Warnings generated in error logs during shutdown after running tests: galera.galera_mdev_10812 galera.galera_myisam_autocommit galera.galera_kill_smallchanges galera.galera_nopk_large_varchar galera.galera_lock_table galera.galera_nopk_bit galera.galera_nopk_blob galera.galera_multirow_rollback galera.galera_kill_ddl galera.galera_myisam_transactions galera.galera_nopk_unicode galera.galera_multi_database galera.galera_many_indexes
       
      Attempting backtrace. You can use the following information to find out
      Attempting backtrace. You can use the following information to find out
       
      galera.galera_nopk_unicode 'innodb'      w1 [ retry-pass ]   2037
       
      Retrying test galera.galera_nopk_unicode, attempt(3/3)...
      
      

      Attachments

        Activity

          People

            stepan.patryshev Stepan Patryshev (Inactive)
            stepan.patryshev Stepan Patryshev (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.