[MDEV-16944] Windows, mysqltest : The process echo.exe cannot access the file - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 10.2(EOL), (13)
10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
Fix Version/s: 10.5.25, 10.11.8, 10.6.18, 11.0.6, 11.1.5, 11.2.4, 11.4.2
Component/s: Tests
Labels:
None
Environment:
Microsoft Windows

Description

http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/9770

innodb.alter_crash 'innodb'              w3 [ fail ]

        Test ended at 2018-07-26 11:17:18

CURRENT_TEST: innodb.alter_crash

The process cannot access the file because it is being used by another process.

mysqltest: In included file "./include/start_mysqld.inc":

included from D:/win32-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 77:

At line 10: exec of 'D:\win32-debug\build\client\Debug\echo.exe "restart" > D:/win32-debug/build/mysql-test/var/3/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2

Output from before failure:

# Restart mysqld after the crash and reconnect.

The result from queries just before the failure was:

< snip >

ALTER TABLE t1 ADD INDEX (c2,c3);

ERROR HY000: Index c3 is corrupted

ALTER TABLE t1 CHANGE c3 c3 INT NOT NULL;

CHECK TABLE t1;

Table	Op	Msg_type	Msg_text

test.t1	check	status	OK

ALTER TABLE t1 ADD INDEX (c2,c3);

DROP TABLE t1;

# Bug #14669848 CRASH DURING ALTER MAKES ORIGINAL TABLE INACCESSIBLE

# -- Scenario 1:

# Crash the server in ha_innobase::commit_inplace_alter_table()

# just after committing the dictionary changes.

CREATE TABLE t1 (f1 INT NOT NULL, f2 INT NOT NULL) ENGINE=innodb;

INSERT INTO t1 VALUES (1,2),(3,4);

SET DEBUG_DBUG='+d,innodb_alter_commit_crash_after_commit';

ALTER TABLE t1 ADD PRIMARY KEY (f2, f1);

ERROR HY000: Lost connection to MySQL server during query

# Restart mysqld after the crash and reconnect.

More results from queries before failure can be found in D:\win32-debug\build\mysql-test\var\3\log\alter_crash.log

Attachments

Issue Links

causes

MDEV-34435 Increase code coverage for debug_dbug test case during startup

Closed

Activity

Ascending order - Click to sort in descending order

Elena Stepanova created issue - 2018-08-11 23:19

Elena Stepanova made changes - 2018-08-11 23:19

Field	Original Value	New Value
Description	http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/9770 {noformat} nnodb.alter_crash 'innodb' w3 [ fail ] Test ended at 2018-07-26 11:17:18 CURRENT_TEST: innodb.alter_crash The process cannot access the file because it is being used by another process. mysqltest: In included file "./include/start_mysqld.inc": included from D:/win32-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 77: At line 10: exec of 'D:\win32-debug\build\client\Debug\echo.exe "restart" > D:/win32-debug/build/mysql-test/var/3/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2 Output from before failure: # Restart mysqld after the crash and reconnect. The result from queries just before the failure was: < snip > ALTER TABLE t1 ADD INDEX (c2,c3); ERROR HY000: Index c3 is corrupted ALTER TABLE t1 CHANGE c3 c3 INT NOT NULL; CHECK TABLE t1; Table Op Msg_type Msg_text test.t1 check status OK ALTER TABLE t1 ADD INDEX (c2,c3); DROP TABLE t1; # # Bug #14669848 CRASH DURING ALTER MAKES ORIGINAL TABLE INACCESSIBLE # # -- Scenario 1: # Crash the server in ha_innobase::commit_inplace_alter_table() # just after committing the dictionary changes. CREATE TABLE t1 (f1 INT NOT NULL, f2 INT NOT NULL) ENGINE=innodb; INSERT INTO t1 VALUES (1,2),(3,4); SET DEBUG_DBUG='+d,innodb_alter_commit_crash_after_commit'; ALTER TABLE t1 ADD PRIMARY KEY (f2, f1); ERROR HY000: Lost connection to MySQL server during query # Restart mysqld after the crash and reconnect. More results from queries before failure can be found in D:\win32-debug\build\mysql-test\var\3\log\alter_crash.log {noformat}	http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/9770 {noformat} innodb.alter_crash 'innodb' w3 [ fail ] Test ended at 2018-07-26 11:17:18 CURRENT_TEST: innodb.alter_crash The process cannot access the file because it is being used by another process. mysqltest: In included file "./include/start_mysqld.inc": included from D:/win32-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 77: At line 10: exec of 'D:\win32-debug\build\client\Debug\echo.exe "restart" > D:/win32-debug/build/mysql-test/var/3/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2 Output from before failure: # Restart mysqld after the crash and reconnect. The result from queries just before the failure was: < snip > ALTER TABLE t1 ADD INDEX (c2,c3); ERROR HY000: Index c3 is corrupted ALTER TABLE t1 CHANGE c3 c3 INT NOT NULL; CHECK TABLE t1; Table Op Msg_type Msg_text test.t1 check status OK ALTER TABLE t1 ADD INDEX (c2,c3); DROP TABLE t1; # # Bug #14669848 CRASH DURING ALTER MAKES ORIGINAL TABLE INACCESSIBLE # # -- Scenario 1: # Crash the server in ha_innobase::commit_inplace_alter_table() # just after committing the dictionary changes. CREATE TABLE t1 (f1 INT NOT NULL, f2 INT NOT NULL) ENGINE=innodb; INSERT INTO t1 VALUES (1,2),(3,4); SET DEBUG_DBUG='+d,innodb_alter_commit_crash_after_commit'; ALTER TABLE t1 ADD PRIMARY KEY (f2, f1); ERROR HY000: Lost connection to MySQL server during query # Restart mysqld after the crash and reconnect. More results from queries before failure can be found in D:\win32-debug\build\mysql-test\var\3\log\alter_crash.log {noformat}

Alice Sherepa added a comment - 2020-12-02 13:01

https://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/18579/steps/test/logs/stdio

innodb.alter_crash 'innodb'              w4 [ fail ]

        Test ended at 2020-12-01 11:29:01

CURRENT_TEST: innodb.alter_crash

The process cannot access the file because it is being used by another process.

mysqltest: In included file "./include/start_mysqld.inc":

included from D:/win32-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 186:

At line 10: exec of 'D:\win32-debug\build\client\Debug\echo.exe "restart" > D:/win32-debug/build/mysql-test/var/4/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2

Output from before failure:

# Restart mysqld after the crash and reconnect.

The result from queries just before the failure was:

< snip >

) ENGINE=InnoDB DEFAULT CHARSET=latin1

DROP TABLE t2;

CREATE TABLE t2 (f1 INT NOT NULL, f2 INT NOT NULL) ENGINE=InnoDB;

ALTER TABLE t2 ADD PRIMARY KEY (f2, f1);

DROP TABLE t2;

db.opt

# -------------------------

# End of Testing Scenario 2

# -------------------------

# Bug#19330255 WL#7142 - CRASH DURING ALTER TABLE LEADS TO

# DATA DICTIONARY INCONSISTENCY

CREATE TABLE t1(a int PRIMARY KEY, b varchar(255), c int NOT NULL)

ENGINE=InnoDB;

INSERT INTO t1 SET a=1,c=2;

SET DEBUG_DBUG='+d,innodb_alter_commit_crash_after_commit';

ALTER TABLE t1 ADD INDEX (b), CHANGE c d int, ALGORITHM=INPLACE;

ERROR HY000: Lost connection to MySQL server during query

# Restart mysqld after the crash and reconnect.

More results from queries before failure can be found in D:\win32-debug\build\mysql-test\var\4\log\alter_crash.log

 - saving 'D:/win32-debug/build/mysql-test/var/4/log/innodb.alter_crash-innodb/' to 'D:/win32-debug/build/mysql-test/var/log/innodb.alter_crash-innodb/'

Retrying test innodb.alter_crash, attempt(2/3)...

***Warnings generated in error logs during shutdown after running tests: innodb.alter_crash

2020-12-01 11:28:55 7032 [ERROR] InnoDB: Flagged corruption of `c2` in table `test`.`t1` in dict_set_index_corrupted

2020-12-01 11:28:55 7032 [ERROR] InnoDB: Flagged corruption of `c3` in table `test`.`t1` in dict_set_index_corrupted

2020-12-01 11:28:58 6780 [ERROR] InnoDB: Index `c2` of table `test`.`t1` is corrupted

2020-12-01 11:28:58 6780 [ERROR] InnoDB: Index `c3` of table `test`.`t1` is corrupted

Alice Sherepa added a comment - 2020-12-02 13:01 https://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/18579/steps/test/logs/stdio innodb.alter_crash 'innodb' w4 [ fail ] Test ended at 2020-12-01 11:29:01 CURRENT_TEST: innodb.alter_crash The process cannot access the file because it is being used by another process. mysqltest: In included file "./include/start_mysqld.inc": included from D:/win32-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 186: At line 10: exec of 'D:\win32-debug\build\client\Debug\echo.exe "restart" > D:/win32-debug/build/mysql-test/var/4/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2 Output from before failure: # Restart mysqld after the crash and reconnect. The result from queries just before the failure was: < snip > ) ENGINE=InnoDB DEFAULT CHARSET=latin1 DROP TABLE t2; CREATE TABLE t2 (f1 INT NOT NULL, f2 INT NOT NULL) ENGINE=InnoDB; ALTER TABLE t2 ADD PRIMARY KEY (f2, f1); DROP TABLE t2; db.opt # ------------------------- # End of Testing Scenario 2 # ------------------------- # # Bug#19330255 WL#7142 - CRASH DURING ALTER TABLE LEADS TO # DATA DICTIONARY INCONSISTENCY # CREATE TABLE t1(a int PRIMARY KEY, b varchar(255), c int NOT NULL) ENGINE=InnoDB; INSERT INTO t1 SET a=1,c=2; SET DEBUG_DBUG='+d,innodb_alter_commit_crash_after_commit'; ALTER TABLE t1 ADD INDEX (b), CHANGE c d int, ALGORITHM=INPLACE; ERROR HY000: Lost connection to MySQL server during query # Restart mysqld after the crash and reconnect. More results from queries before failure can be found in D:\win32-debug\build\mysql-test\var\4\log\alter_crash.log - saving 'D:/win32-debug/build/mysql-test/var/4/log/innodb.alter_crash-innodb/' to 'D:/win32-debug/build/mysql-test/var/log/innodb.alter_crash-innodb/' Retrying test innodb.alter_crash, attempt(2/3)... ***Warnings generated in error logs during shutdown after running tests: innodb.alter_crash 2020-12-01 11:28:55 7032 [ERROR] InnoDB: Flagged corruption of `c2` in table `test`.`t1` in dict_set_index_corrupted 2020-12-01 11:28:55 7032 [ERROR] InnoDB: Flagged corruption of `c3` in table `test`.`t1` in dict_set_index_corrupted 2020-12-01 11:28:58 6780 [ERROR] InnoDB: Index `c2` of table `test`.`t1` is corrupted 2020-12-01 11:28:58 6780 [ERROR] InnoDB: Index `c3` of table `test`.`t1` is corrupted

Sergei Golubchik made changes - 2021-12-06 21:33

Workflow

MariaDB v3 [ 88847 ]

MariaDB v4 [ 140883 ]

Marko Mäkelä added a comment - 2023-11-29 15:28

This appears to be something specific to Microsoft Windows. wlad, can you help? Here is the latest failure:

preview-11.3-preview b9b56b5fdd7d096e6ce59d3c1072ca30506dd694
innodb.alter_crash 'innodb' w2 [ fail ]
Test ended at 2023-09-13 20:33:02

CURRENT_TEST: innodb.alter_crash
The process cannot access the file because it is being used by another process.
mysqltest: In included file "./include/start_mysqld.inc":
included from D:/winx64-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 160:
At line 37: exec of 'D:\winx64-debug\build\client\\Debug\echo.exe "restart" > D:/winx64-debug/build/mysql-test/var/2/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2
Output from before failure:
# Restart mysqld after the crash and reconnect.

This would appear to be a bug in the restart_mysqld.inc logic.

Marko Mäkelä added a comment - 2023-11-29 15:28 This appears to be something specific to Microsoft Windows. wlad , can you help? Here is the latest failure : preview-11.3-preview b9b56b5fdd7d096e6ce59d3c1072ca30506dd694 innodb.alter_crash 'innodb' w2 [ fail ] Test ended at 2023-09-13 20:33:02 CURRENT_TEST: innodb.alter_crash The process cannot access the file because it is being used by another process. mysqltest: In included file "./include/start_mysqld.inc": included from D:/winx64-debug/build/src/mysql-test/suite/innodb/t/alter_crash.test at line 160: At line 37: exec of 'D:\winx64-debug\build\client\\Debug\echo.exe "restart" > D:/winx64-debug/build/mysql-test/var/2/tmp/mysqld.1.expect' failed, error: 1, status: 1, errno: 2 Output from before failure: # Restart mysqld after the crash and reconnect. This would appear to be a bug in the restart_mysqld.inc logic.

