[MDEV-28495] Corruption due to attempting to start up multiple servers on the same data Created: 2022-05-06  Updated: 2023-07-05  Resolved: 2022-07-27

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.34
Fix Version/s: 10.3.36, 10.4.26, 10.7.5, 10.5.22, 10.6.15, 10.9.8, 10.10.6, 10.11.5, 11.0.3, 11.1.2, 11.2.1

Type: Bug Priority: Minor
Reporter: Robin Assignee: Marko Mäkelä
Resolution: Fixed Votes: 0
Labels: corruption, regression, startup

Issue Links:
Duplicate
is duplicated by MDEV-28662 [ERROR] mysqld got signal 11 after up... Closed
is duplicated by MDEV-28697 One Node crashed and did not recover Closed
Problem/Incident
is caused by MDEV-24393 table_open_cache creates same number ... Closed
Relates
relates to MDEV-31568 innodb protection against dual proces... Closed
relates to MDEV-28976 InnoDB: Missing FILE_CHECKPOINT Closed
relates to MDEV-31568 innodb protection against dual proces... Closed

 Description   

Somebody have idea what caused this? I wasn't able to start db server after that.

2022-05-06 16:00:26 0 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2022-05-06 16:00:57 0 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2022-05-06 16:00:57 0 [ERROR] Plugin 'Aria' init function returned error.
2022-05-06 16:00:57 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2022-05-06 16:00:57 0 [Note] InnoDB: Using Linux native AIO
2022-05-06 16:00:57 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-05-06 16:00:57 0 [Note] InnoDB: Uses event mutexes
2022-05-06 16:00:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-06 16:00:57 0 [Note] InnoDB: Number of pools: 1
2022-05-06 16:00:57 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-05-06 16:00:57 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 4, chunk size = 128M
2022-05-06 16:00:58 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-06 16:00:58 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-05-06 16:00:59 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=13591472328
2022-05-06 16:00:59 0 [Note] InnoDB: Starting final batch to recover 11 pages from redo log.
2022-05-06 16:00:59 0 [Note] InnoDB: Resizing redo log from 2*507510784 to 2*717225984 bytes; LSN=13591476263
2022-05-06 16:00:59 0 [Note] InnoDB: Starting to delete and rewrite log files.
2022-05-06 16:00:59 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 717225984 bytes
2022-05-06 16:00:59 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 717225984 bytes
2022-05-06 16:00:59 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2022-05-06 16:00:59 0 [Note] InnoDB: New log files created, LSN=13591476263
2022-05-06 16:00:59 0 [ERROR] InnoDB: Page [page id: space=34654, page number=0] log sequence number 13591485280 is in the future! Current system log sequence number 13591476757.
2022-05-06 16:00:59 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.
2022-05-06 16:00:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-05-06 16:00:59 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-05-06 16:00:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-05-06 16:00:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-05-06 16:00:59 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-05-06 16:00:59 0 [Note] InnoDB: 10.3.34 started; log sequence number 13591476263; transaction id 2553327
2022-05-06 16:00:59 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-05-06 16:00:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-05-06 16:00:59 0 [ERROR] mysqld: unknown option '--validate-config'
2022-05-06 16:00:59 0 [ERROR] Aborting
 
