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

10.5.4 mariadbd crashes during shutdown




      2020-06-28  0:45:33 0 [Note] InnoDB: Buffer pool(s) load completed at 200628  0:45:33
      2020-06-28  0:45:46 0 [Note] /data1/app/mariadb/bin/mariadbd (initiated by: unknown): Normal shutdown
      2020-06-28  0:45:46 0 [Note] Event Scheduler: Purging the queue. 0 events
      2020-06-28  0:45:46 10 [Note] Slave SQL thread exiting, replication stopped in log 'mysql-bin.065769' at position 256; GTID position '0-100065-8777861145'
      Status information:
      Current dir: /data1/mysql/mysql-instance/data/
      Running threads: 2  Cached threads: 2  Stack size: 299008
      Key caches:
      Buffer_size:      33554432
      Block_size:           1024
      Division_limit:        100
      Age_threshold:         300
      Partitions:              0
      blocks used:             0
      not flushed:             0
      w_requests:              0
      writes:                  0
      r_requests:              0
      reads:                   0
      handler status:
      read_key:         4531
      read_next:        1023
      read_rnd          1026
      read_first:          3
      write:            5218
      delete               5
      update:           3764
      Table status:
      Opened tables:         46
      Open tables:           40
      Open files:            35
      Open streams:           4
      Alarm status:
      Active alarms:   0
      Max used alarms: 0
      Next alarm time: 0
      Memory status:
      Non-mmapped space allocated from system: 174833664
      Number of free chunks:                   538
      Number of fastbin blocks:                9
      Number of mmapped regions:               15
      Space in mmapped regions:                171819008
      Maximum total allocated space:           0
      Space available in freed fastbin blocks: 624
      Total allocated space:                   159597856
      Total free space:                        15235808
      Top-most, releasable space:              200192
      Estimated memory (with thread stack):    347250688
      Global memory allocated by server:       34358400
      Memory allocated by threads:             118384
      Events status:
      LLA = Last Locked At  LUA = Last Unlocked At
      WOC = Waiting On Condition  DL = Data Locked
      The Event Scheduler is disabled
      2020-06-28  0:45:46 9 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.065769', position 74476178; GTID position 0-100065-8777871952
      2020-06-28  0:45:46 0 [Note] InnoDB: FTS optimize thread exiting.
      200628  0:45:46 [ERROR] mysqld got signal 11 ;
      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.4-MariaDB-log
      2020-06-28  0:45:46 0 [Note] InnoDB: Starting shutdown...
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 65684313 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...
      2020-06-28  0:45:46 0 [Note] InnoDB: Dumping buffer pool(s) to /data1/mysql/mysql-instance/data/ib_buffer_pool
      2020-06-28  0:45:46 0 [Note] InnoDB: Restricted to 128864 pages due to innodb_buf_pool_dump_pct=25
      stack_bottom = 0x0 thread_stack 0x49000
      2020-06-28  0:45:46 0 [Note] InnoDB: Buffer pool(s) dump completed at 200628  0:45:46
      2020-06-28  0:45:48 0 [Note] InnoDB: Shutdown completed; log sequence number 11724296462283; transaction id 16032419783
      2020-06-28  0:45:48 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
      2020-06-28  0:45:48 0 [Note] /data1/app/mariadb/bin/mariadbd: Shutdown complete
      sql/sql_reload.cc:351(reload_acl_and_cache(THD*, unsigned long long, TABLE_LIST*, int*))[0x556bf763fbad]
      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 /data1/mysql/mysql-instance/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        0                    unlimited            bytes
      Max resident set          unlimited            unlimited            bytes
      Max processes             257066               257066               processes
      Max open files            1024000              1024000              files
      Max locked memory         67108864             67108864             bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       257066               257066               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: core
      2020-06-28  0:48:54 0 [Note] InnoDB: Using Linux native AIO
      2020-06-28  0:48:54 0 [Note] InnoDB: Uses event mutexes


        Issue Links



              Unassigned Unassigned
              wxiaoguang Xiaoguang Wang
              0 Vote for this issue
              4 Start watching this issue



                Git Integration

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