Marko Mäkelä made changes - 2023-11-29 15:28

Fix Version/s		10.4 [ 22408 ]
Fix Version/s		10.5 [ 23123 ]
Fix Version/s		10.6 [ 24028 ]
Fix Version/s		10.11 [ 27614 ]
Fix Version/s		11.0 [ 28320 ]
Fix Version/s		11.1 [ 28549 ]
Fix Version/s		11.2 [ 28603 ]
Fix Version/s		11.3 [ 28565 ]
Fix Version/s	10.2 [ 14601 ]
Affects Version/s		10.3 [ 22126 ]
Affects Version/s		10.4 [ 22408 ]
Affects Version/s		10.5 [ 23123 ]
Affects Version/s		10.6 [ 24028 ]
Affects Version/s		10.7 [ 24805 ]
Affects Version/s		10.8 [ 26121 ]
Affects Version/s		10.9 [ 26905 ]
Affects Version/s		10.10 [ 27530 ]
Affects Version/s		10.11 [ 27614 ]
Affects Version/s		11.0 [ 28320 ]
Affects Version/s		11.1 [ 28549 ]
Affects Version/s		11.2 [ 28603 ]
Affects Version/s		11.3 [ 28565 ]
Assignee	Marko Mäkelä [ marko ]	Vladislav Vaintroub [ wlad ]
Environment		Microsoft Windows

Marko Mäkelä made changes - 2023-11-29 15:28

Status

Open [ 1 ]

Confirmed [ 10101 ]

Vladislav Vaintroub added a comment - 2023-11-29 18:40

This all stems from nonsensical "fix" by Bjorn Munch https://bugs.mysql.com/bug.php?id=58515
Everyone is repeating "exec echo" since then.

Vladislav Vaintroub added a comment - 2023-11-29 18:40 This all stems from nonsensical "fix" by Bjorn Munch https://bugs.mysql.com/bug.php?id=58515 Everyone is repeating "exec echo" since then.

Vladislav Vaintroub made changes - 2024-04-15 21:53

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Vladislav Vaintroub made changes - 2024-04-15 21:54

Summary

innodb.alter_crash failed in buildbot - The process cannot access the file

Windows, mysqltest : The process echo.exe cannot access the file

Vladislav Vaintroub made changes - 2024-04-15 22:09

Assignee	Vladislav Vaintroub [ wlad ]	Oleksandr Byelkin [ sanja ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Vladislav Vaintroub added a comment - 2024-04-15 22:16

sanja, could you please review https://github.com/MariaDB/server/commit/9cb75bb085959a4b8eeec3600e9207e0148a820c

Thank you!

Vladislav Vaintroub added a comment - 2024-04-15 22:16 sanja , could you please review https://github.com/MariaDB/server/commit/9cb75bb085959a4b8eeec3600e9207e0148a820c Thank you!

Oleksandr Byelkin added a comment - 2024-04-17 08:36

OK to push

Oleksandr Byelkin added a comment - 2024-04-17 08:36 OK to push

Oleksandr Byelkin made changes - 2024-04-17 08:36

Assignee	Oleksandr Byelkin [ sanja ]	Vladislav Vaintroub [ wlad ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Vladislav Vaintroub made changes - 2024-04-18 12:10

Fix Version/s		10.5.25 [ 29626 ]
Fix Version/s	10.4 [ 22408 ]
Fix Version/s	10.5 [ 23123 ]
Fix Version/s	10.6 [ 24028 ]
Fix Version/s	10.11 [ 27614 ]
Fix Version/s	11.0 [ 28320 ]
Fix Version/s	11.1 [ 28549 ]
Fix Version/s	11.3 [ 28565 ]
Fix Version/s	11.2 [ 28603 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

JiraAutomate made changes - 2024-04-18 12:10

Fix Version/s		10.6.18 [ 29627 ]
Fix Version/s		10.11.8 [ 29630 ]
Fix Version/s		11.0.6 [ 29628 ]
Fix Version/s		11.1.5 [ 29629 ]
Fix Version/s		11.2.4 [ 29631 ]
Fix Version/s		11.4.2 [ 29633 ]

Marko Mäkelä made changes - 2024-06-20 14:13

Link

This issue causes ~~MDEV-34435~~ [ ~~MDEV-34435~~ ]

People

Assignee:: Vladislav Vaintroub

Reporter:: Elena Stepanova

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2018-08-11 23:19

Updated:: 2024-06-20 14:13

Resolved:: 2024-04-18 12:10

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server