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

InnoDB: Server crashed, waited at ha_innodb.cc line 10727

    XMLWordPrintable

    Details

      Description

      It's write heave database.
      Server crashed with error:

      InnoDB: Error: semaphore wait has lasted > 600 seconds
      InnoDB: We intentionally crash the server, because it appears to be hung.
      201021 11:22:35  InnoDB: Assertion failure in thread 140591196018432 in file srv0srv.c line 2917
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
      InnoDB: If you get repeated assertion failures or crashes, even
      InnoDB: immediately after the mysqld startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
      InnoDB: about forcing recovery.
      201021 11:22:35 [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 http://kb.askmonty.org/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: 5.5.31-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=53
      max_threads=102
      thread_count=34
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 354822 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x0
      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 0x48000
      mysys/stacktrace.c:247(my_print_stacktrace)[0x9ed87b]
      sql/signal_handler.cc:153(handle_fatal_signal)[0x6b8828]
      ??:0(??)[0x7ff83738a0a0]
      ??:0(??)[0x7ff836027125]
      ??:0(??)[0x7ff83602a3a0]
      srv/srv0srv.c:2974(srv_error_monitor_thread)[0x810e33]
      ??:0(??)[0x7ff837381b50]
      ??:0(??)[0x7ff8360d2fbd]
      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.
      201021 11:26:06 mysqld_safe Number of processes running now: 0
      201021 11:26:06 mysqld_safe mysqld restarted
      201021 11:26:06 InnoDB: The InnoDB memory heap is disabled
      201021 11:26:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins
      201021 11:26:06 InnoDB: Compressed tables use zlib 1.2.7
      201021 11:26:07 InnoDB: Initializing buffer pool, size = 100.0G
      201021 11:26:12 InnoDB: Completed initialization of buffer pool
      201021 11:26:12 InnoDB: highest supported file format is Barracuda.
      InnoDB: Log scan progressed past the checkpoint lsn 536256807427273
      201021 11:26:13  InnoDB: Database was not shut down normally!
      InnoDB: Starting crash recovery.
      

      Error logs are attached.
      Server version: 5.5.31-MariaDB (couldn't find this version in the list while creating this bug)

        Attachments

          Activity

            People

            Assignee:
            danblack Daniel Black
            Reporter:
            dhillonarvi@gmail.com Arvinder Singh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration