[MDEV-24810] sys_vars.innodb_flush_method_func failed in buildbot: Server failed to restart Created: 2021-02-08  Updated: 2023-04-14  Resolved: 2023-04-14

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Incomplete Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos73-ppc64/builds/15858

bb-10.3-release 691f93d6d176

sys_vars.innodb_flush_method_func 'innodb' w3 [ fail ]
        Test ended at 2021-02-06 21:25:34
 
CURRENT_TEST: sys_vars.innodb_flush_method_func
mysqltest: In included file "./include/wait_until_connected_again.inc": 
included from ./include/start_mysqld.inc at line 18:
included from ./include/restart_mysqld.inc at line 11:
included from /usr/share/mysql-test/suite/sys_vars/t/innodb_flush_method_func.test at line 24:
At line 23: Server failed to restart
 
The result from queries just before the failure was:
call mtr.add_suppression("InnoDB: Failed to set .*DIRECT");
select @@innodb_flush_method;
@@innodb_flush_method
fsync
create table t(a serial) engine=innodb;
FLUSH TABLES;
select @@innodb_flush_method;
@@innodb_flush_method
O_DIRECT_NO_FSYNC
insert into t values(0);
FLUSH TABLES;



 Comments   
Comment by Marko Mäkelä [ 2023-04-14 ]

Unfortunately, to diagnose this failure we’d need a copy of the server error log, which could give some hints why the server failed to restart. We might even need a core dump, in case the server hung during startup.

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