2022-05-06 16:00:59 3 [ERROR] InnoDB: Page [page id: space=34654, page number=3] log sequence number 13591490369 is in the future! Current system log sequence number 13591476757.
2022-05-06 16:00:59 3 [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.
2022-05-06 14:01:00 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
2022-05-06 14:01:00 0 [Note] Event Scheduler: Purging the queue. 0 events
2022-05-06 14:01:00 0 [Note] InnoDB: FTS optimize thread exiting.
2022-05-06 14:01:00 0 [Note] InnoDB: Starting shutdown...
2022-05-06 14:01:00 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 0, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 1, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 2, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 3, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 4, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 5, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 6, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Instance 7, restricted to 8192 pages due to innodb_buf_pool_dump_pct=25
2022-05-06 14:01:00 0 [Note] InnoDB: Buffer pool(s) dump completed at 220506 14:01:00
Warning: Memory not freed: 520
2022-05-06 14:01:02 0 [Note] InnoDB: Shutdown completed; log sequence number 13591494619; transaction id 2553402
2022-05-06 14:01:02 0 [Note] /usr/sbin/mysqld: Shutdown complete
 
2022-05-06 16:01:02 0 [Note] InnoDB: Using Linux native AIO
2022-05-06 16:01:02 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-05-06 16:01:02 0 [Note] InnoDB: Uses event mutexes
2022-05-06 16:01:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-06 16:01:02 0 [Note] InnoDB: Number of pools: 1
2022-05-06 16:01:02 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-05-06 16:01:02 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 4, chunk size = 128M
2022-05-06 16:01:02 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-06 16:01:02 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=203] log sequence number 13591488868 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=464] log sequence number 13591488868 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=204] log sequence number 13591488912 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=369] log sequence number 13591488912 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=205] log sequence number 13591488956 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=356] log sequence number 13591488956 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=206] log sequence number 13591489000 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=362] log sequence number 13591489000 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=207] log sequence number 13591489060 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=433] log sequence number 13591489060 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=208] log sequence number 13591489104 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=481] log sequence number 13591489104 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=209] log sequence number 13591489148 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=370] log sequence number 13591489148 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=210] log sequence number 13591489192 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=372] log sequence number 13591489192 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=211] log sequence number 13591489236 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=439] log sequence number 13591489236 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=212] log sequence number 13591489280 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=393] log sequence number 13591489280 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=213] log sequence number 13591489324 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=348] log sequence number 13591489324 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=214] log sequence number 13591489368 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=440] log sequence number 13591489368 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=217] log sequence number 13591489412 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=341] log sequence number 13591489412 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 13591489456 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=336] log sequence number 13591489456 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=223] log sequence number 13591489500 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=459] log sequence number 13591489500 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=226] log sequence number 13591489560 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=408] log sequence number 13591489560 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=229] log sequence number 13591494004 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=409] log sequence number 13591494004 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=232] log sequence number 13591494048 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=390] log sequence number 13591494048 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=235] log sequence number 13591494092 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=363] log sequence number 13591494092 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=238] log sequence number 13591494136 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=410] log sequence number 13591494136 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=241] log sequence number 13591494196 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=449] log sequence number 13591494196 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=245] log sequence number 13591494240 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=427] log sequence number 13591494240 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=248] log sequence number 13591494284 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=474] log sequence number 13591494284 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=251] log sequence number 13591494328 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=396] log sequence number 13591494328 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=252] log sequence number 13591494372 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=482] log sequence number 13591494372 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=253] log sequence number 13591494416 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=0, page number=364] log sequence number 13591494416 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-05-06 16:01:02 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-05-06 16:01:02 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-05-06 16:01:02 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-05-06 16:01:02 0 [Note] InnoDB: Waiting for purge to start
2022-05-06 16:01:02 0 [Note] InnoDB: 10.3.34 started; log sequence number 13591476857; transaction id 2553403
2022-05-06 16:01:02 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-05-06 16:01:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-05-06 16:01:02 0 [Note] Server socket created on IP: '127.0.0.1'.
2022-05-06 16:01:02 0 [Note] Reading of all Master_info entries succeeded
2022-05-06 16:01:02 0 [Note] Added new Master_info '' to hash table
2022-05-06 16:01:02 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.3.34-MariaDB-0ubuntu0.20.04.1'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Ubuntu 20.04
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=2369, page number=2232] log sequence number 13591493844 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=2369, page number=3280] log sequence number 13591493780 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=2369, page number=3701] log sequence number 13591493960 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:02 0 [ERROR] InnoDB: Page [page id: space=2369, page number=3723] log sequence number 13591493814 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:02 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.
2022-05-06 16:01:03 0 [ERROR] InnoDB: Page [page id: space=2440, page number=12770] log sequence number 13591493438 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:03 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.
2022-05-06 16:01:03 0 [ERROR] InnoDB: Page [page id: space=2440, page number=13121] log sequence number 13591493408 is in the future! Current system log sequence number 13591476866.
2022-05-06 16:01:03 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.
2022-05-06 16:01:04 39 [ERROR] InnoDB: Page [page id: space=34654, page number=0] log sequence number 13591485280 is in the future! Current system log sequence number 13591476910.
2022-05-06 16:01:04 39 [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.
2022-05-06 16:01:04 39 [ERROR] InnoDB: Page [page id: space=34654, page number=3] log sequence number 13591490369 is in the future! Current system log sequence number 13591476910.
2022-05-06 16:01:04 39 [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.
2022-05-06 16:01:04 39 [ERROR] InnoDB: Page [page id: space=34654, page number=9] log sequence number 13591490369 is in the future! Current system log sequence number 13591476910.
2022-05-06 16:01:04 39 [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.
2022-05-06 16:01:05 39 [ERROR] InnoDB: Page [page id: space=34654, page number=14] log sequence number 13591490485 is in the future! Current system log sequence number 13591476910.
2022-05-06 16:01:05 39 [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.
2022-05-06 16:01:05 39 [ERROR] InnoDB: Page [page id: space=2369, page number=3] log sequence number 13591493746 is in the future! Current system log sequence number 13591476910.
2022-05-06 16:01:05 39 [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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=2] log sequence number 13591485280 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=5] log sequence number 13591493200 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=6] log sequence number 13591490063 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=8] log sequence number 13591485280 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=10] log sequence number 13591488386 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=11] log sequence number 13591489931 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [ERROR] InnoDB: Page [page id: space=34654, page number=13] log sequence number 13591489931 is in the future! Current system log sequence number 13591477309.
2022-05-06 16:01:06 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.
2022-05-06 16:01:06 0 [Note] InnoDB: Buffer pool(s) load completed at 220506 16:01:06
2022-05-06 16:01:10 0x7f8350178700  InnoDB: Assertion failure in file /build/mariadb-10.3-AwHSs6/mariadb-10.3-10.3.34/storage/innobase/row/row0ins.cc line 221
InnoDB: Failing assertion: !cursor->index->is_committed()
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.
220506 16:01:10 [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.3.34-MariaDB-0ubuntu0.20.04.1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=3
max_threads=153
thread_count=8
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f8160000c48
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 = 0x7f8350177dd8 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x32)[0x55e7969d7b92]
/usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x55e7964cd1bd]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x143c0)[0x7f83669503c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7f836678d03b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7f836676c859]
/usr/sbin/mysqld(+0x4ee4bd)[0x55e7961e94bd]
/usr/sbin/mysqld(+0x4dab10)[0x55e7961d5b10]
/usr/sbin/mysqld(+0xa1313f)[0x55e79670e13f]
/usr/sbin/mysqld(+0xa1552c)[0x55e79671052c]
/usr/sbin/mysqld(+0xa25bce)[0x55e796720bce]
/usr/sbin/mysqld(+0x978479)[0x55e796673479]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x91)[0x55e7964d8f81]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x1ad)[0x55e7962ac76d]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xb97)[0x55e7962b67a7]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1673)[0x55e7962de5d3]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1f3)[0x55e7962e5053]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1065)[0x55e7962e7425]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x12d)[0x55e7962e93dd]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1fa)[0x55e7963cc9ba]
/usr/sbin/mysqld(handle_one_connection+0x3f)[0x55e7963ccb8f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8609)[0x7f8366944609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7f8366869163]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f8160011970): INSERT INTO `ps_guest` (`id_operating_system`, `id_web_browser`, `id_customer`, `javascript`, `screen_resolution_x`, `screen_resolution_y`, `screen_color`, `sun_java`, `adobe_flash`, `adobe_director`, `apple_quicktime`, `real_player`, `windows_media`, `accept_language`, `mobile_theme`) VALUES ('0', '0', '0', '0', '0', '0', '0', '0', '0', '0', '0', '0', '0', '', '0')
 
