Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4.16, 10.5.7
-
Ubuntu 20.04, php 7.4 and Maria DB 10.5.7
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
- duplicates
-
MDEV-24096 Server crash, InnoDB fatal error, Assertion `first_free <= srv_page_size - 8' failed in trx_undo_page_report_modify
- Closed
- is caused by
-
MDEV-23672 Assertion `v.v_indexes.empty()' failed in dict_table_t::instant_column
- Closed
- is duplicated by
-
MDEV-24162 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.5.7/storage/innobase/include/fut0lst.h line 127
- Closed