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

mysql maridab server is crashing several times a day

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Won't Fix
    • 10.1(EOL)
    • N/A
    • OS = Ubuntu (Ubuntu 18.04.6 LTS)
      Service = mysql Ver 15.1 Distrib 10.1.48-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
      CPU = 4core
      Memory = 8GB
      Storage = 300GB

    Description

      2025-04-07  0:15:42 139752323562624 [ERROR] InnoDB: The OS said file flush did not succeed
      2025-04-07 00:15:42 7f1a9f9a3c80  InnoDB: Operating system error number 1 in a file operation.
      InnoDB: Error number 1 means 'Operation not permitted'.
      InnoDB: Some operating system error numbers are described at
      InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
       InnoDB: Operation flush to file /build/mariadb-10.1-CYSeUP/mariadb-10.1-10.1.48/storage/xtradb/os/os0file.cc and at line 2950
      2025-04-07  0:15:42 139752323562624 [ERROR] InnoDB: File (unknown): 'flush' returned OS error 201. Cannot continue operation
      250407  0:15:42 [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.1.48-MariaDB-0ubuntu0.18.04.1
      key_buffer_size=16777216
      read_buffer_size=131072
      max_used_connections=0
      max_threads=1002
      thread_count=0
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2217522 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)[0x5632229bb6ae]
      /usr/sbin/mysqld(handle_fatal_signal+0x53b)[0x563222581cfb]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f1a9e889980]
      linux/raise.c:51(__GI_raise)[0x7f1a9db19e87]
      stdlib/abort.c:81(__GI_abort)[0x7f1a9db1b7f1]
      /usr/sbin/mysqld(+0x836621)[0x563222820621]
      /usr/sbin/mysqld(+0x8378dd)[0x5632228218dd]
      /usr/sbin/mysqld(+0x95a9c3)[0x5632229449c3]
      /usr/sbin/mysqld(+0x95ab27)[0x563222944b27]
      /usr/sbin/mysqld(+0x9102fc)[0x5632228fa2fc]
      /usr/sbin/mysqld(+0x91766b)[0x56322290166b]
      /usr/sbin/mysqld(+0x81499d)[0x5632227fe99d]
      /usr/sbin/mysqld(+0x819758)[0x563222803758]
      /usr/sbin/mysqld(+0x8ab7eb)[0x5632228957eb]
      /usr/sbin/mysqld(+0x7e048e)[0x5632227ca48e]
      /usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x62)[0x563222584252]
      /usr/sbin/mysqld(+0x42a792)[0x563222414792]
      /usr/sbin/mysqld(_Z11plugin_initPiPPci+0x78a)[0x5632224156ba]
      /usr/sbin/mysqld(+0x3827e7)[0x56322236c7e7]
      /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x4aa)[0x563222371fda]
      csu/libc-start.c:344(__libc_start_main)[0x7f1a9dafcc87]
      /usr/sbin/mysqld(_start+0x2a)[0x56322236624a]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
      information that should help you find out what is causing the crash.
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
       
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: The InnoDB memory heap is disabled
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Using Linux native AIO
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Using SSE crc32 instructions
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Completed initialization of buffer pool
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Highest supported file format is Barracuda.
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Starting crash recovery from checkpoint LSN=15742883852
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      2025-04-07  0:15:48 140513607732352 [Note] InnoDB: Starting final batch to recover 10 pages from redo log
      2025-04-07  0:15:49 140513607732352 [Note] InnoDB: 128 rollback segment(s) are active.
      2025-04-07  0:15:49 140513607732352 [Note] InnoDB: Waiting for purge to start
      2025-04-07  0:15:49 140513607732352 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.49-89.0 started; log sequence number 15742890076
      2025-04-07  0:17:25 140513607732352 [Note] Plugin 'FEEDBACK' is disabled.
      2025-04-07  0:17:25 140512925316864 [Note] InnoDB: Dumping buffer pool(s) not yet started
      2025-04-07  0:17:25 140513607732352 [Note] Recovering after a crash using tc.log
      2025-04-07  0:17:25 140513607732352 [Note] Starting crash recovery...
      2025-04-07  0:17:25 140513607732352 [Note] Crash recovery finished.
      2025-04-07  0:17:25 140513607732352 [Note] Server socket created on IP: '0.0.0.0'.
      2025-04-07  0:17:25 140513607732352 [Note] /usr/sbin/mysqld: ready for connections.
      Version: '10.1.48-MariaDB-0ubuntu0.18.04.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Ubuntu 18.04

      Attachments

        Activity

          People

            Unassigned Unassigned
            technova Technova
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.