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

Database not starting

    XMLWordPrintable

    Details

      Description

      Journalctl has told me to come here to submit a bug and here I am. I have tried to do a mysql dump of the databases that have been recently modified with innodb_force_recovery set to different values, but then the database goes away inmediately and wouldn't allow to run it.
      Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)" when trying to connect.

      I'm not a programmer so I'm not sure what kind of imformation you need or where to find it.

      journalctl -u mariadb -xe

      Nov 06 13:47:23  mariadbd[222737]: 2020-11-06 13:47:23 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace b>
      Nov 06 13:47:23  mariadbd[222737]: 2020-11-06 13:47:23 0x7ff3697fe700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.>
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: We intentionally generate a memory trap.
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: If you get repeated assertion failures or crashes, even
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: immediately after the mysqld startup, there may be
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: corruption in the InnoDB tablespace. Please refer to
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
      Nov 06 13:47:23  mariadbd[222737]: InnoDB: about forcing recovery.
      Nov 06 13:47:23  mariadbd[222737]: 2020-11-06 13:47:23 0 [ERROR] InnoDB: Page [page id: space=0, page number=445] log sequence number 81581802317 is>
      Nov 06 13:47:23  mariadbd[222737]: 2020-11-06 13:47:23 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace b>
      Nov 06 13:47:24  systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
      -- Subject: Unit process exited
      -- Defined-By: systemd
      -- Support: http://www.ubuntu.com/support
      --
      -- An ExecStart= process belonging to unit mariadb.service has exited.
      --
      -- The process' exit code is 'killed' and its exit status is 6.
      Nov 06 13:47:24  systemd[1]: mariadb.service: Failed with result 'signal'.
      -- Subject: Unit failed
      -- Defined-By: systemd
      -- Support: http://www.ubuntu.com/support
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              lbartolome Lucía
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration