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

crash after sst (rsync) with enable TLS in 10.6.20 on ubuntu 22.04

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.6.20
    • None
    • Galera SST, SSL
    • Ubuntu 22.04

    Description

      With TLS enable and MariaDB 10.6.20 on Ubuntu 22.04

      • * after SST in rsync mode (wsrep_sst_method=rsync), MariaDB start and crash :

      Error log :

      2025-03-24 14:19:41 3 [Note] WSREP: SST received
      2025-03-24 14:19:41 3 [Note] WSREP: Server status change joiner -> initializing
      2025-03-24 14:19:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
      2025-03-24 14:19:41 0 [Note] InnoDB: Number of pools: 1
      2025-03-24 14:19:41 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
      2025-03-24 14:19:41 0 [Note] InnoDB: Initializing buffer pool, total size = 2147483648, chunk size = 134217728
      2025-03-24 14:19:41 0 [Note] InnoDB: Completed initialization of buffer pool
      2025-03-24 14:19:41 0 [Note] InnoDB: Setting log file /myqdata/myserver01/log/innodb/ib_logfile101 size to 235929600 bytes
      2025-03-24 14:19:41 0 [Note] InnoDB: Renaming log file /myqdata/myserver01/log/innodb/ib_logfile101 to /myqdata/myserver01/log/innodb/ib_logfile0
      2025-03-24 14:19:41 0 [Note] InnoDB: New log file created, LSN=337378
      2025-03-24 14:19:41 0 [ERROR] InnoDB: Page [page id: space=0, page number=0] log sequence number 359327 is in the future! Current system log sequence number 337432.
      2025-03-24 14:19:41 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the ib_logfile0. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
      2025-03-24 14:19:41 0 [ERROR] InnoDB: Failed to read page 0 from file '/myqdata/myserver01/data/ibdata1': Data structure corruption
      2025-03-24 14:19:41 0 [Note] InnoDB: Page dump (16384 bytes):

      2025-03-24 14:19:41 0 [Note] InnoDB: End of page dump
      2025-03-24 14:19:41 0 [ERROR] InnoDB: File '/myqdata/myserver01/data/ibdata1' is corrupted
      2025-03-24 14:19:41 0 [Note] InnoDB: Retry with innodb_force_recovery=5
      2025-03-24 14:19:41 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
      2025-03-24 14:19:41 0 [Note] InnoDB: Starting shutdown...
      2025-03-24 14:19:41 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
      2025-03-24 14:19:41 0 [Note] Plugin 'FEEDBACK' is disabled.
      250324 14:19:41 server_audit: MariaDB Audit Plugin version 1.4.14 STARTED.
      250324 14:19:41 server_audit: logging started to the file /myqdata/myserver01/log/log/server_audit.log.
      2025-03-24 14:19:41 0 [ERROR] Unknown/unsupported storage engine: InnoDB
      2025-03-24 14:19:41 0 [ERROR] Aborting
      2025-03-24 14:19:41 3 [ERROR] WSREP: sst_received failed: State wait was interrupted
      2025-03-24 14:19:41 1 [ERROR] WSREP: Application received wrong state:
      Received: 00000000-0000-0000-0000-000000000000
      Required: d5e26221-08a3-11f0-a443-9e9bc759d947
      2025-03-24 14:19:41 1 [ERROR] WSREP: Application state transfer failed. This is unrecoverable condition, restart required.

      With mariabackup for SST, it's OK

      Attachments

        Activity

          No workflow transitions have been executed yet.

          People

            Unassigned Unassigned
            laurent.dangeard@orange.com Laurent Dangeard
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.