MySQL Bugs: #46628: server hang and crash

Bug #46628	server hang and crash
Submitted:	10 Aug 2009 13:13	Modified:	27 Apr 2010 6:19
Reporter:	Miroslav Mastný	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S1 (Critical)
Version:	5.0.67, 5.0.84, 5.1.42	OS:	Windows (XP Prof)
Assigned to:		CPU Architecture:	Any

Description:
Server hang and crash after timeout, select max(autoincrement_column) and insert without autoincrement_column value to innodb always active.

Computer was changed, database engine reinstalled, database structure recreated, all MyISAM tables repaired.

Query executed from C client: mysql_version.h
#define PROTOCOL_VERSION		10
#define MYSQL_SERVER_VERSION		"4.1.15"

Error log attached.

How to repeat:
Propably execute same queries to deadlock

Thank you for the bug report. Could you please provide the dump file (with insert statements) and the queries involved?. Thanks in advance.

Is sorry, but i cannot find any dump file. I will send you next time. Where will be requested dump file located?

Thank you for the feedback. The dump file you need to create it for example with mysqldump client tool so we can create the database to run the queries against. Thanks in advance.

Thank you for the feedback.

I can not repeat described behavior using generic test.

Please explain how you run these problem queries. Do you use transactions? Is it possible if you run other queries in same transactions before these 2 problem statements?

Which MySQL version do you use?

Look for header (Version:     5.0.67/5.0.84)

This looks like something got wrong during upgrading.

Use ALTER TABLE <your-innodb-tables> ENGINE=INNODB;

This will copy the table. Which means it will refresh it.

I think something happens to indexes or whatever else on your innodb table during upgrade.

Table was previously completelly rebuilded (create detection_cameras_new, insert all records from detection_cameras, rename tables), problem stay.

Please show output from:

SHOW VARIABLES LIKE '%isolation%';

'tx_isolation', 'REPEATABLE-READ'

current version is 5.0.67 (seems to be little more stable)

Thank you for the feedback.

I still can not repeat problem described. Also you have a lot of records "mysqld got exception 0xc0000005 ;" This can show memory failures also. Please check you RAM.

Please also indicate accurate version of Windows and MySQL package do you run.

Thank you for the feedback.

> Computer was completelly changed, RAM problem is implausible.

Was it same hardware?

No

We upgrade to version 5.1.39, problem stay (server crashes in few hours). New error log attached.

Do you have any new information or any debug version to more debug output?

In the last case I see assertion failure and (forced) crash because of InnoDB flushing buffer pool and blocking other thread(s) from working with it for too long. 

So, please, send your current my.ini file content. How much RAM do you have in this system and is it 32-bit or 64-bit OS?

32-bit OS, 2GB memory (1GB free)

My second (testing) server generate same deadlocks, but does't crash.

Thank you for the feedback.

Bug #44030 which looks similar to problem originally reported has been fixed in version 5.1.40. Could you please try this version or latest 5.1.41 and inform us if problem still exists?

MySQL community server 5.1.42 still crash few times per day with message

InnoDB: We intentionally crash the server, because it appears to be hung.
100105 20:16:52  InnoDB: Assertion failure in thread 14576 in file .\srv\srv0srv.c line 2137

Thank you for the feedback.

> MySQL community server 5.1.42 still crash few times per day

Does it crash with same queries? Could you please send us new error log with InnoDB monitor output? Please also try current version 5.1.45.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Server with MySQL database is off and never will be used in future. You can stop this bug.

Thank you for the feedback.

Closed as "Can't repeat" because last comment.