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

Crash on galera.MW-328E

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.2(EOL)
    • N/A
    • Galera, Tests
    • None

    Description

      • Latest 10.2 with release build using commit c13519312bebc3104510d84157894b7477c09a78
      • Galera library with debug build using commit commit 4398bfc4906c6e153971bfd210cafdb11693c4a0
      • ./mtr --suite=galera --big-test --force --parallel=auto

      CURRENT_TEST: galera.MW-328E
      2019-10-29 11:09:08 140548863358720 [Note] /home/jan/mysql/10.2-sst/sql/mysqld (initiated by: root[root] @ localhost [127.0.0.1]): Normal shutdown
      2019-10-29 11:09:08 140548863358720 [Note] WSREP: Stop replication
      2019-10-29 11:09:08 140548863358720 [Note] WSREP: Closing send monitor...
      2019-10-29 11:09:08 140548863358720 [Note] WSREP: Closed send monitor.
      2019-10-29 11:09:08 140548863358720 [Note] WSREP: gcomm: terminating thread
      2019-10-29 11:09:08 140548863358720 [Note] WSREP: gcomm: joining thread
      2019-10-29 11:09:08 140548863358720 [Note] WSREP: gcomm: closing backend
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: forgetting a8e9a930 (tcp://127.0.0.1:16145)
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: Node a8e5305a state prim
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: view(view_id(PRIM,a8e5305a,5) memb {
      	a8e5305a,0
      } joined {
      } left {
      } partitioned {
      	a8e9a930,0
      })
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: save pc into disk
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: forgetting a8e9a930 (tcp://127.0.0.1:16145)
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: view((empty))
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: gcomm: closed
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 1
      2019-10-29 11:09:09 140548887267072 [Warning] WSREP: 0x55579723a468 down context(s) not set
      2019-10-29 11:09:09 140548887267072 [Warning] WSREP: Failed to send state UUID: -107 (Transport endpoint is not connected)
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: Received self-leave message.
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: Flow-control interval: [0, 0]
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: Trying to continue unpaused monitor
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: Received SELF-LEAVE. Closing connection.
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: Shifting SYNCED -> CLOSED (TO: 141)
      2019-10-29 11:09:09 140548887267072 [Note] WSREP: RECV thread exiting 0: Success
      2019-10-29 11:09:09 140548983879424 [Note] WSREP: New cluster view: global state: a8e5f569-fa2b-11e9-a2b9-a38e5593e461:141, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version 3
      2019-10-29 11:09:09 140548983879424 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: recv_thread() joined.
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: Closing replication queue.
      2019-10-29 11:09:09 140548863358720 [Note] WSREP: Closing slave action queue.
      2019-10-29 11:09:09 140548983879424 [Note] WSREP: applier thread exiting (code:0)
      2019-10-29 11:09:11 140548984186624 [Note] WSREP: rollbacker thread exiting
      2019-10-29 11:09:11 140548863358720 [Note] Event Scheduler: Purging the queue. 0 events
      2019-10-29 11:09:11 140548073568000 [Note] InnoDB: FTS optimize thread exiting.
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: dtor state: CLOSED
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: mon: entered 141 oooe fraction 0 oool fraction 0
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: mon: entered 141 oooe fraction 0 oool fraction 0
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: mon: entered 164 oooe fraction 0 oool fraction 0
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: cert index usage at exit 0
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: cert trx map usage at exit 109
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: deps set usage at exit 0
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: avg deps dist 1.06383
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: avg cert interval 0.0141844
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: cert index size 7
      2019-10-29 11:09:11 140549000972032 [Note] WSREP: Service thread queue flushed.
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: wsdb trx map usage 1 conn query map usage 0
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: MemPool(LocalTrxHandle): hit ratio: 0.735294, misses: 9, in use: 1, in pool: 8
      2019-10-29 11:09:11 140548863358720 [Note] WSREP: trx map:
      1612 source: a8e5305a-fa2b-11e9-9f7f-8791de2d41e3 version: 4 local: 1 state: EXECUTING flags: 0 conn_id: -1 trx_id: 1612 seqnos (l: -1, g: -1, s: -1, d: -1, ts: 1572340145799802915)
      conn query map:
       
       
      mysqld: galera/src/wsdb.cpp:54: galera::Wsdb::~Wsdb(): Assertion `trx_map_.size() == 0' failed.
      191029 11:09:11 [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.2.28-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=4
      max_threads=153
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63019 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
      /home/jan/mysql/10.2-sst/sql/mysqld(my_print_stacktrace+0x29)[0x5557957bf119]
      mysys/stacktrace.c:268(my_print_stacktrace)[0x5557953401bb]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x13f40)[0x7fd42326bf40]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fd422d64ed7]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7fd422d46535]
      /lib/x86_64-linux-gnu/libc.so.6(+0x2540f)[0x7fd422d4640f]
      /lib/x86_64-linux-gnu/libc.so.6(+0x35012)[0x7fd422d56012]
      src/wsdb.cpp:55(galera::Wsdb::~Wsdb())[0x7fd41e170dea]
      src/replicator_smm.cpp:259(galera::ReplicatorSMM::~ReplicatorSMM())[0x7fd41e1aa1ce]
      src/replicator_smm.cpp:279(galera::ReplicatorSMM::~ReplicatorSMM())[0x7fd41e1aa5d9]
      src/wsrep_provider.cpp:104(galera_tear_down)[0x7fd41e1c7d70]
      /home/jan/mysql/10.2-sst/sql/mysqld(wsrep_unload+0x17)[0x55579582a5e7]
      wsrep/wsrep_loader.c:221(wsrep_unload)[0x5557952da6e7]
      sql/wsrep_mysqld.cc:871(wsrep_deinit(bool))[0x55579513175a]
      sql/mysqld.cc:2020(kill_server(void*) [clone .constprop.88])[0x55579513186e]
      sql/mysqld.cc:2051(kill_server_thread)[0x555795784fff]
      nptl/pthread_create.c:487(start_thread)[0x7fd423261182]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fd422e3eb1f]
      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 /home/jan/mysql/10.2-sst/mysql-test/var/8/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             127852               127852               processes 
      Max open files            1024                 1024                 files     
      Max locked memory         67108864             67108864             bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       127852               127852               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 %s %c %d %P
      
      

      Attachments

        Issue Links

          Activity

            People

              seppo Seppo Jaakola
              jplindst Jan Lindström (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.