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

Mariadb (galera) node crashed with an error: [ERROR] [FATAL] InnoDB: fsync() returned 5

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Not a Bug
    • 10.4.11
    • N/A
    • N/A
    • DISTRIB_ID=Ubuntu
      DISTRIB_RELEASE=16.04
      DISTRIB_CODENAME=xenial
      DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"
      Linux 4.4.0-138-generic

    Description

      Hello Team,

      Mariadb Galera node crashed and we observed following errors in the log file.
      Storage is mounted via NFS: version is nfs4.

      Some variables:

      innodb_flush_log_at_trx_commit 2
      innodb_flush_method O_DIRECT
      innodb_flush_sync ON
      sync_binlog 0

      2020-03-16 7:33:19 0 [Note] WSREP: Created page /exstorage/database/mysql/galera/gcache.page.000011 of size 1770627216 bytes
      2020-03-16 7:33:20 0 [Note] WSREP: Deleted page /exstorage/database/mysql/galera/gcache.page.000010
      2020-03-16 7:33:22 0 [ERROR] [FATAL] InnoDB: fsync() returned 5
      200316 7:33:22 [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.11-MariaDB-1:10.4.11+maria~xenial-log
      key_buffer_size=65536
      read_buffer_size=2097152
      max_used_connections=67
      max_threads=102
      thread_count=83
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 629241 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 0x30000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55e8ec83e49e]
      /usr/sbin/mysqld(handle_fatal_signal+0x307)[0x55e8ec2d0037]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f3c8e297390]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f3c8cfb4428]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f3c8cfb602a]
      /usr/sbin/mysqld(+0xc25041)[0x55e8ec685041]
      /usr/sbin/mysqld(+0xb47888)[0x55e8ec5a7888]
      /usr/sbin/mysqld(+0xcc4858)[0x55e8ec724858]
      /usr/sbin/mysqld(+0xccbcb5)[0x55e8ec72bcb5]
      /usr/sbin/mysqld(+0xb2747d)[0x55e8ec58747d]
      /usr/sbin/mysqld(+0xb2a2d5)[0x55e8ec58a2d5]
      /usr/sbin/mysqld(+0xbdad7d)[0x55e8ec63ad7d]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f3c8e28d6ba]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f3c8d08641d]
      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 /exstorage/database/mysql/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 64024 64024 processes
      Max open files 16364 16364 files
      Max locked memory 65536 65536 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 64024 64024 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

      2020-03-16 7:33:35 0 [Note] WSREP: Loading provider /usr/lib/galera/libgalera_smm.so initial position: 240beee1-412e-11ea-85b1-2b4776f5dbba:1847879
      wsrep loader: [INFO] wsrep_load(): loading provider library '/usr/lib/galera/libgalera_smm.so'
      wsrep loader: [INFO] wsrep_load(): Galera 26.4.3(r4535) by Codership Oy <info@codership.com> loaded successfully.
      2020-03-16 7:33:35 0 [Note] WSREP: CRC-32C: using hardware acceleration.
      2020-03-16 7:33:35 0 [Note] WSREP: Found saved state: 240beee1-412e-11ea-85b1-2b4776f5dbba:-1, safe_to_bootstrap: 0
      2020-03-16 7:33:35 0 [Note] WSREP: GCache DEBUG: opened preamble:
      Version: 2
      UUID: 240beee1-412e-11ea-85b1-2b4776f5dbba
      Seqno: -1 - -1
      Offset: -1
      Synced: 0
      2020-03-16 7:33:35 0 [Note] WSREP: Recovering GCache ring buffer: version: 2, UUID: 240beee1-412e-11ea-85b1-2b4776f5dbba, offset: -1
      2020-03-16 7:33:35 0 [Note] WSREP: GCache::RingBuffer initial scan... 0.0% ( 0/3221225496 bytes) complete.

      Please excuse if I have missed providing any information and let me know about the same.

      Thank you.

      Nilesh

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              ngavali Nilesh
              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.