Connection ID (thread ID): 46
Status: NOT_KILLED
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
 
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit                     Soft Limit           Hard Limit           Units     
Max cpu time              unlimited            unlimited            seconds   
Max file size             unlimited            unlimited            bytes     
Max data size             unlimited            unlimited            bytes     
Max stack size            8388608              unlimited            bytes     
Max core file size        0                    unlimited            bytes     
Max resident set          unlimited            unlimited            bytes     
Max processes             63683                63683                processes 
Max open files            32768                32768                files     
Max locked memory         65536                65536                bytes     
Max address space         unlimited            unlimited            bytes     
Max file locks            unlimited            unlimited            locks     
Max pending signals       63683                63683                signals   
Max msgqueue size         819200               819200               bytes     
Max nice priority         0                    0                    
Max realtime priority     0                    0                    
Max realtime timeout      unlimited            unlimited            us        
Core pattern: |/usr/share/apport/apport %p %s %c %d %P %E



 Comments   
Comment by Marko Mäkelä [ 2022-05-06 ]

The first messages suggest that you are attempting to run multiple servers on a single set data files. Before MDEV-24393, InnoDB would have refused to start up in such a case by default. Currently, this is only prevented when a non-default startup parameter is specified. The Aria storage engine unconditionally uses advisory locking on hits log file but not on other files.

