MySQL Bugs: #47206: MySQL Restarts

Bug #47206	MySQL Restarts
Submitted:	9 Sep 9:16	Modified:	21 Oct 9:34
Reporter:	Kostas Mastracoulis
Status:	Open
Category:	Server: InnoDB	Severity:	S2 (Serious)
Version:	5.1.31	OS:	Linux (SUSE 10 SP2)
Assigned to:		Target Version:

Description:
We own a high traffic System (20-30 trans/sec). We face mysql restart almost 2 or 3 times
a week. Here is the logging during the restart:

Any ideas?

Thank you.

How to repeat:
It is unknown the reason so...

The logs of MySQL during the restart

Attachment: MySQLError.txt (text/plain), 8.53 KiB.

Thank you for the problem report. I had never seen a bug report with assertion like this.
Can you, please, try to repeat with a newer version, 5.1.37, and inform about the
results.

Assertion is in os_aio_simulated_handle() function. It expects for os_file_read() or
os_file_write() to return 0, while they don't and do not set any error. Do you know what
exact SQL statement leads to this assertion failure?

Send your my.cnf also.

I am not able to use another version since we are talking about operating Live Systems.At
this point I have to admit that I faced the same issue with version 5.0.27 version.

Additionally I do not know the statement that it is operating at this moment.

Please find attached the my.cnf file.

The my.cnf file

Attachment: mycnf.text (text/plain), 5.45 KiB.

Thank you for the feedback.

Right before crash error log contains:

> 090908 15:22:07  InnoDB: Error: Write to file ./ibdata1 failed at offset 0 134217728.
> InnoDB: 393216 bytes should have been written, only 139264 were written.

Do you have enough free space? Do you have enough free space in temporary directory?

> Additionally I do not know the statement that it is operating at this moment.

If you experience crashes 2-3 times per week you can try to get such a statement. Easiest
way to do it is turn general query log to ON. But in this case you should monitor disk
space, because error log would grow rapidly. Also you can log queries on application
level or use MySQL Proxy with help script.

Alternatively you can use debug version of mysqld and generate core file.

Please try to get problem query using either method.

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".

Since restarts takes place during different statements everytime, I suppose that there is
no meaning to take logs. Any other possible ideas?

Thank you for your replies.