[MDEV-24155] Database not starting Created: 2020-11-06  Updated: 2021-08-19  Resolved: 2020-11-09

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4.16, 10.5.7
Fix Version/s: 10.4.17, 10.5.8

Type: Bug Priority: Major
Reporter: Lucía Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: corruption, socket, startup
Environment:

Ubuntu 20.04, php 7.4 and Maria DB 10.5.7

Issue Links:
Duplicate
duplicates MDEV-24096 Server crash, InnoDB fatal error, Ass... Closed
is duplicated by MDEV-24162 InnoDB: Assertion failure in file /ho... Closed
Problem/Incident
is caused by MDEV-23672 Assertion `v.v_indexes.empty()' faile... Closed

 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



 Comments   
Comment by Marko Mäkelä [ 2020-11-06 ]

lbartolome, in which version of MariaDB was the database originally created?

If you are using unique indexes on BLOB columns or indexed virtual columns, it is possible that your database was corrupted as explained in MDEV-24096.

Comment by Marko Mäkelä [ 2020-11-06 ]

According to a recent comment in MDEV-13689, this kind of a crash should indeed be the consequence of MDEV-23672, which can cause any page to be corrupted in the InnoDB buffer pool. It will be fixed in MDEV-24096.

Comment by Lucía [ 2020-11-06 ]

Not sure whether it was 10.4. or 10.5.x

It was installed in August from the mariadb repository.

And I disabled the indexes in the biggest database (>5 Gb) since the database was growing too much. I'm using sphinx instead.

Comment by Lucía [ 2020-11-07 ]

For what is worth, I uninstalled and reinstall everything. I had to apt purge and then -rm -rf for the reinstallation to work.

Comment by Lucía [ 2020-11-07 ]

Not sure whether this is related to the possible bug or it's my server having hardware problems or overload (it's on a shared VPS). The database has restarte itself twice.
Nov 07 14:21:22 mariadbd[503438]: 2020-11-07 14:21:22 0 [Note] InnoDB: Starting final batch to recover 1464 pages from redo log.
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: 128 rollback segments are active.
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full;>
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: 10.5.7 started; log sequence number 9692056005; transaction id 58184
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] Server socket created on IP: '0.0.0.0'.
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] Reading of all Master_info entries succeeded
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] Added new Master_info '' to hash table
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] /usr/sbin/mariadbd: ready for connections.
Nov 07 14:21:23 mariadbd[503438]: Version: '10.5.7-MariaDB-1:10.5.7+maria~focal' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org bi>
Nov 07 14:21:23 systemd[1]: Started MariaDB 10.5.7 database server.
– Subject: A start job for unit mariadb.service has finished successfully
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- A start job for unit mariadb.service has finished successfully.
–
-- The job identifier is 298592.
Nov 07 14:21:23 /etc/mysql/debian-start[503458]: Upgrading MySQL tables if necessary.
Nov 07 14:21:23 mariadbd[503438]: 2020-11-07 14:21:23 0 [Note] InnoDB: Buffer pool(s) load completed at 201107 14:21:23
Nov 07 14:21:23 /etc/mysql/debian-start[503461]: Looking for 'mysql' as: /usr/bin/mysql
Nov 07 14:21:23 /etc/mysql/debian-start[503461]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Nov 07 14:21:23 /etc/mysql/debian-start[503461]: This installation of MariaDB is already upgraded to 10.5.7-MariaDB, use --force if you still n>
Nov 07 14:21:23 /etc/mysql/debian-start[503473]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
Nov 07 15:08:22 mariadbd[503438]: 2020-11-07 15:08:22 5889 [Warning] Aborted connection 5889 to db: 'xxxx' user: 'xxxxx' host: '>
Nov 07 15:17:51 systemd[1]: mariadb.service: Main process exited, code=killed, status=9/KILL
– 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 9.
Nov 07 15:17:51 systemd[1]: mariadb.service: Failed with result 'signal'.
– Subject: Unit failed
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- The unit mariadb.service has entered the 'failed' state with result 'signal'.
Nov 07 15:17:57 systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 2.
– Subject: Automatic restarting of a unit has been scheduled
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- Automatic restarting of the unit mariadb.service has been scheduled, as the result for
– the configured Restart= setting for the unit.
Nov 07 15:17:57 systemd[1]: Stopped MariaDB 10.5.7 database server.
– Subject: A stop job for unit mariadb.service has finished
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- A stop job for unit mariadb.service has finished.
–
-- The job identifier is 298880 and the job result is done.
Nov 07 15:17:57 systemd[1]: Starting MariaDB 10.5.7 database server...
– Subject: A start job for unit mariadb.service has begun execution
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- A start job for unit mariadb.service has begun execution.
–
-- The job identifier is 298880.
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.7-MariaDB-1:10.5.7+maria~focal) starting as proc>
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Warning] Could not increase number of max_open_files to more than 65535 (request: 1313>
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Using Linux native AIO
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Uses event mutexes
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Number of pools: 1
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Initializing buffer pool, total size = 536870912, chunk size = 134217728
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: Completed initialization of buffer pool
Nov 07 15:17:57 mariadbd[506552]: 2020-11-07 15:17:57 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority>
Nov 07 15:17:58 mariadbd[506552]: 2020-11-07 15:17:58 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=9692057132,9692057132
Nov 07 15:17:58 mariadbd[506552]: 2020-11-07 15:17:58 0 [Note] InnoDB: Starting final batch to recover 1892 pages from redo log.
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: 128 rollback segments are active.
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full;>
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: 10.5.7 started; log sequence number 9703466797; transaction id 86926
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] Plugin 'FEEDBACK' is disabled.
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] Server socket created on IP: '0.0.0.0'.
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] Reading of all Master_info entries succeeded
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] Added new Master_info '' to hash table
Nov 07 15:17:59 mariadbd[506552]: 2020-11-07 15:17:59 0 [Note] /usr/sbin/mariadbd: ready for connections.
Nov 07 15:17:59 mariadbd[506552]: Version: '10.5.7-MariaDB-1:10.5.7+maria~focal' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org bi>
Nov 07 15:18:00 mariadbd[506552]: 2020-11-07 15:18:00 0 [Note] InnoDB: Buffer pool(s) load completed at 201107 15:18:00
Nov 07 15:18:00 systemd[1]: Started MariaDB 10.5.7 database server.
– Subject: A start job for unit mariadb.service has finished successfully
– Defined-By: systemd
– Support: http://www.ubuntu.com/support
–
-- A start job for unit mariadb.service has finished successfully.
–
-- The job identifier is 298880.

Comment by Marko Mäkelä [ 2020-11-09 ]

lbartolome, I would advise you not to use MariaDB 10.5.7 due to this bug. Basically, any InnoDB data file may become corrupted if one of the InnoDB tables contains an indexed virtual column, or a table defines a unique index on a BLOB or TEXT column. Please use 10.5.6 until 10.5.8 is available, or be prepared to reinitialize your database again.

Comment by Lucía [ 2020-11-09 ]

Thanks for the advice Marko.

Comment by Christopher Yeleighton [ 2021-08-19 ]
2021-08-19 13:53:38 0 Note InnoDB: Uses event mutexes
2021-08-19 13:53:38 0 Note InnoDB: Compressed tables use zlib 1.2.11
2021-08-19 13:53:38 0 Note InnoDB: Number of pools: 1
2021-08-19 13:53:38 0 Note InnoDB: Using generic crc32 instructions
2021-08-19 13:53:38 0 Note mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-08-19 13:53:38 0 Note InnoDB: Using Linux native AIO
2021-08-19 13:53:38 0 Note InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2021-08-19 13:53:38 0 Note InnoDB: Completed initialization of buffer pool
2021-08-19 13:53:38 0 Note InnoDB: Starting crash recovery from checkpoint LSN=684800012,684800012
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=301] with future log sequence number 685051656
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=203] with future log sequence number 685185399
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=202] with future log sequence number 684986632
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=201] with future log sequence number 685185373
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=200] with future log sequence number 685185347
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=199] with future log sequence number 685051432
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=198] with future log sequence number 685185321
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=197] with future log sequence number 685185295
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=196] with future log sequence number 685051364
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=195] with future log sequence number 685185269
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=194] with future log sequence number 685183435
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=193] with future log sequence number 685183176
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=192] with future log sequence number 685183150
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=63] with future log sequence number 685051286
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=62] with future log sequence number 685051262
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=61] with future log sequence number 685051238
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=60] with future log sequence number 685182569
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=59] with future log sequence number 684982236
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=58] with future log sequence number 685182044
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=57] with future log sequence number 685182020
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=56] with future log sequence number 684880135
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=55] with future log sequence number 685047409
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=54] with future log sequence number 685047385
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=53] with future log sequence number 684978861
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=52] with future log sequence number 685047361
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=51] with future log sequence number 684968667
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=50] with future log sequence number 685181327
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=49] with future log sequence number 685181303
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=48] with future log sequence number 685046128
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=47] with future log sequence number 685046104
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=46] with future log sequence number 685180941
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=45] with future log sequence number 684967924
2021-08-19 13:53:38 0 Warning InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=6] with future log sequence number 684877255
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=4] log sequence number 685141086 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=6] log sequence number 684877255 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=649] log sequence number 684877040 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=45] log sequence number 684967924 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=426] log sequence number 684967589 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=46] log sequence number 685180941 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=659] log sequence number 685180871 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=47] log sequence number 685046104 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=868] log sequence number 685045721 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=48] log sequence number 685046128 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=884] log sequence number 685045905 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=49] log sequence number 685181303 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=885] log sequence number 685181107 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0 ERROR InnoDB: Page [page id: space=0, page number=50] log sequence number 685181327 is in the future! Current system log sequence number 684822137.
2021-08-19 13:53:38 0 ERROR InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-08-19 13:53:38 0x7fa9a1d4b800   InnoDB: Assertion failure in file /home/abuild/rpmbuild/BUILD/mariadb-10.5.10/storage/innobase/include/fut0lst.h line 127

InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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 mysqld 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.

210819 13:53:38   ERROR mysqld got signal 6 ;

This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

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.5.10-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 567969 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

Generated at Thu Feb 08 09:27:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.