Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Critical
-
Resolution: Unresolved
-
10.11, 11.4, 11.8, 12.3
-
Not for Release Notes
Description
The test innodb.log_file_overwrite is failing quite often ever since the InnoDB startup and shutdown were simplified in MDEV-38833 and MDEV-38968.
|
10.11 ebae058ae3d63d8633db48dd6231d37a7f552b4c |
innodb.log_file_overwrite w10 [ fail ]
|
Test ended at 2026-03-16 13:29:37
|
CURRENT_TEST: innodb.log_file_overwrite
|
mysqltest: In included file "./include/wait_until_connected_again.inc":
|
included from ./include/start_mysqld.inc at line 49:
|
included from ./include/restart_mysqld.inc at line 11:
|
included from /home/buildbot/amd64-ubuntu-2204-debug/build/mysql-test/suite/innodb/t/log_file_overwrite.test at line 14:
|
At line 44: Server failed to restart
|
The result from queries just before the failure was:
|
call mtr.add_suppression("InnoDB: Plugin initialization aborted");
|
call mtr.add_suppression("plugin 'InnoDB' registration as a STORAGE ENGINE failed.");
|
CREATE TABLE t1(f1 INT NOT NULL, f2 TEXT)ENGINE=InnoDB;
|
# restart: --debug_dbug=+d,ib_log_checkpoint_avoid_hard --innodb_flush_sync=0
|
INSERT INTO t1 SELECT seq, repeat('a', 4000) FROM seq_1_to_1800;
|
# restart: --debug_dbug=+d,before_final_redo_apply --innodb_log_file_size=8M
|
Here are some context from the test file:
|
mysql-test/suite/innodb/t/log_file_overwrite.test |
|
10
|
INSERT INTO t1 SELECT seq, repeat('a', 4000) FROM seq_1_to_1800; |
11
|
let $restart_parameters=--debug_dbug=+d,before_final_redo_apply --innodb_log_file_size=8M; |
12
|
let $shutdown_timeout=0;
|
13
|
--source include/restart_mysqld.inc |
Let us look at the corresponding server error log file:
2026-03-16 13:20:41 0 [Note] InnoDB: innodb_buffer_pool_size_max=8388608m, innodb_buffer_pool_size=8m
|
2026-03-16 13:20:41 0 [Note] InnoDB: Completed initialization of buffer pool
|
2026-03-16 13:20:41 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=10658786
|
2026-03-16 13:20:41 0 [Note] InnoDB: Multi-batch recovery needed at LSN 13728140
|
2026-03-16 13:20:41 0 [Note] InnoDB: End of log at LSN=18073949
|
2026-03-16 13:20:41 0 [Note] InnoDB: To recover: LSN 13728140/18073949; 262 pages
|
2026-03-16 13:20:41 0 [Note] InnoDB: To recover: LSN 16796593/18073949; 258 pages
|
2026-03-16 13:20:41 0 [ERROR] InnoDB: Plugin initialization aborted at srv0start.cc[1447] with error Generic error
|
2026-03-16 13:20:41 0 [Note] InnoDB: Starting shutdown...
|
CURRENT_TEST: innodb.log_file_overwrite
|
$ /home/buildbot/amd64-ubuntu-2204-debug/build/sql/mariadbd --defaults-group-suffix=.1 --defaults-file=/home/buildbot/amd64-ubuntu-2204-debug/build/mysql-test/var/10/my.cnf --log-output=file --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-lock-waits --innodb-metrics --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-columns --innodb-sys-fields --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-indexes --innodb-sys-tables --innodb-sys-virtual --loose-sequence --core-file --loose-debug-sync-timeout=300
|
2026-03-16 13:29:37 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 32246)
|
The $shutdown_timeout=0 should cause the server to be killed. Before the SIGKILL is sent, a shutdown may be initiated. That is why it is normal to see the message InnoDB: Starting shutdown... followed by nothing.
For some reason, the test is stuck for 9 minutes without attempting to restart the server after the kill.
Note: MDEV-39104 is a similar failure where InnoDB shutdown clearly is hanging. It does not use $shutdown_timeout=0.
Attachments
Issue Links
- relates to
-
MDEV-33073 always green buildbot
-
- Stalled
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-