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

Troubles with DB

    XMLWordPrintable

Details

    Description

      mariadb stopped with log:

      [root@papatuning ~]# systemctl status mariadb.service -l
      mariadb.service - MariaDB database server
      Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
      Active: inactive (dead) since Sun 2024-08-18 08:48:40 UTC; 2h 5min ago
      Process: 1100 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS)
      Process: 1099 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
      Process: 989 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
      Main PID: 1099 (code=exited, status=0/SUCCESS)
      *
      after restart:*

      240818 8:48:39 [Note] /usr/libexec/mysqld (mysqld 5.5.65-MariaDB) starting as process 32336 ...
      240818 8:48:39 InnoDB: The InnoDB memory heap is disabled
      240818 8:48:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
      240818 8:48:39 InnoDB: Compressed tables use zlib 1.2.7
      240818 8:48:39 InnoDB: Using Linux native AIO
      240818 8:48:39 InnoDB: Initializing buffer pool, size = 852.0M
      240818 8:48:39 InnoDB: Completed initialization of buffer pool
      240818 8:48:39 InnoDB: highest supported file format is Barracuda.
      240818 8:48:39 InnoDB: Starting crash recovery from checkpoint LSN=108373520862
      InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      240818 8:48:39 InnoDB: Starting final batch to recover 3799 pages from redo log
      240818 8:48:40 InnoDB: Waiting for the background threads to start
      240818 8:48:40 InnoDB: Assertion failure in thread 140386844538624 in file btr0btr.c line 3383
      InnoDB: Failing assertion: btr_page_get_prev(merge_page, mtr) == buf_block_get_page_no(block)
      InnoDB: We intentionally generate a memory trap.
      InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      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.
      240818 8:48:40 [ERROR] mysqld got signal 6 ;

      how to fix?

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              iSv Ilya Sviridenko
              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.