Messages saying that a log sequence number is in the future are a sign of serious corruption. Even if the server did not crash, your data should be corrupted beyond repair.

Based on comments in MDEV-24393, serg appears to have believed that advisory locking would be enabled by default. Maybe the default should indeed be changed to avoid corruption like this.

Comment by Robin [ 2022-05-06 ]

You are right, I ran mysqld --validate-config and I didn't realize it's only for mysql. I was able to recover data so it's not that big deal.

Thank you for your answer. I'll be more carefull next time.

Comment by Sergei Golubchik [ 2022-05-16 ]

marko, we can enable external-locking by default. Supposedly it won't have much of a performance impact now, when MyISAM is rarely used.

Comment by Marko Mäkelä [ 2022-07-27 ]

danblack, thank you for reminding that this serious regression needs attention.

Based on some discussion with serg, I implemented a simple fix: advisory locks on the InnoDB system tablespace will be acquired unconditionally. An attempt to start up another server would then loook like this:

bb-10.3-MDEV-28495 66d7599c2792555b52c570c3047bea310e59fc3b

2022-07-27 13:17:57 0 [Note] /dev/shm/10.3/sql/mysqld (mysqld 10.3.36-MariaDB-debug) starting as process 370559 ...
/dev/shm/10.3/sql/mysqld: One can only use the --user switch if running as root
2022-07-27 13:17:57 0 [ERROR] mysqld: Can't lock aria control file '/dev/shm/10.3/mysql-test/var/install.db/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2022-07-27 13:18:28 0 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/dev/shm/10.3/mysql-test/var/install.db/aria_log_control'
2022-07-27 13:18:28 0 [ERROR] Plugin 'Aria' init function returned error.
2022-07-27 13:18:28 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2022-07-27 13:18:28 0 [Note] InnoDB: Using Linux native AIO
2022-07-27 13:18:28 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2022-07-27 13:18:28 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-07-27 13:18:28 0 [Note] InnoDB: Uses event mutexes
2022-07-27 13:18:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-07-27 13:18:28 0 [Note] InnoDB: Number of pools: 1
2022-07-27 13:18:28 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-07-27 13:18:28 0 [Note] InnoDB: Initializing buffer pool, total size = 3G, instances = 8, chunk size = 128M
2022-07-27 13:18:29 0 [Note] InnoDB: Completed initialization of buffer pool
2022-07-27 13:18:29 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-07-27 13:18:29 0 [Warning] InnoDB: Failed to set O_DIRECT on file./ibdata1; OPEN: Invalid argument, continuing anyway. O_DIRECT is known to result in 'Invalid argument' on Linux on tmpfs, see MySQL Bug#26662.
2022-07-27 13:18:29 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2022-07-27 13:18:29 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2022-07-27 13:18:29 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1708] with error Generic error
2022-07-27 13:18:29 0 [Note] InnoDB: Starting shutdown...
2022-07-27 13:18:31 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-07-27 13:18:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-07-27 13:18:31 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-07-27 13:18:31 0 [Warning] /dev/shm/10.3/sql/mysqld: unknown option '--loose-enable-named-pipe'
2022-07-27 13:18:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-07-27 13:18:31 0 [ERROR] Aborting
 
Warning: Memory not freed: 520

I still think that it would be cleaner to prevent any further storage engines from starting up if the Aria storage engine cannot be started (since it is mandatory for system tables), but I have no control over that.

Comment by Marko Mäkelä [ 2022-07-27 ]

InnoDB will unconditionally attempt to acquire an advisory lock on the system tablespace.

Comment by Marko Mäkelä [ 2023-07-05 ]

Unfortunately, this serious correctness regression was not fixed in MariaDB Server 10.5 and later major versions before MDEV-31568 was fixed.

Generated at Thu Feb 08 10:01:11 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.