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

Cant launch MariaDB Server

    XMLWordPrintable

Details

    Description

      Writing a core file at C:\xampp\mysql\data
      Minidump written to C:\xampp\mysql\data\mysqld.dmp
      2024-02-26 19:16:59 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 21832
      2024-02-26 19:16:59 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
      2024-02-26 19:16:59 0 [Note] InnoDB: Uses event mutexes
      2024-02-26 19:16:59 0 [Note] InnoDB: Compressed tables use zlib 1.3
      2024-02-26 19:16:59 0 [Note] InnoDB: Number of pools: 1
      2024-02-26 19:16:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
      2024-02-26 19:16:59 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
      2024-02-26 19:16:59 0 [Note] InnoDB: Completed initialization of buffer pool
      2024-02-26 19:16:59 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=41621806
      2024-02-26 19:16:59 0 [Note] InnoDB: Starting final batch to recover 5 pages from redo log.
      2024-02-26 19:16:59 0 [ERROR] [FATAL] InnoDB: Trying to read page number 49153 in space 0, space name innodb_system, which is outside the tablespace bounds. Byte offset 0, len 16384Please check that the configuration matches the InnoDB system tablespace location (ibdata files)
      240226 19:16:59 [ERROR] mysqld got exception 0x80000003 ;
      Sorry, we probably made a mistake, and this is a bug.

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              ace01 Loic NITOUD
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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