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

Today one of our production servers stopped and it wrote in the error.log to create a Jira ticket here

    XMLWordPrintable

Details

    • Not for Release Notes

    Description

      The server suddenly stopped, here is the error.logs from that point of time. For a quick and dirty solution we added force_recovery = 1 and it started. Can't find any problems since then when it died, gonna check if we have any corrupted tables or data.

      2025-11-27 14:33:15 9470442 [Warning] Aborted connection 9470442 to db: 'efood' user: 'efood' host: 'localhost' (Got an error reading communication packets)
      2025-12-10 11:10:55 14685197 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1
      2025-12-10 11:10:55 14685197 [ERROR] InnoDB: File './ibdata1' is corrupted
      2025-12-10 11:10:55 0x7f1a10713640 InnoDB: Assertion failure in file ./storage/innobase/trx/trx0purge.cc line 268
      InnoDB: Failing assertion: undo_page
      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 mariadbd startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      251210 11:10:55 [ERROR] mysqld got signal 6 ;
      Sorry, we probably made a mistake, and this is a bug.

      Your assistance in bug reporting will enable us to fix this for the next release.
      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.11.7-MariaDB-1:10.11.7+maria~ubu2204 source revision: 87e13722a95af5d9378d990caf48cb6874439347
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=23
      max_threads=2172
      thread_count=15
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4915333 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x7f19580057a8
      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 = 0x7f1a10712c38 thread_stack 0x49000
      2025-12-10 11:10:55 0x7f1a1067d640 InnoDB: Assertion failure in file ./storage/innobase/buf/buf0lru.cc line 281
      InnoDB: Failing assertion: !block->page.in_file()
      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 mariadbd startup, there may be
      InnoDB: corruption in the InnoDB tablespace. Please refer to
      InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      InnoDB: about forcing recovery.
      2025-12-10 11:12:42 0 [Note] Starting MariaDB 10.11.7-MariaDB-1:10.11.7+maria~ubu2204 source revision 87e13722a95af5d9378d990caf48cb6874439347 as process 3137564
      2025-12-10 11:12:42 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2025-12-10 11:12:42 0 [Note] InnoDB: Number of transaction pools: 1
      2025-12-10 11:12:42 0 [Note] InnoDB: Using generic crc32 instructions
      2025-12-10 11:12:42 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
      2025-12-10 11:12:42 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-12-10 11:12:42 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
      2025-12-10 11:12:42 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=127543533107
      2025-12-10 11:12:42 0 [ERROR] InnoDB: Corrupted page identifier at 127551091090; set innodb_force_recovery=1 to ignore the record.
      2025-12-10 11:12:42 0 [Note] InnoDB: End of log at LSN=127551091090
      2025-12-10 11:12:42 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
      2025-12-10 11:12:42 0 [Note] InnoDB: Starting shutdown...
      2025-12-10 11:12:42 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      2025-12-10 11:12:42 0 [Note] Plugin 'FEEDBACK' is disabled.
      2025-12-10 11:12:42 0 [ERROR] Unknown/unsupported storage engine: InnoDB
      2025-12-10 11:12:42 0 [ERROR] Aborting

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              diffdev Different Dev
              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.