Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.6
-
None
Description
Reported by marko.
https://buildbot.mariadb.org/#/builders/236/builds/8787/steps/7/logs/stdio
commit 96133583cc54f0da7524e4f657daf412e9a50209
spider/bugfix.insert_select w3 [ fail ]
|
Test ended at 2023-02-24 08:46:42
|
CURRENT_TEST: spider/bugfix.insert_select
|
Failed to start mysqld.2.1
|
mysqltest failed but provided no output
|
- saving '/home/buildbot/amd64-ubuntu-2004-fulltest/build/mysql-test/var/3/log/spider/bugfix.insert_select/' to '/home/buildbot/amd64-ubuntu-2004-fulltest/build/mysql-test/var/log/bugfix.insert_select/'
|
Retrying test spider/bugfix.insert_select, attempt(2/3)...
|
worker[3] > Restart - not started
|
worker[3] > Restart - not started
|
***Warnings generated in error logs during shutdown after running tests: spider/bugfix.insert_select
|
2023-02-24 8:46:41 0 [Warning] InnoDB: Are you sure you are using the right ib_logfile0 to start up the database? Log sequence number in the ib_logfile0 is 42778, less than the log sequence number in the first system tablespace file header, 43654.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 43412 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=0, page number=8] log sequence number 43466 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=0, page number=10] log sequence number 43574 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=0, page number=12] log sequence number 43300 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=0, page number=9] log sequence number 43459 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 43452 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 43546 is in the future! Current system log sequence number 42802.
|
2023-02-24 8:46:41 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.
|
2023-02-24 8:46:41 0 [ERROR] mariadbd: Aria recovery failed. Please run aria_chk -r on all Aria tables (*.MAI) and delete all aria_log.######## files
|
2023-02-24 8:46:41 0 [ERROR] Plugin 'Aria' init function returned error.
|
2023-02-24 8:46:41 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
|
2023-02-24 8:46:41 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
|
2023-02-24 8:46:41 0 [ERROR] Failed to initialize plugins.
|
2023-02-24 8:46:41 0 [ERROR] Aborting
|
marko said it is similar to MDEV-28976.
Attachments
Issue Links
- is blocked by
-
MDEV-22979 "mysqld --bootstrap" / mysql_install_db hangs when Spider is installed
- Closed
-
MDEV-29870 Backport fixes to spider init bugs to 10.4-10.6 once they have SQL service
- Closed
- relates to
-
MDBF-535 Document / improve buildbot setup for spider
- Closed